Milo: Why might a rule I set up not be followed?

[Guest]

I created a rule in Outlook such that certain words in the subject line
should cause the mail to go to a certain folder. And sometimes they do. But
often they don't. Why might a properly spelled word in the subject line not
follow the rule?

 

[Brian Tillman]

I created a rule in Outlook such that certain words in the subject
line should cause the mail to go to a certain folder. And sometimes
they do. But often they don't. Why might a properly spelled word in
the subject line not follow the rule?

Post the exact definition of your rule and an example of a subject that you
believe should work but doesn't. (I suspect I know the answer, but your
information will tell me for sure.)

 

[Guest]

I cleared out my inbox spam already before seeing your response so I'll have
to wait til I get a bit more to post them exactly, but here's the rule for
now (it won't let me cut and paste, but I'll give you a subset of the words
as an idea):

Apply this message after the mail arrives
with 'Viagara' or 'Viagra' or 'OEM' or '0EM' or 'pharmacy' or 'pharmaceutical'
in the subject
and on this machine [what DOES that mean anyway? I only have one machine]
move it to the Patterns folder

Pattern is my folder for junk mail that I don't even have to peruse for real
stuff because it meets the junk criteria.

Also, the built in JunkEmail program that I use seems to have higher
priority than my Rules. It's nice that some thing with OEM are caught, but
I'd rather my rule put them in Pattern than the "Junk Email" folder that I
have to go through carefully to make sure I don't miss client stuff.

Bottom line, though: Subject lines with Pharmacy, OEM, 0EM, etc are
sometimes still going into my Inbox.

 

[Brian Tillman]

I cleared out my inbox spam already before seeing your response so
I'll have to wait til I get a bit more to post them exactly, but
here's the rule for now (it won't let me cut and paste, but I'll give
you a subset of the words as an idea):

Apply this message after the mail arrives
with 'Viagara' or 'Viagra' or 'OEM' or '0EM' or 'pharmacy' or
'pharmaceutical' in the subject
and on this machine [what DOES that mean anyway? I only have one
machine] move it to the Patterns folder

When you have a machine not connecting to Exchange, you are correct that all
rules are client-side rules, so all rules contain "on this machine"
implicitly. However, some rules will say "on this machine" explicitly
because they could be only a client-side rule. For any rule that references
a local PST (which is where your "Patterns" folder resides), Outlook will
add this condition automatically.

Pattern is my folder for junk mail that I don't even have to peruse
for real stuff because it meets the junk criteria.

Make sure you include the "stop processing more rules" action if you have
other rules that follow this one.

Also, the built in JunkEmail program that I use seems to have higher
priority than my Rules. It's nice that some thing with OEM are
caught, but I'd rather my rule put them in Pattern than the "Junk
Email" folder that I have to go through carefully to make sure I
don't miss client stuff.

This is correct. The built-in Junk E-mail filter runs before your rules.

Bottom line, though: Subject lines with Pharmacy, OEM, 0EM, etc are
sometimes still going into my Inbox.

If you have any rules in addition to the one you described, not having the
"stop processing more rules" action can cause the effect you see.

 

[Guest]

I've added that to each rule now (had never heard of that before). Will see
if things improve!

Isn't there any way to say "My rules come before the JunkEmail filter"?
Seems like that would be a given for situations where you wanted to be sure
to avoid the spam filter for real email, for instance.

Actually, I'm kind of amazed that privately chosen rules aren't the DEFAULT
for coming before the Junk sorting.

Thanks!

I cleared out my inbox spam already before seeing your response so
I'll have to wait til I get a bit more to post them exactly, but
here's the rule for now (it won't let me cut and paste, but I'll give
you a subset of the words as an idea):

Apply this message after the mail arrives
with 'Viagara' or 'Viagra' or 'OEM' or '0EM' or 'pharmacy' or
'pharmaceutical' in the subject
and on this machine [what DOES that mean anyway? I only have one
machine] move it to the Patterns folder

When you have a machine not connecting to Exchange, you are correct that all
rules are client-side rules, so all rules contain "on this machine"
implicitly. However, some rules will say "on this machine" explicitly
because they could be only a client-side rule. For any rule that references
a local PST (which is where your "Patterns" folder resides), Outlook will
add this condition automatically.

Pattern is my folder for junk mail that I don't even have to peruse
for real stuff because it meets the junk criteria.

Make sure you include the "stop processing more rules" action if you have
other rules that follow this one.

Also, the built in JunkEmail program that I use seems to have higher
priority than my Rules. It's nice that some thing with OEM are
caught, but I'd rather my rule put them in Pattern than the "Junk
Email" folder that I have to go through carefully to make sure I
don't miss client stuff.

This is correct. The built-in Junk E-mail filter runs before your rules.

Bottom line, though: Subject lines with Pharmacy, OEM, 0EM, etc are
sometimes still going into my Inbox.

If you have any rules in addition to the one you described, not having the
"stop processing more rules" action can cause the effect you see.

 

[Brian Tillman]

Isn't there any way to say "My rules come before the JunkEmail
filter"? Seems like that would be a given for situations where you
wanted to be sure to avoid the spam filter for real email, for
instance.

No, there's no way.

Actually, I'm kind of amazed that privately chosen rules aren't the
DEFAULT for coming before the Junk sorting.

Before Outlook 2003 SP1, rules ran before the junk mail filter. So many
people complained that junk got moved to their folders that Microsoft
changed the behavior.