"Thomas M. Sasala" <[EMAIL PROTECTED]> wrote:
> I think you are missing the point. I'm not looking at the
>exit code. Let me be specific. I was using a Java transport class
>that was not properly written. I would send a message with this class
>and the class would say the message was sent. However, in reality,
>smtpd would reject the message.
>
> To debug the problem I used recordio. I noticed that the
>class was not reading any output from smptd. It just stuffed the
>whole message into smptd and exited. So, I modified the class to
>read input and check for +OK and -ERROR.
+OK and -ERR (not ERROR) are from POP, not SMTP.
> I recorded an entire session where every response from smptd
>was +OK, BUT the mail was never delivered.
Please post that.
>By pouring through the
>logs, I noticed that when there was an exit code of 256, the mail
>was not delivered. When the exit code was 0, the mail was delivered.
>Somewhere during this whole process, I saw the message about bad
>cr/lf. Once I fixed that problem, everything started to work.
If you saw the cr/lf message, I can assure you qmail-smtpd returned
an error on the SMTP DATA command.
> So, the point here is that smtpd responded with +OK for everything,
>leading me to believe the mail had been accepted and was delivered.
If your SMTP daemon is doing "+OK", it's not qmail-smtpd. In fact,
it's probably not even an SMTP daemon.
>However, the mail *never* showed up in the queue. The qmail log was
>blank and the smtpd log showed an exit code of 256.
The qmail-send log would be blank if no message was successfully
injected, e.g., because of a stray LF.
-Dave
