Matthias wrote: > >Harald is partly right > >The problem about not being tagged is as Harald said, that kill level is >the same as tag2 level. >at tag level there are just some headers added (I've set that to -999 so >that i get headers in ANY mail) >at tag2 level it will modify the subject if told so >at kill level it will delete/quarantine/whatever the mails > >Since you have set kill level = tag2 level the tag2-actions (subject >change) are never triggered.... >Try setting it like >tag level : -999 >tag2 level : 10 >kill level : 20 >for a conservative start... >
Now you are partly right ;-) Since the final_spam_destiny is D_PASS the spam should get a ***SPAM*** header (tag2_level) and it should be forwarded to the user + the quarantine-dir (kill_level). There is nothing wrong with having kill_level==tag2_level, but I agree it is not so useful if you have final_spam_destiny=D_REJECT. I often use tag2_level=6.2 and kill_level=5.0 with final_spam_destiny=D_PASS. That way mail with scores between 5 and 6.1 is copied to the quarantine but is NOT tagged with **SPAM**. This gives me the opportunity to analyse why it scored 'almost spam' so I can adapt my rules even before it gets to false positives. In the log from Harold I only miss the line with SPAM-TAG, the rest looks the same as on my system.. Maybe a different version will help? I use Amavisd-new-20030616-p8 with the perl (install Mail::SpamAssassin) SpamAssassin version 2.63. Or maybe 'spamassassin --lint' or 'amavisd debug' will give some hints.. Regards Menno van Bennekom
