V
Vanguard
I define a rule that checks for a word in the Subject header. The rule
can specify just the lowercase version of the word, say "word. When I
send a test message to myself, it can have "word", "WORD", "Word" or
other permutations and the rule will trigger on that message and perform
whatever action was defined within it. That's good because I certainly
do not want to create a list of multiple words or phrases to cover every
possible capitalization of individual characters.
However, I found that the clause "with <string> in the message header"
is case sensitive. As a test, I would send test messages from Hotmail
which inserts the "X-Originating-IP:" header in outbound e-mails sent
using their webmail interface. The rule was:
Apply this rule after the message arrives
with "x-originating-ip:" in the message header
delete it
and stop processing more rules
This rule will not fire on a test message sent from Hotmail. However,
if I change the condition clause to:
with "X-Originating-IP:" in the message header
then the rule does fire and the received message from Hotmail gets
deleted. This sucks. I certainly don't want to specify every
permutation of capitalization that could be used for the name of a
header.
My actual rule tests on the existence or lack of the "Message-ID:"
header but everyone here should be able to emulate the above test rule
using e-mails sent from Hotmail (or whatever header they want to test
against which uses mixed case). In my case, I was originally testing
against "Message-ID:". Most spam seems to neglect this optional header
(because they don't want to be identified and spam-friendly ISPs don't
want to identify their spamming customers, either), but most legit
e-mails do have this header (except bulk mailings, like newsletters, so
you'll have to whitelist them). I later received a non-spam e-mail with
"Message-Id:" as the header name so I added that. Then later I got
another non-spam e-mail with "Message-id:" as the header name. To cover
the most likely capitalizations, my clause now reads:
with "Message-ID:" or "Message-Id:" or "Message-id:" or
"message-ID:" or "message-Id:" or "message-id:" in the message header
This is getting ridiculous. Why is searching case-INsensitive for
strings in the Subject header or body but are case-sensitive for
searches in the message headers?
can specify just the lowercase version of the word, say "word. When I
send a test message to myself, it can have "word", "WORD", "Word" or
other permutations and the rule will trigger on that message and perform
whatever action was defined within it. That's good because I certainly
do not want to create a list of multiple words or phrases to cover every
possible capitalization of individual characters.
However, I found that the clause "with <string> in the message header"
is case sensitive. As a test, I would send test messages from Hotmail
which inserts the "X-Originating-IP:" header in outbound e-mails sent
using their webmail interface. The rule was:
Apply this rule after the message arrives
with "x-originating-ip:" in the message header
delete it
and stop processing more rules
This rule will not fire on a test message sent from Hotmail. However,
if I change the condition clause to:
with "X-Originating-IP:" in the message header
then the rule does fire and the received message from Hotmail gets
deleted. This sucks. I certainly don't want to specify every
permutation of capitalization that could be used for the name of a
header.
My actual rule tests on the existence or lack of the "Message-ID:"
header but everyone here should be able to emulate the above test rule
using e-mails sent from Hotmail (or whatever header they want to test
against which uses mixed case). In my case, I was originally testing
against "Message-ID:". Most spam seems to neglect this optional header
(because they don't want to be identified and spam-friendly ISPs don't
want to identify their spamming customers, either), but most legit
e-mails do have this header (except bulk mailings, like newsletters, so
you'll have to whitelist them). I later received a non-spam e-mail with
"Message-Id:" as the header name so I added that. Then later I got
another non-spam e-mail with "Message-id:" as the header name. To cover
the most likely capitalizations, my clause now reads:
with "Message-ID:" or "Message-Id:" or "Message-id:" or
"message-ID:" or "message-Id:" or "message-id:" in the message header
This is getting ridiculous. Why is searching case-INsensitive for
strings in the Subject header or body but are case-sensitive for
searches in the message headers?