For those who are using the BASE64 test and finding that you have to counterweight for Exchange Servers that uselessly encode plain ASCII messages, note that there is a new patch level:
HEADERS -10 CONTAINS Microsoft Exchange V6.0.6375.0 in addition to John Tolmachoff's research: HEADERS -10 CONTAINS Microsoft Exchange V6.0.5762.3 HEADERS -10 CONTAINS Microsoft Exchange V6.0.6249.0 Also note that a BASE64 encoded message will also trigger NOLEGITCONTENT if you use it penalize such messages in addition to its intended effect of rewarding legitimate messages... so your counterweight (-10 in my example) should equal your BASE64 plus your positive NOLEGITCONTENT weight. Andrew 8) p.s. Of course, YMMV. Exchange doesn't always encode a plain message in BASE64... --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
