Someone has to have an answer to this....Any MVS want to try???

[Rick]

I have created a rule for any rule with [Norton Antispam] be marked as read
but doesn't get marked read. If I manualy run the rule but on it's own it
doesn't?

My rule is as follows:

Apply this rule after the message arrives
with "Norton AntiSpam or [Norton AntiSpam] or *Norton AntiSpam* in the
Subject
Move it to Norton AntiSpam Folder and Mark it As Rea and Stop Processing
more rules.

I think the problem is unless the ENTIRE suject matches, the rule won't
apply. Is there a wildcard or away to get any message with [Norton
Antispam] to be marked as read? A wildcard to ignore [Norton Antispam] and
read another part of the subject?

I do have "stop processing more rules" checked.

Yes the rule is turned on.

Are Wildcards possible inside of rules?

Some MVS must know!

 

[Diane Poremsky]

does it get moved? The first or second conditions should work.

Oh, I think I see part of the problem - you need to mark as read before
moving. if you an reorder the actions, create two rules, one to mark as
read, the second moves and stops processing.

 

[*Vanguard*]

"Rick" said in news:[email protected]:

I have created a rule for any rule with [Norton Antispam] be marked
as read but doesn't get marked read. If I manualy run the rule but
on it's own it doesn't?

My rule is as follows:

Apply this rule after the message arrives
with "Norton AntiSpam or [Norton AntiSpam] or *Norton AntiSpam* in the
Subject
Move it to Norton AntiSpam Folder and Mark it As Rea and Stop
Processing more rules.

I think the problem is unless the ENTIRE suject matches, the rule
won't apply. Is there a wildcard or away to get any message with
[Norton Antispam] to be marked as read? A wildcard to ignore [Norton
Antispam] and read another part of the subject?

I do have "stop processing more rules" checked.

Yes the rule is turned on.

Are Wildcards possible inside of rules?

Some MVS must know!

The Subject header test clause is case insensitive and will scan for
substrings within the header. I don't know why you are testing on 3
substrings when just 1 will do as well.

Apply this rule after the message arrives
With "Norton AntiSpam" in the Subject
Move it to 'Norton AntiSpam' folder
And mark it as read
And stop processing more rules

You don't need to test on the same substring that is not enclosed in any
special characters, is enclosed within brackets, and is enclosed in
asterisks. Just test on the substring.

Personally I wouldn't even want Symantec to be continually spam me with
their 'Norton' product name for a folder name. There probably is no
real reason that the folder must be named "Norton AntiSpam" other than
their marketing wants it in your face everytime you have your e-mail
client opened. I'd rename it to just Spam so that any rule for another
anti-spam product will just use the same folder. Of course, there
really isn't any need for a new folder. Just use the Junk folder. I
configure my Junk folder to enable auto-archive which permanently
deletes messages in there that are over 2 days old, plus the Preview
mode is turned off for the Junk folder.

 

[*Vanguard*]

"Diane Poremsky" said in news:%[email protected]:

does it get moved? The first or second conditions should work.

Oh, I think I see part of the problem - you need to mark as read
before moving. if you an reorder the actions, create two rules, one
to mark as read, the second moves and stops processing.

When defining a rule and selecting which clauses to include, the user
doesn't get to specify the order of the clauses within a rule. There is
no way to "reorder the actions" within a rule. No matter in what order
you check the boxes to select the clauses, they always show up in the
same order in the rule. Also, they are AND'ed so it doesn't matter as
to their order. Clauses are AND'ed. Rules are OR'ed.

It should also not be necessary to define 2 rules, one for marking the
message as read (and NOT use the stop clause) following by another to
move the message. A single rule with both the move and mark-as-read
clauses should work. I use several such rules to for spam that gets
moved into the Junk folder which also gets marked as read.

I don't believe any wildcarding of strings is allowed in the rules.
However, I wouldn't put it past Outlook to screw up a substring with
leading or trailing asterisks. I also see no need to test on the same
substring 3 times within a rule. It is more likely that Rick has other
rules in front of this one that are causing the problem.

Rick might also be trying to manually test the rule after the message
already got moved. The rules only get exercised against messages in the
Inbox. If the message has already been moved to another folder, none of
the rules will get exercised on it there. You could have 2 rules, one
to move following by one to mark as read, but the handle to the message
is retained when making a pass through all the rules when applied
against each message. So when a pass is made through the rule list
against each message, moving a message from the Inbox won't bar the rest
of the rules from getting exercised against it. However, if the message
isn't in the Inbox when you [manually] run the rules list then they
won't find the message. The message has to start out in the Inbox.

 

[*Vanguard*]

"*Vanguard*" said in news:[email protected]:

"Diane Poremsky" said in news:%[email protected]:

does it get moved? The first or second conditions should work.

Oh, I think I see part of the problem - you need to mark as read
before moving. if you an reorder the actions, create two rules, one
to mark as read, the second moves and stops processing.

When defining a rule and selecting which clauses to include, the user
doesn't get to specify the order of the clauses within a rule. There
is no way to "reorder the actions" within a rule. No matter in what
order you check the boxes to select the clauses, they always show up
in the same order in the rule. Also, they are AND'ed so it doesn't
matter as to their order. Clauses are AND'ed. Rules are OR'ed.

It should also not be necessary to define 2 rules, one for marking the
message as read (and NOT use the stop clause) following by another to
move the message. A single rule with both the move and mark-as-read
clauses should work. I use several such rules to for spam that gets
moved into the Junk folder which also gets marked as read.

I don't believe any wildcarding of strings is allowed in the rules.
However, I wouldn't put it past Outlook to screw up a substring with
leading or trailing asterisks. I also see no need to test on the same
substring 3 times within a rule. It is more likely that Rick has
other rules in front of this one that are causing the problem.

Rick might also be trying to manually test the rule after the message
already got moved. The rules only get exercised against messages in
the Inbox. If the message has already been moved to another folder,
none of the rules will get exercised on it there. You could have 2
rules, one to move following by one to mark as read, but the handle
to the message is retained when making a pass through all the rules
when applied against each message. So when a pass is made through
the rule list against each message, moving a message from the Inbox
won't bar the rest of the rules from getting exercised against it.
However, if the message isn't in the Inbox when you [manually] run
the rules list then they won't find the message. The message has to
start out in the Inbox.

Okay, one caveat to my above statement. When the rule list gets
*automatically* exercised against each message, the message must first
be in the Inbox. When you manually run the rule(s), you get to select
the starting folder (and whether to include subfolders or not). So
manual execution can be different than automatic execution.

 

[Rick]

I have no choice. Gets sent there by Norton. It's also a needed folder
because that folder allows you choose that "this is not spam".

I had the 3 conditions trying to get one to work. Norton AntiSpam by itself
doesn't do the trick.