I was getting something like this (please note this is not
the actual log - I can post that tomorrow is someone wants to see
it):
933785415.436366 tcpserver: status: 1/40
933785415.437241 tcpserver: pid 6010 from 127.0.0.1
933785415.462990 tcpserver: ok 6010 localhost:127.0.0.1:25
localhost:127.0.0.1:root:4309
933785453.943401 tcpserver: end 6010 status 256
933785453.943468 tcpserver: status: 0/40
When the status in the next to last line was 0, the message
was delivered. When the status was 256, the message was not
delivered. I could not find any information about exit codes
in any of the documentation. I fixed the problem code, which
made the problem go away. But it still doesn't change the fact
that I had the problem. The remote system thought the message was
delivered, but it was not (i.e., all responses from smtpd where +OK,
but the message never showed up). This seems broken to me.
What do you mean by the 'final' ok? OK to ending the
data segment?
-Tom
Harald Hanche-Olsen wrote:
>
> + Markus Stumpf <[EMAIL PROTECTED]>:
>
> | As with disappering messages:
> | smtpd simply accepts the email and hands it on to other processes
> | (qmail-queue).
>
> That statement may be a bit misleading. The cronology is the other
> way around: qmail-smtpd hands the message to qmail-queue, and does not
> give the final OK until qmail-queue has exited with a zero status
> code. Any SMTP client that doesn't wait for that final OK is broken.
>
> - Harald
--
+-------------------------------------------------------------------+
+ Thomas M. Sasala, Electrical Engineer [EMAIL PROTECTED] +
+ MRJ Technology Solutions http://www.mrj.com +
+ 10461 White Granite Drive, Suite 102 (W)(703)277-1714 +
+ Oakton, VA 22124 (F)(703)277-1702 +
+-------------------------------------------------------------------+
