Robert wrote: > I've been trying to find the answer to this question, but I must not > be looking in the right places. I'm not even sure if this is a > Postfix or amavisd configuration issue.
> We are running Postfix 2.2.1 with MySQL, SpamAssassin, ClamAV and > amavisd-new 2.3.3. Courier-IMAP is the delivery system. The system > supports about 30 virtual domains right now and users are very > happy. Spam messages are flagged, but not quarantined. There are > no Linux system user accounts - everything for Postfix domains, > users, aliases, user-specified spam settings, vacations, etc. is > located in the MySQL database. > The problem, I think, is that mail addressed originally to alias > addresses is not being filtered for spam or viruses. For example, > many domains have an alias like [EMAIL PROTECTED] that is delivered > to a real mailbox like [EMAIL PROTECTED] It seems like mail > addressed to the info address does not get filtered properly. So > while most users rarely if ever see unflagged spam, the users who > are responsible for the info address get a lot of spam. We've > looked at those message headers and they don't have the SpamAssassin > spam score header. > Am I interpreting this problem correctly? Is there an amavisd > configuration controlling scanning of mail to aliases, or is this a > problem with my Postfix configuration? > Thanks. My thoughts would be the aliases are not in amavisd-new's users table and the domains are not in @local_domains_maps so the recipients are not considered local which would prevent the changes to the headers. Any address like info@ or sales@ will get a lot more spam that other accounts because these are extremely common user names. read all of http://www.ijs.si/software/amavisd/README.postfix.txt and notice you can configure your system: TO DO 'VIRTUAL ALIAS' MAPPING AND OTHER POSTFIX CLEANUP PROCESSING BEFORE OR AFTER CONTENT FILTERING? I think if you observed the log (and possibly temporarily increased $log_level) that you would probably see that mail addressed to info@ is getting scanned, but it is not getting tagged. I might first try simply adding all the domains to @local_domains_maps, but I'm not sure this will work if you have catchall users like '@.' or '@example.com' who's user.local field is set to 'N'. There may be an advantage to having a separate info@ user so you can create a little stronger spam policy for that particular recipient if desired. Gary V ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
