Noel Jones wrote:
Victor Duchovni wrote:
On Fri, Feb 06, 2009 at 01:30:01PM -0800, Chris St Denis wrote:
Anyway, on to the problems. How do I deal with log entries like
this. A queue ID is created, but nothing ever happens to it. There
is no reject
There was one valid recipient, but the mail transaction was not
completed. This could be a header_checks rule, or a network failure
or the client crashing. Any logfile processor will have to deal
sessions that do not go from start to end.
Wietse
Thanks, but those particular causes doesn't seem to explain it.
This system does not have any header checks (the server it's
receiving the mail from does all the spam/etc. filtering) and if it
was a network failure or client crashing there should be an
additional error message like /^timeout after ([A-Z-]+) (.*)$/ or
^/lost connection after ([A-Z-]+).*from (.*)$/
Only if the connection was lost. The client may have been doing address
validation or a dictionary attack, ... and so can just "QUIT" after
"RCPT TO". Presto-magic, no errors. No message implies connection loss
only after "DATA", not after "RCPT TO".
also you grepped for only "smtpd" processes. There is likely further
information about this transaction logged by cleanup and qmgr, all
with the same QUEUEID.
No, I did a second grep for the queue ID (it's in the original post).
That was the only process with it.
There is a policy server however. Could a reject from a policy server
cause this or would it generate a "reject:" line?
--
Chris St Denis
Programmer
SmarttNet (www.smartt.com)
Ph: 604-473-9700 Ext. 200
-------------------------------------------
"Smart Internet Solutions For Businesses"
