Steve [Spamassassin] writes: > Larry Nedry wrote: > > VBounce works very well for me. > > <http://wiki.apache.org/spamassassin/VBounceRuleset> > Thanks for this pointer... I've taken a look at this and installed it on > my Spamassassin 3.1 configuration. I am, however, bemused about a > couple of details... > > I understand that this plugin introduces two new tags: > > (a) BOUNCE_MESSAGE > (b) ANY_BOUNCE_MESSAGE > > I'm not clear what is the intended difference in their meaning.
There are several more; MY_SERVERS_FOUND: a whitelisted relay a la "whitelist_bounce_relays" was found BOUNCE_MESSAGE: an MTA-generated bounce, "message was undeliverable" etc. CRBOUNCE_MESSAGE: Challenge-response bounce message, eg. "please confirm your message was not spam" VBOUNCE_MESSAGE: a virus-scanner-generated bounce, e.g. "You sent a virus" ANY_BOUNCE_MESSAGE: any of the *BOUNCE_MESSAGE types > Having read about the whitelist_bounce_relays, I thought that looked very > neat... and I verified that every bounce message that I want to receive will > mention in the headers (ellipsis => something-or-other) :- > > Received: > from ... (...) by mail.mydomain.com (Postfix)... > > So, I configured whitelist_bounce_relays to mail.mydomain.com. > Unfortunately, as far as I can tell, this has made no difference. Both > bogus bounces and legitimate bounces (where I intentionally send a mail > message to a non-existent account on a remote server) are marked > identically with both BOUNCE_MESSAGE and ANY_BOUNCE_MESSAGE.... > Shouldn't the whitelisted bounce be marked differently? This relay string should appear in the Received headers of the *bounced* message, not of the *bounce* message. in other words, the message inside the bounce. That's why you use it to list your own outbound MTAs. --j. > Still rather confused... > > Steve
