In a very homogenous environment I would do that, but a significant number of the hosts in question are not running a mail daemon. I can get by with the current capabilities, but think cfengine could handle mail better.
Thank you, -Jason Martin -----Original Message----- From: Frank Smith [mailto:[EMAIL PROTECTED] Sent: Friday, August 19, 2005 1:52 PM To: Martin, Jason H; help-cfengine@gnu.org Subject: Re: smtpserver & mx records --On Friday, August 19, 2005 12:59:42 -0700 "Martin, Jason H" <[EMAIL PROTECTED]> wrote: > <resending sans-html, sorry> > > One nice feature would be to have CFEngine understand the concept of > MX records in relation to the smtpserver variable. cfexecd could then > attempt to deliver the output mail to each of the hosts in turn until > it finds one that will accept the message, otherwise it should drop > it. You could set smtpserver to localhost, assuming you have at least a minimal MTA running on each machine listening for local connections, Then the messages could be routed via MX records and would be spooled if your main mailservers happened to be unreachable at the time. Frank > > I realize that the email output is generally a low priority, but it is > very handy to direct it to an automated tool to verify that cfengine > is working properly and picking up its rule updates. > > Thank you, > -Jason Martin > _______________________________________________ Help-cfengine mailing list Help-cfengine@gnu.org http://lists.gnu.org/mailman/listinfo/help-cfengine
