Another way to help test that amavisd-new is writing something to the headers is to temporarily set $final_spam_destiny = D_PASS; and make sure you have enabled $sa_spam_subject_tag = '***SPAM*** '; and send yourself a spam message. You should get the message in your inbox with the subject line prefixed with ***SPAM***. If you send yourself the gtube string, you should do it from an account outside your network. One that you would typically not use to send mail to yourself. If you need the gtube string, I have provided it here: http://www200.pair.com/mecham/spam/gtube.txt The text on the Subject: line should not be removed by SpamAssassin.
According to the SpamAssassin documentation, an X-Spam-Checker-Version header will be written by SpamAssassin. Are you seeing this header? I will admit I am pretty much stumped at this point. If SpamAssassin is called after processing by amavisd-new, depending on spamassassin settings, SpamAssassin would likely write its own set of headers. If you are not seeing any of those either, I'm not sure what is going on. Also, in a test I did, with spamc/spamd running after amavisd-new (mail was detected as spam and passed to the recipient), the original message was defanged (included as an attachment in a spamassassin report). If spamassassin was called after amavisd-new, I would think there would be more evidence of it than simply having the X-Spam headers removed. For this reason, I'm not sure what is happening at this point, and I'm not seeing what I may have missed. Sorry Gary V _______________________________________________ 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/
