On Fri, 28 Jul 2006, Chris Blaise wrote:
>
> 2006-07-28 07:23:11 1G6SGG-0007wS-Bh <= someaddress@???
That shows a delay of 175 seconds, based on the timestamp in the message
ID (which is generated after Exim receives the message header), and the
more readable log line timestamp (generated after Exim finally accepts the
message). There's no way of getting Exim to log this difference directly,
I'm afraid.
$ exim -be '${base62d:1G6SGG}'
1154092816
$ TZ=MST7MDT date -d"2006-07-28 07:23:11" +%s
1154092991
> My guess is that msn is quitting before waiting the full RFC timeout
> (by a lot in the DATA section!) and hanging up the connection. It thinks
> the message wasn't sent, exim thinks it was, and the message thus gets
> duplicated.
That's almost certainly correct.
> Is there a way to detect if this is happening via log options?
lost_incoming_connection is part of the default logging options; you might
want to add smtp_connection for more detail.
> And/or is there a built-in way deal with this situation?
The only way is to ensure that your machine is meaty enough to scan email
quickly. In particular you should ensure that SpamAssassin is tuned for
speed, such as having a local DNS cache for RBL lookups.
Tony.
--
<fanf@???> <dot@???>
http://dotat.at/ ${sg{\N${sg{\
N\}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}\
\N}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}
