At 11:16 PM 1/23/07, Kyle Wheeler wrote:
Sometimes, when you're doing something unfriendly like rejecting
spam or viruses at SMTP-time (e.g. with simscan), or using
badmailfrom or something like that, you will get errors like this.
There's no actual error recorded in your logs most likely,
Actually, simscan does log when it rejects mail. But in a more
general sense, Kyle's right. Unpatched qmail-smtp does no logging,
so if it rejects a message for some reason, you won't see it in your
logs. You should see tcpserver logging the open/close of the
connection.
As an example of this problem, I subscribe to a couple of email
services from the New York Times. Some of the messages were getting
to me, but I was seeing a LOT of connections in my logs from some of
their servers, which kept connecting and not delivering anything. No
clue why.
Somebody on this list gave me a script to use in my smtpd-run file,
which would call qmail-smtpd, selectively invoking recordio depending
on an environment variable. I could set the variable in my tcprules
file to turn on recordio just for the problem connections, to log all
the traffic. When I did that, I could see qmail-smtpd telling the
NYTimes servers that it wasn't going to talk to them because they
were sending bare LFs. Then I could use the same technique to invoke
fixcrio just for those IPs to fix the problem.
You might not have this specific problem, but there's a good chance
that you have a situation where qmail-smtpd is telling Google's
servers why it doesn't want to talk to them without telling you in
your logs, and if you can capture the session traffic it might tell
you why.
|