On Thu, Oct 07, 1999 at 07:32:45AM -0400,
"Thomas M. Sasala" <[EMAIL PROTECTED]> wrote:
> 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.
This stuff is pretty much irrelevant. You can't expect to check the status
of which messages were accepted successfully by looking at the exit code.
SMTP allows for the transfer of more than one message and for messages
to be resent after some failure in the same session. So a single exit code
can't tell you all of what you need to know. The data command will return a
success code if the message was successfully accepted. This is what needs to
be checked.
