Pablo wrote: >> > Your situation is unclear. >> sorry my bad spelling. example.org is a local domain, and I am sending > mail >> from hotmail to example.org. >> >> When you say >> > everything works as expected, what particular behavior happens >> > that is working? Are you referring to the X-Spam headers getting >> > written?
> I found what was happening. Since I was running amavis-new on both machines > at the same ip-netblock, the first machine was reciving the email, and > tagging it as spam, and then relaying the message to the second machine. For > some reason, when the mail gets relayed to the second machine, amavis-new at > the second machine don't consider the email as spam, and then removes its > x-spam tags from header, since $remove_existing_spam_headers defaults to > enabled and there was no explicit option in the amavis-new. > So, I just added $remove_existing_spam_headers = 0 to the second machine so > it doesn't remove any x-spam tag and the "problem" disappears, tags are > where should be! > Since amavis-new is a very good tool for deploying a content filtering > gateway, shoulnd't the option $remove_existing_* defaults to disabled? > anyway, I just find it out when reading the amavisd.conf-sample file. > Thank you, > Pablo Typically you want to remove existing spam headers. These headers originate from somewhere other than your local machine and usually should not be trusted. After all, spammers can easily create these. You would not want to confuse programs like procmail with multiple X-Spam headers. The mail may have scored lower on your second machine, but the second machine should still create new X-Spam headers. The reason it is not is possibly due to it scoring below sa_tag_level (in other words you need to lower sa_tag_level on server A). I am going to assume you are using your server B as a secondary MX for your domain. On server A, one thing you might consider doing is bypassing spam checks (or bypassing amavisd-new) for mail received from server B. That way the X-Spam headers created by server B will not be touched and you will not have the possibility of having the Subject rewritten twice, so you will not get: ***SPAM*** ***SPAM*** Subject goes here It would also save processing power since the mail has already gone through spam checks once before, but of course it's your decision. I would also investigate why the spam scored lower on server A than it did on server B (when it was relayed from server B). It could be spamassassin's trusted_networks and internal_networks are not configured properly. Gary V ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ 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/
