Quote:
Originally posted by RickJ:
First, let me apologize for my erroneous conclusion.
|
No problem. I'm sure we've all done something similar. At least, I know *I* have.
Quote:
Here's what I did for my test:
Using Thunderbird Mail, I composed a message with the phrase "would you li<!garbagetag>ke to be financially independent." Then, using the program's formatting options, I sent this message to myself as "plain text only" and as "rich text (html) only." Only the message that was sent as HTML got through EFM's filter. I did check the headers on the message and confirmed that "Content-Type: text/html; charset=us-ascii" was in it. Hence, I thought the message was HTML.
However, it turns out that Thunderbird changed the "<" and ">" symbols to "<" and ">" prior to sending it;
|
Well, near as I can tell, the message
indeed was HTML. However, the "tags" were not tags. They were less than and greater than symbols.
Quote:
|
...that's why EFM didn't block the "HTML" message.
|
What do you mean "block"? Do you mean strip the tag out? Block means something else to someone writing email filters.
Quote:
My mistake for not checking further into the actual source code of the message. Sorry.
|
Important lesson to learn. When writing email filters, you should always examine the source of the email that you are trying to filter (or not filter, as the case may be). Email clients often do some kind of transformation or rendering (and especially with HTML versions) that are not strictly equivalent to the message source.
Quote:
|
But now I have a different question: why is EFM ignoring my garbage tags properly but not those from a spammer?
|
I am assuming by "garbage tags" that you mean this:
Code Sample: would you li<!garbagetag>ke to be financially independent. |
|
EFM would have no idea whether you or a spammer sent the email, so that can certainly not be the distinguishing factor. Something else must be the factor.
The only way to answer a question like this is to have an exact copy of the raw email source plus an exact copy of the email filter data file from EFM at the time the message was run through it. Anything else is conjecture.
-- I'm fairly certain there is a logical explanation. I just don't know what it is...