Chris Petersen writes:
After thinking that there was something wrong with one of my credit card
companies' mail server, I noticed the following in my maillog:
Feb 12 09:17:37 mail courierd: newmsg,id=00164819.45D0A131.00001C49: dns;
localhost (localhost [127.0.0.1])
Feb 12 09:17:37 mail courierd:
started,id=00164819.45D0A131.00001C49,from=<>,module=esmtp,host=alerts.chase.com,addr=<Cha...@alerts.chase.com>
Feb 12 09:17:37 mail courieresmtp:
id=00164819.45D0A131.00001C49,from=<>,addr=<Cha...@alerts.chase.com>: 250
Backscatter bounce dropped.
Feb 12 09:17:37 mail courieresmtp:
id=00164819.45D0A131.00001C49,from=<>,addr=<Cha...@alerts.chase.com>,success:
delivered: backscatter bounce dropped
Feb 12 09:17:37 mail courieresmtp:
id=00164819.45D0A131.00001C49,from=<>,addr=<Cha...@alerts.chase.com>,status:
success
Feb 12 09:17:37 mail courierd: completed,id=00164819.45D0A131.00001C49
For now, I've set BOFHSUPPRESSBACKSCATTER=none in bofh to see if I can
get a copy of the actual message (is there anything else I can do, or
maybe a way to whitelist this specific address so I don't have to
completely disable backscatter suppression?).
I just wanted to see if anyone else has run into this or a similar
issue. The timing of these messages corresponds directly with
non-bounce messages (specifically, the "your bill is due in X days" or
"we have mailed out your statement" type emails), so I'm concerned that
there might be a glitch in courier's backscatter detection (or chase.com
is screwing something up in their message headers).
No glitch. It's working as intended. Now, find the reason from the
preceding bounce, and fix it. You're accepting mail, but during local
delivery the mail bounces, and gets suppressed as backscatter -- and
rightfully so.
6 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Weird backscatter...
