Jonas Eckerman wrote:
John Rudd wrote:
static-70-21-118-207.res.east.verizon.net.
So, I've been considering moving those checks to filter_end and having
it generate tags that indicate the message should be treated as spam
instead of being rejected.
What works fine for me is to do this checks just before calling
SpamAssassin and add the result as headers to the mail that SpamAssassin
checks.
This way I can have SpamAssassin rules scoring for things that looks
like dynamic or dul hostnames. So a dynamic looking host name in itself
won't stop a mail from beeing received, but it will increase the
likelyhood of the mail beeing rejected.
(This kind of thing is why I patched mimedefang.pl so I can add my own
headers to SpamAssassins input.)
I've just created a SpamAssassin Plugin that does it in SA directly.
I'm still testing it. I'll put the code up for review soon.
John
_______________________________________________
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID. You may ignore it.
Visit http://www.mimedefang.org and http://www.roaringpenguin.com
MIMEDefang mailing list [email protected]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
