Yesterday and today, we've seen at least five (5) instances of
emails being bounced when trying to deliver to a local user
on our server from an external MTA. (Using 1.3.3.2)

Looks like this in the logs: (real addresses obscured)

Aug-6-07 18:28:42 Connected: 64.233.166.181:11068 -> 216.160.187.241:25 -> 216.160.187.241:2525
Aug-6-07 18:28:43 Commencing DNSBL checks on 64.233.166.181
Aug-6-07 18:28:43 Completed DNSBL checks on 64.233.166.181
Aug-6-07 18:28:43 [DNSBL] id-6522c14371 64.233.166.181 <[EMAIL PROTECTED]> to: [EMAIL PROTECTED] DNSBL Received-DNSBL: pass Aug-6-07 18:29:40 id-6522c14371 64.233.166.181 <[EMAIL PROTECTED]> to: [EMAIL PROTECTED] URIBL Received-URIBL: pass
Aug-6-07 18:29:50 Cache reset (/usr/local/assp/spamdb)
Aug-6-07 18:29:51 (snipped...bunch of other connections)
Aug-6-07 18:29:51 [MessageOK] id-6522c14371 64.233.166.181 <[EMAIL PROTECTED]> to: [EMAIL PROTECTED] message ok The Subject was Here Aug-6-07 18:29:51 64.233.166.181 <[EMAIL PROTECTED]> to: [EMAIL PROTECTED] is disconnected

Aug-6-07 18:22:31 Connected: 17.250.248.182:49457 -> 216.160.187.241:25 -> 216.160.187.241:2525 Aug-6-07 18:22:32 id-6152c2950 17.250.248.182 <[EMAIL PROTECTED]> renewing tuplet: (17.250.248.0,mac.com) age: 11m 24s
Aug-6-07 18:22:32 Commencing DNSBL checks on 17.250.248.182
Aug-6-07 18:22:32 Completed DNSBL checks on 17.250.248.182
Aug-6-07 18:22:32 [DNSBL] id-6152c2950 17.250.248.182 <[EMAIL PROTECTED]> to: [EMAIL PROTECTED] DNSBL Received- DNSBL: pass Aug-6-07 18:23:31 id-6152c2950 17.250.248.182 <[EMAIL PROTECTED]> to: [EMAIL PROTECTED] URIBL Received- URIBL: pass
Aug-6-07 18:23:43 Cache reset (/usr/local/assp/spamdb)
Aug-6-07 18:24:00 [MessageOK] id-6152c2950 17.250.248.182 <[EMAIL PROTECTED]> to: [EMAIL PROTECTED] message ok Was the Subject Line Aug-6-07 18:24:00 17.250.248.182 <[EMAIL PROTECTED]> to: [EMAIL PROTECTED] is disconnected

In each case, there is a "Cache reset (/usr/local/assp/spamdb)"
during the attempted message delivery.

From the logs it looks like the message is being delivered - but it isn't.
The originating MTA is bouncing the message back to the external
sender.

Other emails from the SAME sender to the SAME recipient do get
delivered if there is NOT a "Cache reset" during the delivery.

OK, is my server just going weird or has anyone else seen this?

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Assp-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user

Reply via email to