Daniel Quinlan wrote: > Read the documentation! Run "man Mail::SpamAssassin::Conf" or > "perldoc Mail::SpamAssassin::Conf" and look for "defang_mime". > Can we add a mime_defang section to the FAQ?
As far as I can tell, defang_mime has nothing to do with my question. In fact, I'm aware I have that option turned on and have read the complete documentation (I even drafted one section of it a few months ago). I want to know if anyone has written an eval rule to detect a situation where the spammer's encoding type does not seem to match the actual encoding of the body of the message. The messages I'm getting have an encoding type of text/html (from the spammer), are changed to text/plain by SA, but neither encoding type matches the encoding of the message body (base64), so none of the SA 2.31 body rules ever match the actual body (unless the body rule happens to match the subject, which isn't base64 encoded). I assume the spammers do this because outlook express or other mailers might try to auto-convert the body if it looks like base64 (either that or the spammer is quite stupid). My question has nothing to do with the fact that SA changed the content type of the message to text/plain. I'm quite pleased SA does that for me. If nobody has written such a rule already, I'll be happy to dig a bit into Perl and write one for my personal usage. Thanks, Erik ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
