7 More Discussions You Might Find Interesting
1. Linux
Hello
I have a shell script, which should send email, if any error occurred. This script is running in Red Hat Linux 4.6, and want to configure postfix so it can relay to an Exchange Server.
The Authorization method of Exchange server, I guess is: 250-AUTH NTLM. So I have:
Server A ( Red... (1 Reply)
Discussion started by: viktor1985
1 Replies
2. Shell Programming and Scripting
Hello
I hope somebody can help with this.
I have a shell, that in case of failure, sends an email (relaying through an Exchange Server). This Exchange server only offers NTLM authentication.
250-AUTH NTLM
This is the configuration I have:
Postfix 2.1.1 as client.
Cyrus-SASL... (1 Reply)
Discussion started by: viktor1985
1 Replies
3. UNIX for Dummies Questions & Answers
Hello
I hope somebody can help with this.
I have a shell, that in case of failure, sends an email (relaying through an Exchange Server). This Exchange server only offers NTLM authentication.
250-AUTH NTLM
This is the configuration I have:
Postfix 2.1.1 as client.
Cyrus-SASL... (1 Reply)
Discussion started by: viktor1985
1 Replies
4. UNIX for Dummies Questions & Answers
Hi All,
I have a unix box which is in a network with windows machine, I am able to send the mails to the user id's with in the unix box. I dont have Internet connection for this box, so I am not able to test if it can send mails to external network or not?
I want to know, if SMTP is already... (1 Reply)
Discussion started by: balu_puttaganti
1 Replies
5. Programming
Greetings,
I am writing a C socket application that needs NTLM authorization before it can post HTTP requests, and
I am having trouble with NTLM authorization messages.
:b: I've found the following urls extremely valuable for creating message functions:
Davenport WebDAV-SMB Gateway... (1 Reply)
Discussion started by: edvin
1 Replies
6. Programming
how do you send a ".\n" in a smtp client?
>354 Send message, end with <CRLF>.<CRLF>
>.
>
i have already issued a "./n" but it doesnt work.
please help. thanks. (1 Reply)
Discussion started by: grotesque
1 Replies
7. UNIX for Advanced & Expert Users
Hi All,
I am running an email server on a Linux machine. My goal is to set up in a way that I can use pop3 to retrieve mail from a Windows machine using Outlook. Now I can download the messages from the Linux email server, however I can not send out messages. I encounter this error:
... (1 Reply)
Discussion started by: vtran4270
1 Replies
2004-04-15
mailping
0.0.4
MAILPING-CRON(1) Mailping MAILPING-CRON(1)
NAME
mailping-cron - run periodic processing to test email service availability and functioning
SYNOPSIS
mailping-cron
DESCRIPTION
mailping-cron processes incoming emails, updates status and sends out probe messages.
The idea is to configure multiple email "circuits", send probe messages regularly, and see whether they complete the circuit and how long
it took.
Setting up a circuit
1. Give a name to the circuit, hereafter referred to as circuit.
2. Arrange for a local email address to be delivered to maildir /var/lib/mailping/state/circuit/incoming/. See mailping-store.
3. Create a configuration for the circuit, by creating directory /etc/mailping/circuit.
If you need non-default sender and/or recipient addresses, create files from and to there, containing the sender and recipient
addresses suitable for the circuit.
4. You're done! Munin should now see the data.
Testing multiple servers
To test functioning of more than one email server, arrange an email alias at a remote site pointing to an address on your server, and set
the address of that alias here.
Here's an example of testing a system consisting of two email servers and everything in that path (smarthosts, primary MXs, virus checkers,
etc.):
Local address <mailping+that@this.example.com> is delivered with mailping-store to /var/lib/mailping/state/that/incoming/.
Remote address <echo@that.example.com> is an alias that redirects all email to <mailping+that@this.example.com>.
/etc/mailping/that/to is set to <echo@that.example.com>.
FILES
/etc/mailping/circuit/from
Sender address for the probe emails. Default: <currentuserid@fullyqualifiedhostname>.
/etc/mailping/circuit/to
Recipient address for the probe emails. You must arrange for the email to eventually get delivered to the maildir
/var/lib/mailping/state/circuit/incoming/. mailping-store will probably be useful in that. Default:
<currentuserid+circuit@fullyqualifiedhostname>
/etc/mailping/circuit/admin
Admistrative address, set as Reply-To in probe messages. Default: do not add Reply-To.
/etc/mailping/circuit/interval
How often a probe message is sent, in seconds. Default: 600 seconds.
/var/lib/mailping/state/circuit/
Stored state for the probing.
/var/lib/mailping/state/circuit/junk/
Maildir used to store all messages in incoming that do not look like probe messages. Read and delete them regularly.
/var/lib/mailping/state/circuit/broken/
Maildir used to store all messages in incoming that do look like probe messages, but a corresponding pending entry cannot be found.
Duplicated probe messages cause these. Read and delete them regularly.
ENVIRONMENT
MAILPING_CONFIGDIR
Override the location of the configuration directory. Default: /etc/mailping
MAILPING_STATEDIR
Override the location of the state directory. Circuit states are stored in the state subdirectory of this directory, in subdirectories
named after the circuit name. Default: /var/lib/mailping
SEE ALSO
mailping-store(1), mailping-success(1), mailping-latency(1)
AUTHOR
Tommi Virtanen <tv@havoc.fi>
Havoc Consulting
Author.
COPYRIGHT
Copyright (C) 2004 Havoc Consulting
mailping 0. 2004-04-15 MAILPING-CRON(1)