Spamassassin 3.02 rewrite_subject
I'm using Debian testing, before upgrading spamassassin used to rewrite the subject, I understand that it now works differently but for some reason its looks like its not doing things correctly
my local.conf
rewrite_header Subject ****SPAM(_SCORE_)****
required_hits 4.5
from my logfiles I can see doing the rewrite but it looks like its rewriting it with the original subject.
Mar 16 14:23:22 trinity sm-mta[1359]: j2GENAA5001359: Milter add: header: X-Spam-Flag: YES
Mar 16 14:23:22 trinity sm-mta[1359]: j2GENAA5001359: Milter add: header: X-Spam-Status: Yes, score=9.2 required=4.5 tests=NO_REAL_NAME,URIBL_AB_SURBL,\n\tURIBL_OB_SURBL,URIBL_SBL,URIBL_SC_SURBL,URIBL_WS_SURBL autolearn=no \n\tversion=3.0.2
Mar 16 14:23:22 trinity sm-mta[1359]: j2GENAA5001359: Milter add: header: X-Spam-Level: *********
Mar 16 14:23:22 trinity sm-mta[1359]: j2GENAA5001359: Milter add: header: X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on trinity.bdmedia.net
Mar 16 14:23:22 trinity sm-mta[1359]: j2GENAA5001359: Milter change: header Subject: from Delivery Status Notification (Failure) to Delivery Status Notification (Failure)\r
Mar 16 14:23:22 trinity sm-mta[1359]: j2GENAA5001359: Milter change: header Content-Type: from multipart/report; report-type=delivery-status;\n\tboundary="9B095B5ADSN=_01C50A887F1D9432000ABE2Cpdpsmb01.precisi" to multipart/mixed; boundary="----------=_4238415A.7B9029E1"
Mar 16 14:23:22 trinity sm-mta[1359]: j2GENAA500
Am I missing something? I'm also using spamass-milter if that has anything to do with it, but i was also using that beore the upgrade.
Gabe
Reply to: