Re: Configuring for use with qmail
Marco Paganini <[email protected]> Wed, 31 Mar 2004 12:23:31 -0500
| Newsgroups | gmane.mail.spam.active-spam-killer.general |
|---|---|
| Message-ID | <[email protected]> |
Hi Marc, (very late answer, sorry...) > > > Marco: I think a more prominent log level for the error message would > > > be in order when the sendmail command fails, no? > > > > The problem is that sendmail will fork and always return a valid > > code... > > ... but some light-weight SMTP forwarders (nullmailer, ssmtp, etc.) > may not. > > What I understood from "sendmail". > > "sendmail" really means to thing: > - one thing is a more or less standard interface to send a mail from a > unix machine > - the other is a particular implementation of it. > > Some implementations may return immediatly a valid code guaranteeing > that if something goes wrong, they'll get back to you (using an mail > message usually?). Asynchronous style. Others may not systematically > fork and try to be more "synchronized" style, giving you feedback as > soon as possible. > > Please correct me. When I talk "sendmail" in this particular case, I'm referring to "/usr/sbin/sendmail", provided by many different MTAs. The problem with detecting a "failure" with sendmail is that sendmail delivers asynchronously. It will always return an "OK" code and deal with the problem later. Of course, it can be configured to run synchronously, but that would add undesirable delays to the process. Regards, Paga -- Marco Paganini | UNIX / Linux / Networking [email protected] | PGP: http://www.paganini.net/pgp/ http://www.paganini.net | Magnus Frater te spectat... ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click