It Keeps Coming
 

I keep getting bogus-- and virus filled-- messages supposedly from
Microsoft and the "Microsoft Security Corporation," etc. I set filters
in OE6 to never download these messages from the server, but it does
anyway. Can anyone tell me why the filter doesn't do what I tell it?
Thanks.

It Keeps Coming
 

No way to know since we don't see your message rule from here.

Also: You might want to consider anti-spam software.

---
Ted Zieglar
"Backup is a computer user's best friend."

Ron wrote:
I keep getting bogus-- and virus filled-- messages supposedly from
Microsoft and the "Microsoft Security Corporation," etc. I set filters
in OE6 to never download these messages from the server, but it does
anyway. Can anyone tell me why the filter doesn't do what I tell it?
Thanks.

It Keeps Coming
 

Not without knowing how you set up the rule, but here are some guidelines:

In general:

Have all rules that divert mail to folders first.

Delete it from server next.

All others last.

Make sure that every rule also has Stop processing more rules checked,
unless that option is grayed out.

How to set up OE Message Rules:
http://www.oeupdates.com/outlook-exp...lock-spam.html

http://www.timeatlas.com/mos/Email/O...tlook_Express/

http://www.jackieswebworks.com/outlo...ss%20notes.htm

Some Message Rule Ideas:
http://www.mindspring.com/~majik/messagerules.htm

Some tips:
http://insideoe.tomsterdam.com/tips/rules.htm

Message Rules not working?:
http://www.tomsterdam.com/insideoe/faqs/why.htm#rules
--
Bruce Hagen
MS-MVP Outlook Express
~IB-CA~

"Ron" wrote in message
oups.com...
I keep getting bogus-- and virus filled-- messages supposedly from
Microsoft and the "Microsoft Security Corporation," etc. I set filters
in OE6 to never download these messages from the server, but it does
anyway. Can anyone tell me why the filter doesn't do what I tell it?
Thanks.

It Keeps Coming
 

Ted Zieglar wrote:
No way to know since we don't see your message rule from here.

It was pretty straightforward: if from Microsoft (or anything with
Microsoft in it) *don't download from server.* But it ignores the rule
and lets the crap through anyway. I can route it to the delete folder
easily enough, but I rather not let it get that far in the first place.
Block sender doesn't work either.

Ron

It Keeps Coming
 

If it is a Subject rule, it should work. (See my reply). If it is a Message
Body rule, Delete it from server will not work because the message has to be
downloaded before the rule can see the text. So for that, Delete it & Stop
processing more rules is the best you can do.
--
Bruce Hagen
MS-MVP Outlook Express
~IB-CA~

"Ron" wrote in message
ups.com...

Ted Zieglar wrote:
No way to know since we don't see your message rule from here.

It was pretty straightforward: if from Microsoft (or anything with
Microsoft in it) *don't download from server.* But it ignores the rule
and lets the crap through anyway. I can route it to the delete folder
easily enough, but I rather not let it get that far in the first place.
Block sender doesn't work either.

Ron

It Keeps Coming
 

"Ron" wrote in message ups.com...

Ted Zieglar wrote:
No way to know since we don't see your message rule from here.

It was pretty straightforward: if from Microsoft (or anything with
Microsoft in it) *don't download from server.* But it ignores the rule
and lets the crap through anyway. I can route it to the delete folder
easily enough, but I rather not let it get that far in the first place.
Block sender doesn't work either.

Don't download it - kill it on the mailserver with MMM3:
http://mmm3.sourceforge.net/

It Keeps Coming
 

Bruce Hagen wrote:
If it is a Subject rule, it should work. (See my reply). If it is a Message
Body rule, Delete it from server will not work because the message has to be
downloaded before the rule can see the text. So for that, Delete it & Stop
processing more rules is the best you can do.

Interesting... But I had it set up as a From rule as it seems to be the
logical thing to do. Of course as somebody once said, "logic is the
science of being wrong with certainty."

Ron