Message Rules for headers (not email body) ...

I've been studying the raw messages and headers for my junk mail and come to
the conclusion that hugh percent of my legitimate email has "for
xxxxxx@yyyyyy.zzz" in the first "recieved:" header although some times that
first header is split into multiple lines.

The few ligitimate emails that didn't have my "for xxxxxxx@yyyyyyy.zzz" in
the header were from my ISP and Microsoft's email welcome message ... in
other words ... very ligitimate large vendors can get away with improper
headers, but there seems to be very few of them and they can be easily white
listed. Any email blasts from ligitmate sources still had the "for
xxxxxxxxxx@yyyyyyy.zzzz" because they have to play by the rules.

In various tests I've done ... it is clear that none of the standard rules
allow you to search the recieve header and it also probably doesn't support
a searching a string with a split in the header line. So even if a header
could be searched ... a string of "for xxxxxx@yyyyyyy.zzz" would fail if the
line split after the "for".

So bottom line, ... Microsoft ... I'd assume youy have notice this failing
so why don't you alllow rules for headers? If you do please tell me how and
if it properly search a split line. Or is ut that you do not think we are
not smart enough to use them or is it that you really want junk mail to
chase us?

Windows Mail/OE was designed for the light to moderate email user.
Microsoft considers filtering rules based on advanced headers to be
beyond the average user's capability. You would either have to
switch to a more capable email program like Eudora, or add a
third party spam blocker such as K9.

Gary VanderMolen

"Terry Schwarz" <terryschwarz@verizon.net> wrote in message news:ucf6KgrXHHA.3656@TK2MSFTNGP05.phx.gbl...
> I've been studying the raw messages and headers for my junk mail and come to
> the conclusion that hugh percent of my legitimate email has "for
> xxxxxx@yyyyyy.zzz" in the first "recieved:" header although some times that
> first header is split into multiple lines.
>
> The few ligitimate emails that didn't have my "for xxxxxxx@yyyyyyy.zzz" in
> the header were from my ISP and Microsoft's email welcome message ... in
> other words ... very ligitimate large vendors can get away with improper
> headers, but there seems to be very few of them and they can be easily white
> listed. Any email blasts from ligitmate sources still had the "for
> xxxxxxxxxx@yyyyyyy.zzzz" because they have to play by the rules.
>
> In various tests I've done ... it is clear that none of the standard rules
> allow you to search the recieve header and it also probably doesn't support
> a searching a string with a split in the header line. So even if a header
> could be searched ... a string of "for xxxxxx@yyyyyyy.zzz" would fail if the
> line split after the "for".
>
> So bottom line, ... Microsoft ... I'd assume youy have notice this failing
> so why don't you alllow rules for headers? If you do please tell me how and
> if it properly search a split line. Or is ut that you do not think we are
> not smart enough to use them or is it that you really want junk mail to
> chase us?
>