> Ok, so @local_domains_maps is correct. > The 'X-Spam-Status: No' tells that spam score was below tag2 level > (where subject modifications start), and above tag level (which > enables adding X-Spam-* header fileds). Si in this case it was > normal that subject was not modified.
Thanks again, I had the tag2_level and the kill_level set at the same number, which made it impossible to get a mail with an altered subject line. It does work quite well, thanks again. Are there any recommendations at what level one should set the tag2_level in relation to the cut-off level. I have had a very strict setting of 5.5 for both of these, but the number of false positives had increased to an unbearable level for the users. Maybe 2-3 a week. My next step is to try the sql quarantine and then MailZu, so the users can take care of the problem themselves. Hopefully! Thanks, .peter ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ 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/
