|
Will,
Use Notepad to check the tail end of the file. The Declude
headers may be at the end of the file. If the Declude headers are at the end of
the file, note whether or not:
1. The Received: lines appear
normal
2. There may or may not be some X-Header lines immediately
after the Received: lines that appear normal
3. The From, To, Subject and body of the message all appear
to be on one or two lines in Notepad.
4. Followed by Declude headers
If the above is true, then:
1. The
message is in violation of RFC in that it is missing either carriage returns or
line feeds. The RFC calls for lines to be terminated by a carriage return/line
feed pair.
2. This is a known issue with Declude handling these
types of messages. Based on observation, it appears that Declude processes
messages in line-mode rather than byte-mode. Rather interesting that Declude
trusts spammers and virus writers to construct messages according to
RFC.
-----------------------------
Let me know what you
find.
While writing this message, I happened to think about
attachments. It would appear to me, that there is an implied possibility for
attachments and therefore viruses to pass through undetected. All that should
be required is that the lines that make up the entire email, including the
attachment section, be terminated with line feeds instead of carriage
return/line feed pairs. Under such condition, Declude would see only one line
and not find the relevant sections. I will test this
possibility.
Michael Thomas
--- 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. |
- [Declude.JunkMail] Declude 4.3.14 - Issues Andy Schmidt
- [Declude.JunkMail] Declude 4.3.14 - Issues Andy Schmidt
- [Declude.JunkMail] Suge of spam in recie... Will
- RE: [Declude.JunkMail] Suge of spam ... Michael Thomas - Mathbox
