On Mar 16, 2007, at 10:43 AM, Bill Shupp wrote:
I can't recall seeing that exit status, and don't see it in the man
page. I assume you have simscan debugging turned on?
(SIMSCAN_DEBUG="9" environment). It could be something in the
qmail-queue chain.
Regarding recordio, just put it at the front of your chain, i.e. just
before rblsmtpd. Also, I use this multilog expression to grab just
the
4x and 5x errors, which may or not be useful here:
multilog t '-* * > *' '-* * < *' '+* * > 5*' '* > 4*'
/var/log/qmail/smtpd-mx
Anything interesting corresponding in your clamd or spamd logs?
OK, I think I've figured it out. I'm pretty sure that status 256 is
when the connection is closed improperly -- i.e., there wasn't a QUIT
before closing. That's my best guess at this point, and I don't
think it's an indication of a problem.
It looks like a lot of SMTP servers close the connection before
waiting for a response. I did see it on soft-failures (like barelfs
from a Windows server) and even connections that didn't get past HELO.
At this point, I'm not too concerned. I'm leaving simscan logging
set high and will grep the logs for the domain we've had trouble with
to see what the deal is. I did see a message come through with a
status 256 that was correctly delivered locally, so it isn't a fatal
error.
-Tom
