Title: Message
Microsoft software is probably the "most guilty" for using the vague
application-octet-stream MIME type instead of something more explicit, like
application/msexcel. PDF is also very likely to come as a stream. I
place viruses and malware asa distant 3rd for using
stream.
As
,
AndrewSent: Wednesday, October 27, 2004 3:27 PMTo:
'[EMAIL PROTECTED]'Subject: RE: [Declude.JunkMail] Best
Practices for handing legit email fla gged as spam?
Microsoft software is probably the "most guilty" for using the vague
application-octet-stream MIME type instead of some
PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Colbeck,
AndrewSent: Wednesday, October 27, 2004 3:27 PMTo:
'[EMAIL PROTECTED]'Subject: RE: [Declude.JunkMail]
Best Practices for handing legit email fla gged as
spam?
Microsoft software is probably the "most g
Practices for handing
legit email fla gged as spam?
Microsoft software is probably the "most guilty"
for using the vague application-octet-stream MIME type instead of
something more explicit, like application/msexcel. PDF is also very
likely to come as a stream. I place viruses and
: [EMAIL PROTECTED]Subject:
RE: [Declude.JunkMail] Best Practices for handing legit email fla gged as
spam?
Problem was that this wasn't sent through Microsoft OL
it was sent through IMail's web interface.
Also, why would these content types go in the
Body?
Wouldn't they go
: Wednesday, October 27, 2004 4:44 PMTo:
[EMAIL PROTECTED]Subject: RE: [Declude.JunkMail] Best
Practices for handing legit email fla gged as spam?
Ok they're being displayed in the headers using Outlook
Peek.
Anyway...
For some reason the filter isn't
logging/catching.
If I
