>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!" ------------------------------------------------------------------------- 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/
