Thanks for the answers. I would imagine that it makes a lot of sense to limit it at 32 K. The root of my issue then becomes Microsoft Word's unbelievably bloated code. If they can't construct a simple E-mail without 500% overhead in their tagging, I can see why Linux people laugh about Window's performance. That message had 13,058 displayable characters with spaces without attachments, but it contained 83,023 characters with spaces counting the formatting code (the previous quoted number didn't have spaces included). That made a 13 K message 84 K. Geeze!

Matt



R. Scott Perry wrote:


Is there a limit to how far down a file the text filters will search?


Yes -- it will only check the first 32K of the E-mail.

Also, is there a fix available for the BADHEADERS 8400000a error? I get a decent number of these every day, and they're often false positives (as was discussed before). The message that I'm referencing failed because of both the text filter not hitting and that BADHEADERS issue (not RFC compliant, but supported functionality from popular mail clients).


That's something that we are currently investigating.

-Scott


--- [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.

Reply via email to