I wrote some new habeas rules, which take care of the recents
Habeas forgery :
# Jan 2004 : Fake Habeas
header __HABEAS_SWE eval:message_is_habeas_swe( )
header __HAB_FORGE_BOUND Content-Type =~ /boundary="--[0-9]{15,20}"/
header __HAB_FORGE_MID Message-ID =~ /<[A-Z]{20,[EMAIL PROTECTED]/
meta HABEAS_FORGERY (__HAB_FORGE_BOUND && __HAB_FORGE_MID &&
__HABEAS_SWE)
meta HABEAS_SWE (__HABEAS_SWE && ! HABEAS_FORGERY)
# -8.0 for default Habeas score.
describe HABEAS_FORGERY Common Habeas Forgery
lang fr describe HABEAS_FORGERY Spammeur utilisant Habeas sans autorisation
score HABEAS_FORGERY 3.5
(better to use them than desactivating the HABEAS_SWE rule).
--
Maxime Ritter
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
