Re: Display DCC results in headers
I dunno if anybody else will find this useful, but I made a modification to DCC.pm that will make it display the same DCC results via the SpamAssassin report that dcc would normally add in it's header. You probably ought to open a Bugzilla enhancement ticket for this and attach the patch. It sounds like something that others might want, and in a bug there will be a record of it. Loren
Display DCC results in headers
I dunno if anybody else will find this useful, but I made a modification to DCC.pm that will make it display the same DCC results via the SpamAssassin report that dcc would normally add in it's header. http://www.disco-zombie.net/tmp/dcc_header_plugin.tar.gz Normally, dccproc/ifd/whatever adds a header that looks like this: X-DCC--Metrics: lum 1049; Body=17 Fuz1=17 Fuz2=17 Done through SA, you just either trip the DCC_CHECK rule or you don't. My organization is going to be adding dcc to our mail system fairly soon, and we want people to be able to see the actual results, yet due to our mail system's current configuration, SpamAssassin is by far the best way to perform the DCC checks, so I just made SpamAssassin add the info... The results look like this: *2 DCC_CHECK Listed in DCC (http://rhyolite.com/anti-spam/dcc/) * [lum 1049; Body=1 Fuz1=1 Fuz2=many] or this: * -0.0 DCC_CHECK_NEGATIVE Not listed in DCC * [lum 1049; Body=16 Fuz1=16 Fuz2=16] If you only have the report header on when something is scored as spam, just apply the patch and you're set. Otherwise, just add the following scoring to one of your config files: score DCC_CHECK 0 1.37 0 2.17 full DCC_CHECK eval:check_dcc(0) describe DCC_CHECK Listed in DCC (http://rhyolite.com/anti-spam/dcc/) tflags DCC_CHECKnet full DCC_CHECK_NEGATIVE eval:check_dcc(1) describe DCC_CHECK_NEGATIVE Not listed in DCC tflags DCC_CHECK_NEGATIVE net score DCC_CHECK_NEGATIVE0 -0.0001 0 -0.0001 And since I'm not a fan of directly modifying my SA installation, I keep the modified DCC.pm in with my SA config and just specify the path. Anyway, like I said, dunno if anybody'll find it useful, but since I did it I figured I might as well share it just in case. I'm sure now that I've gone to the trouble somebody's going to point me to some "dcc_add_header 1" config variable that I overlooked. ;^) -- Gus
Display DCC results in headers
I dunno if anybody else will find this useful, but I made a modification to DCC.pm that will make it display the same DCC results via the SpamAssassin report that dcc would normally add in it's header. http://www.disco-zombie.net/tmp/dcc_header_plugin.tar.gz Normally, dccproc/ifd/whatever adds a header that looks like this: X-DCC--Metrics: lum 1049; Body=17 Fuz1=17 Fuz2=17 Done through SA, you just either trip the DCC_CHECK rule or you don't. My organization is going to be adding dcc to our mail system fairly soon, and we want people to be able to see the actual results, yet due to our mail system's current configuration, SpamAssassin is by far the best way to perform the DCC checks, so I just made SpamAssassin add the info... The results look like this: *2 DCC_CHECK Listed in DCC (http://rhyolite.com/anti-spam/dcc/) * [lum 1049; Body=1 Fuz1=1 Fuz2=many] or this: * -0.0 DCC_CHECK_NEGATIVE Not listed in DCC * [lum 1049; Body=16 Fuz1=16 Fuz2=16] If you only have the report header on when something is scored as spam, just apply the patch and you're set. Otherwise, just add the following scoring to one of your config files: score DCC_CHECK 0 1.37 0 2.17 full DCC_CHECK eval:check_dcc(0) describe DCC_CHECK Listed in DCC (http://rhyolite.com/anti-spam/dcc/) tflags DCC_CHECKnet full DCC_CHECK_NEGATIVE eval:check_dcc(1) describe DCC_CHECK_NEGATIVE Not listed in DCC tflags DCC_CHECK_NEGATIVE net score DCC_CHECK_NEGATIVE0 -0.0001 0 -0.0001 And since I'm not a fan of directly modifying my SA installation, I keep the modified DCC.pm in with my SA config and just specify the path. Anyway, like I said, dunno if anybody'll find it useful, but since I did it I figured I might as well share it just in case. I'm sure now that I've gone to the trouble somebody's going to point me to some "dcc_add_header 1" config variable that I overlooked. ;^) -- Gus
