David Boyes wrote:
I'm not so much interested in using an email client for
composing,
sending, and receiving email as I am in having a standardized MTA that
programs such as Tripwire, Logwatch, Nagios, and Hobbit can use for
alerts
and exceptional conditions. What I would like is for them to send
their
messages to my corporate mailbox and then I could set up some rules
for
squirreling them away into their own folder.
I want them to be standardized so that I can easily document for
the
benefit of my teammates what steps to go through when setting up a new
Linux guest.
That's exactly what running any of the Unix MTAs {sendmail, exim,
postfix, etc} in non-daemon mode is intended to do. In this
configuration it fires up, sends the message, and exits. No queuing
done, and it gives a positive return code as to whether it worked or not
(rc=0 means message delivered). You have to rely on the smart host to be
up and you take the hit of the startup cost of the MTA for each message,
but that's a premise of your desired configuration.
Setting up the smarthost configuration with YaST and then turning off
the init script using the runlevel editor should be sufficient. Your
scripts can then run /usr/bin/sendmail when needed and it should Just
Work. (note that all the MTAs use a symlink to /usr/bin/sendmail for
historical reasons; you don't have to use actual sendmail to get this to
work).
You _must_ flush the queue because if you don't, and there is a delivery
problem, mail will be queued.
--
Cheers
John
-- spambait
[EMAIL PROTECTED] [EMAIL PROTECTED]
Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/
do not reply off-list
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
