Nathan wrote:
>>Michael Scheidell wrote
>>Look for policy banks, maybe MYNETS policy will help.
> I am looking into policy banks to see how I incorporate it into not scanning
> outgoing mail from authenticated relay clients. So is this message from
> amavisd-new? If so, why is it so hit and miss? What triggers the message?
> "A message from <[EMAIL PROTECTED]> to:
->> [EMAIL PROTECTED]
> was considered unsolicited bulk e-mail (UBE).
> Our internal reference code for your message is 16416-06/SxgoZ3XUffHr
> The message carried your return address, so it was either a genuine mail
> from you, or a sender address was faked and your e-mail address abused by
> third party, in which case we apologize for undesired notification.
> We do try to minimize backscatter for more prominent cases of UBE and for
> infected mail, but for less obvious cases of UBE some balance between losing
> genuine mail and sending undesired backscatter is sought, and there can be
> some collateral damage on both sides.
> First upstream SMTP client IP address: [xx.xx.xx.xx] myserver.myserver.tld
> According to a 'Received:' trace, the message originated at: [xx.xx.xx.xx],
> nobody
> Return-Path: <[EMAIL PROTECTED]>
> Message-ID: <[EMAIL PROTECTED]>
> Subject: Some Subject
> Delivery of the email was stopped!"
It's not hit and miss when you understand why it happens some times
and not others. The original message was considered spam (it
scored at or above $sa_kill_level_deflt). In the 'out of the box'
configuration amavisd-new will bounce spam messages due to:
$final_spam_destiny = D_BOUNCE; # (defaults to D_BOUNCE)
Also, the message must have scored below:
$sa_dsn_cutoff_level = 9; # spam level beyond which a DSN is not sent,
# effectively turning D_BOUNCE into D_DISCARD;
# undef disables this feature and is a default;
The sender gets the bounce notice.
The message may have been quarantined. If so, look in the quarantine
and read the headers of the message and see what the X-Spam-Status
shows (for the score and what SA rules hit). The recipient domain
must be considered 'local' in order for this header to get written.
In other words it should be included in @local_domains_maps or
similar mechanism.
This may be of some use in getting familiar with what is going on:
http://www200.pair.com/mecham/spam/amavisd-settings.html
Gary V
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
