Mail Monitor -- Spam filter - Only one header of several is processed

Windows XP Professional SP1 US English
True Launch Bar 2.2
Mail Monitor 1.8.1 beta

I have a rule "Received Contains <some_substring>". An email comes that contains 3 Received: headers and only the third one contains <some_substring>. The message is not flagged. If I enter a rule that is matched by the first (topmost) Received: header, the message is flagged.

This bug will be fixed in the next version.

This bug will be fixed in the next version.

The problem seems to be still present in 1.9 beta, although I tested it on a "Contains regexp" condition this time. I might get the regexp wrong, but I expect that
[code]Received: from User (ppp067.mbit.ru [195.149.201.67])

Hi all.

I believe I have found a similar bug in v1.9.
I do not know if it has the same cause though, which is why I'm writing this post.

I tried to create a filter condition whereas if the "Received" field contains my email address but the "To" field doesn't, the email is deleted.
Explorer crashes as soon as I click "Ok".
After restart, the filter condition seems to have been created but does not work.
The email I created the condition from has two "Received" fields, the one containing the "for" value being the first one.

XP Home SP1 / TLB v2.2 / Mail Monitor v1.9

Yes I've reproduced this bug OK, new version will be released soon

"...new version will be released soon "

Great, thanks.

Another problem I'm affraid:
Some emails seem to load themselves automatically (the entire message).
I have not yet been able to find any pattern in this behavior.
Is this a feature I haven't found the setting for, or is it a bug?

One question: is there a way to save the email accounts settings?
It would make updating to new versions much easier.

Some emails seem to load themselves automatically (the entire message).
I have not yet been able to find any pattern in this behavior.
Is this a feature I haven't found the setting for, or is it a bug?

Mail Monitor load entire message if you are using filters by message body or attachments. So I recommend use this filters very carefully. Folow these recommendations:
1) Place all conditions with message body into separate rule and plase this rule at the bottom of the list. This will allow Mail Monitor filter messages by header fields and do not load some messages.
2) Use condition Max message size to disable too long messages to be loaded.
3) Turn on Free message body to free memory after filtering.



Edited By Yuri Kobets on Sep. 19 2003 at 13:12

Thanks for the quick reply, Yuri.

I was actually wondering how Mail Monitor could check the message bodies without loading them.

Sorry Yuri, me again. ???

I have move the three "Mail body contains.." conditions I am using to a new rule, and moved the rule at the bottom of the list.
I have just received an email which wasn't catched by any rules (and rightly so), and the message was automatically loaded.

Mail Monitor loads every message when check message body if this message was not satisfy any rules at the top. On the other side you've found one more bug. Free message body does not works if message is not satisfy conditions

"(By the way, notice that it is more customary to say "matches regexp"/"does not match regexp".)"

Centaur, I do not think it applies in this case, as only part of the text needs to match.
To be pedantic, it would have to be:
"Contains the matching regexp/does not contain..."

But I might be wrong though, which would explain why using " \$[:digit:]+ " does not flag subjects containing any amount in dollars.
Or is it a bug? ???

But I might be wrong though, which would explain why using " \$[:digit:]+ " does not flag subjects containing any amount in dollars.

try this expression:

Code:

\$[[:digit:]]+

This is more correctly because you define the set of digits.



Edited By Yuri Kobets on Sep. 21 2003 at 14:30

Thanks again for your quick reply, Yuri.
It is now working.

Centaur, I do not think it applies in this case, as only part of the text needs to match.

In classic regexp-matching software (meaning Perl) the relation "matches" is defined on pairs (string, regexp) so that S matches R if S contains a substring that exactly matches R. If one wants to test for an exact match but not substring match, one adds the beginning anchor ^ on the left and the end anchor $ on the right.

No doubt you're right Centaur, but most Mail Monitor users wouldn't know that "In classic regexp-matching software (meaning Perl) the relation "matches" is defined on pairs (string, regexp) so that S matches R if S contains a substring that exactly matches R." and might find a technically exact description confusing.
i.e, "I do not want the regular expression to match the subject, only part of it. ???"

So I'd vote for it to be left the way it is.