I have a rule that fails to catch all the targeted mail in my InBox.

But if I then run the rule manually (with"Run Rules Now") the remainder of
the targeted mail in my InBox gets handled properly by the rule.

This inconsistancy between when the rule is run automatically and manually
is weird.

Anyone have any suggestions?

PS Outlook 2007 on Vista.

"Tom" wrote in message ...
I have a rule that fails to catch all the targeted mail in my InBox.

But if I then run the rule manually (with"Run Rules Now") the
remainder of the targeted mail in my InBox gets handled properly by
the rule.

This inconsistancy between when the rule is run automatically and
manually is weird.


You are running ONLY the one rule when you exercise it manually. That
means you are not also running all the other rules. Rules are
exercised in the order they are listed. You have prior rules that get
triggered and prevent or interfere with your later problematic rule.
You can change the order of your rules, or better analyze them to
determine what should be their proper order and if you are using the
correct conditions within your rules.

If you select ALL rules when you run manually, does the problematic
rule work or not?

If you select ALL rules when you run manually, does the problematic rule
work or not?

Yes, when I enable all rules and running them manually, the problematic rule
works.

Thanks.

Your message got me to thinking and I suspect that Outlook's built-in spam
detecting rules are superceding my rule.

Since a spammer starting spoofing my return address, I'm getting buried by
"bounced" messages: about 50/hour.

Outlook's internal spam detector is moving these messages to a "Junk"
folder.

However there are so many of them, that when reviewing the "Junk" folder, I
can't spot the handful of other email that sometimes is flagged as spam but
isn't.

I'm trying to create a custom rule that would automatically move these
messages to a "Bounced" folder rather than the automatic "Junk" folder.

So, I think your analysis is correct: another rule (Outlooks internal spam
detector) is getting to these emails first. I'm going to try turning off
Outlook's "Automatic" filtering (as much as I hate to) to see if my rule
then is applied. At least then I'll understand what's going on.

Tom wrote:

Yes, when I enable all rules and running them manually, the
problematic rule works.

It would help if you posted the exact rule text and an example of a message
you think should trigger it.
--
Brian Tillman [MVP-Outlook]

Tom wrote:

Your message got me to thinking and I suspect that Outlook's built-in
spam detecting rules are superceding my rule.

The Junk E-mail filter runs before the Rules engine. You can't change that.
You can, however, as you say, reduce the sensitivity of the Junk E-mail
filter or, if you find those messages, add the sender to your Safe Sender's
list (or in the case of a mailing list, add the list address to the Safe
Recipients list).
--
Brian Tillman [MVP-Outlook]

The only rule I have is:

Apply this rule after the message arrives
with 'undelivered' or
'Mail delivery failed' or
'Mail delivery failure' or
"FAILURE NOTICE' or
'Returned mail' or
'Undelivered:' or
'(Failure)' or
'Returned to Sender' or
'Undeliverable:' or
'undeliverable' or
'warning:' or
'Your message did not reach some or all of the intended recipients' or
'Undeliverable'
move it to the Spoofed folder

An example of email that is not having the rule applied:

From: System Administrator
Sent: Wednesday, October 24, 2007 2:15 PM
To: REDACTED
Subject: Undeliverable: French rock star Bertrand Cantat released from
prison


Your message did not reach some or all of the intended recipients.

Subject: French rock star Bertrand Cantat released from prison
Sent: 10/24/2007 2:25 PM

The following recipient(s) cannot be reached:

REDACTED on 10/24/2007 2:15 PM
The e-mail account does not exist at the organization this
message was sent to. Check the e-mail address, or contact the recipient
directly to find out the correct address.
back2server.back2.local #5.1.1

The above mail is ending up in my Junk folder, not the Spoofed filter. I
have set my Junk Mail to "No automatic filtering" I understand that even
with that settting, mail from blocked senders is still sent to the Junk
folder. But "System Administrator" does not appear in my blocked senders
folder. (In fact, appropriately, Outlook prohibits adding "System
Administrator" to the blocked senders folder.)

If I select "Run Rules Now," then the above e-mail is properly moved to the
Spoofed folder. So the rule is right. It seems like Outlook for some reason
considers this email as spam (even though I have "No automatic filtering"
selected) and pre-empting my rule...

Any suggestions?

Thanks for your help!

Tom

I omitted, when transcribing my rule in my previous e-mail, to type in the
words "in the subject"

"Tom" wrote in message ...
If you select ALL rules when you run manually, does the problematic
rule work or not?

Yes, when I enable all rules and running them manually, the
problematic rule works.


Then I would suspect you are attempting to exercise a rule that checks
for a string but within HTML-formatted e-mails. The string
"superfluous" is not the same as "superb/bfluous". While YOU
don't see the HTML formatting, especially because it toggles on and
off the bolding but affects no characters, your rule will still see
all the HTML tags. All HTML is plain text but e-mail clients will
attempt to render the HTML formatting which can mean some effects are
invisible to you.

You'll need to look at the raw source of the e-mail to see if the
string is actually in the one that you think your rule should trigger
on. If you are trying to trigger on spam words, and if they are
HTML-formatted e-mails, there are lots of ways of hiding those spam
words, like using abutting HTML tags, using tables, or other
formatting methods.

"Tom" wrote in message
...
The only rule I have is:

Apply this rule after the message arrives
with 'undelivered' or
'Mail delivery failed' or
'Mail delivery failure' or
"FAILURE NOTICE' or
'Returned mail' or
'Undelivered:' or
'(Failure)' or
'Returned to Sender' or
'Undeliverable:' or
'undeliverable' or
'warning:' or
'Your message did not reach some or all of the intended recipients'
or
'Undeliverable'
move it to the Spoofed folder


Wrong rule. Use the following which detects if it is a *valid* NDR
(non-delivery report) by checking for the header.

Apply this rule after the message arrives
with "report-type=delivery-status" in the message header
and move it to the Junk folder (or wherever you want)
and stop processing more rules

You neglected to include the stop-clause. You are also attempting to
trigger on the various comments that a mail server *might* insert in
the body to denote the cause of the NDR. Trigger on the header.