V
VanguardLH
Outlook 2013 x64
Windows 7 Home Premium x64
E-mail account type: IMAP
In just one of my IMAP accounts, when I modify or just touch
(double-click the rule and click Finish) a rule and then click Apply or
OK in the Rules and Alerts dialog, I get the following popup warning:
The rule has a condition that the server cannot process. The action
'stop processing more rules' will prevent all remaining server rules
from being carried out. Are you sure this is what you
want to do?
Yes No
Oh, yes, such an information alert ... not! Which rule? Which
condition? By selecting the first rule and clicking Apply (after
touching any rule), the blue highlighted first rule is no longer
selected and gray highlighting shows up on another rule. Maybe that's
the rule it is bitching about. Still there no information on what
condition that Outlook is bitching about.
I have no server-side rules. This is an IMAP account, not an Exchange
account. ALL rules are client-side rules. It's not like any rule I
define in Outlook is miraculously showing up in the filters defined up
on the server in my IMAP e-mail account.
Every one of my rules (except the last one) has the "stop processing
more rules" clause. That is to eliminate side effects from having the
rules OR'ed together past when a rule fires on a message. Once a rule
fires, I want its actions commited and no other actions. That means not
letting subsequent rule get exercised on the same message (even if their
conditions match).
I have a rule that deletes any e-mail that doesn't have an "@" in the
sender's e-mail address. If they don't put an e-mail address (which has
an "@" to delineate the left and right tokens) in their From header then
I don't want their e-mail. So it has a stop clause because none of the
following rules are applicable anymore. That rule looks like:
Apply this rule after the message arrives
assign it to the "No @ in From" category
and delete it
and mark it as read
except with "@" in the sender's address
stop processing more rules
Outlook doesn't bitch on that rule. It bitches on rules where all I'm
doing is ensuring a wanted e-mail sent to a specific alias (which gets
delivered to my account) stays in the Inbox (so no action is specified)
and gives me a popup alert about the new e-mail (versus the desktop
alert that fades away so it's not showing upon my return to the
computer). An example rule is:
Apply this rule after the message arrives
with <aliasmailaddress> in the recipient's address
play "youvegotmail.wav"
and display "<name> aliased message" in the New Item Alert window
and assign it to the "<name> aliased message" category
and stop processing more rules
That's the type of rule that Outlook is bitching about claiming it's a
server rule. Obviously this not a server rule. Defining it in Outlook
does not upload it to the e-mail account as a filter up there. This is
an IMAP account, not an Exchange account where Outlook can push up rules
into the Exchange account. There is no action defined in this rule.
The e-mail arrives in the Inbox, I want to be sure it stays there, and
really the point of this rule is to merely popup the alert window
(rather than rely on the desktop alert that fades away). It is somewhat
a whitelisting rule because when an e-mail is received into that IMAP
account that used a specific alias e-mail address that redirects to
there then I don't want to apply any other rules to that aliased
message. It showed up and that's all I want the rule to do other than
ensure no other rules get exercised on the same message.
This is a new problem. When I first defined these rules a week, or
more, ago then this popup warning did not show up. I noticed one rule
had an unwanted effect, fixed it, but then this alert popped up when I
clicked Apply or OK. The rule didn't change other than to add another
string to the "with <something> in the recipient's address" clause.
There is NOTHING in these rules that have the server do anything. I'm
not deleting e-mails, moving them, or anything that the server has to do
in synchronizing to the local message store in Outlook. The server
should see NOTHING of what this rule is doing. Everything these rules
do is at the client end.
I have the same type of rules for the other IMAP account and touching
them and clicking on Apply or OK does not popup this uninformative
warning window. I've tried deleting and recreating the rules but
Outlook continues to bitch on these type of rules for one IMAP account.
The part saying "The action 'stop processing more rules' will prevent
all remaining server rules from being carried out" is okay. That's what
the "stop processing more rules" clause is for. It's the "The rule has
a condition that the server cannot process" part that doesn't make
sense. For rules where the server would have to do something, like a
rule that deletes an e-mail, this warning doesn't appear. For rules
where the server would never experience any change to the e-mails up on
the server is when Outlook bitches about a condition the server cannot
process but the server never sees.
I disabled all rules in this IMAP account (Yahoo Mail) and create a new
rule. I started with a simple rule that did nothing other than shown
the New Item Alert window, so it looked like:
Apply this rule after the message arrives
display "test alert" in the New Item Alert window
Clicking Apply or OK did not bring up the warning window. I then added
the stop clause, as in:
Apply this rule after the message arrives
display "test alert" in the New Item Alert window
and stop processing more rules
No warning popup when I clicked Apply in the Rules and Alerts window. I
then added the "with <strings> in the recipient's address", as in:
Apply this rule after the message arrives
with "gobbletygook" in the recipient's address
display "test alert" in the New Item Alert window
and stop processing more rules
Clicking Apply then brought up the warning window about "the rule has a
condition that the server cannot process." Oh r-e-a-l-l-y. Just what
does the server have to do with a client-side rule that inspects the
content of the recipient's e-mail address (in the To/Cc headers)? So
Outlook is puking on a condition in a rule with which the server has no
involvement but claiming the server is involved. If I remove the stop
clause then the warning doesn't appear when clicking Apply; however,
that means subsquent rules may fire on the same e-mail resulting in side
effects in OR'ing together multiple fired rules.
Windows 7 Home Premium x64
E-mail account type: IMAP
In just one of my IMAP accounts, when I modify or just touch
(double-click the rule and click Finish) a rule and then click Apply or
OK in the Rules and Alerts dialog, I get the following popup warning:
The rule has a condition that the server cannot process. The action
'stop processing more rules' will prevent all remaining server rules
from being carried out. Are you sure this is what you
want to do?
Yes No
Oh, yes, such an information alert ... not! Which rule? Which
condition? By selecting the first rule and clicking Apply (after
touching any rule), the blue highlighted first rule is no longer
selected and gray highlighting shows up on another rule. Maybe that's
the rule it is bitching about. Still there no information on what
condition that Outlook is bitching about.
I have no server-side rules. This is an IMAP account, not an Exchange
account. ALL rules are client-side rules. It's not like any rule I
define in Outlook is miraculously showing up in the filters defined up
on the server in my IMAP e-mail account.
Every one of my rules (except the last one) has the "stop processing
more rules" clause. That is to eliminate side effects from having the
rules OR'ed together past when a rule fires on a message. Once a rule
fires, I want its actions commited and no other actions. That means not
letting subsequent rule get exercised on the same message (even if their
conditions match).
I have a rule that deletes any e-mail that doesn't have an "@" in the
sender's e-mail address. If they don't put an e-mail address (which has
an "@" to delineate the left and right tokens) in their From header then
I don't want their e-mail. So it has a stop clause because none of the
following rules are applicable anymore. That rule looks like:
Apply this rule after the message arrives
assign it to the "No @ in From" category
and delete it
and mark it as read
except with "@" in the sender's address
stop processing more rules
Outlook doesn't bitch on that rule. It bitches on rules where all I'm
doing is ensuring a wanted e-mail sent to a specific alias (which gets
delivered to my account) stays in the Inbox (so no action is specified)
and gives me a popup alert about the new e-mail (versus the desktop
alert that fades away so it's not showing upon my return to the
computer). An example rule is:
Apply this rule after the message arrives
with <aliasmailaddress> in the recipient's address
play "youvegotmail.wav"
and display "<name> aliased message" in the New Item Alert window
and assign it to the "<name> aliased message" category
and stop processing more rules
That's the type of rule that Outlook is bitching about claiming it's a
server rule. Obviously this not a server rule. Defining it in Outlook
does not upload it to the e-mail account as a filter up there. This is
an IMAP account, not an Exchange account where Outlook can push up rules
into the Exchange account. There is no action defined in this rule.
The e-mail arrives in the Inbox, I want to be sure it stays there, and
really the point of this rule is to merely popup the alert window
(rather than rely on the desktop alert that fades away). It is somewhat
a whitelisting rule because when an e-mail is received into that IMAP
account that used a specific alias e-mail address that redirects to
there then I don't want to apply any other rules to that aliased
message. It showed up and that's all I want the rule to do other than
ensure no other rules get exercised on the same message.
This is a new problem. When I first defined these rules a week, or
more, ago then this popup warning did not show up. I noticed one rule
had an unwanted effect, fixed it, but then this alert popped up when I
clicked Apply or OK. The rule didn't change other than to add another
string to the "with <something> in the recipient's address" clause.
There is NOTHING in these rules that have the server do anything. I'm
not deleting e-mails, moving them, or anything that the server has to do
in synchronizing to the local message store in Outlook. The server
should see NOTHING of what this rule is doing. Everything these rules
do is at the client end.
I have the same type of rules for the other IMAP account and touching
them and clicking on Apply or OK does not popup this uninformative
warning window. I've tried deleting and recreating the rules but
Outlook continues to bitch on these type of rules for one IMAP account.
The part saying "The action 'stop processing more rules' will prevent
all remaining server rules from being carried out" is okay. That's what
the "stop processing more rules" clause is for. It's the "The rule has
a condition that the server cannot process" part that doesn't make
sense. For rules where the server would have to do something, like a
rule that deletes an e-mail, this warning doesn't appear. For rules
where the server would never experience any change to the e-mails up on
the server is when Outlook bitches about a condition the server cannot
process but the server never sees.
I disabled all rules in this IMAP account (Yahoo Mail) and create a new
rule. I started with a simple rule that did nothing other than shown
the New Item Alert window, so it looked like:
Apply this rule after the message arrives
display "test alert" in the New Item Alert window
Clicking Apply or OK did not bring up the warning window. I then added
the stop clause, as in:
Apply this rule after the message arrives
display "test alert" in the New Item Alert window
and stop processing more rules
No warning popup when I clicked Apply in the Rules and Alerts window. I
then added the "with <strings> in the recipient's address", as in:
Apply this rule after the message arrives
with "gobbletygook" in the recipient's address
display "test alert" in the New Item Alert window
and stop processing more rules
Clicking Apply then brought up the warning window about "the rule has a
condition that the server cannot process." Oh r-e-a-l-l-y. Just what
does the server have to do with a client-side rule that inspects the
content of the recipient's e-mail address (in the To/Cc headers)? So
Outlook is puking on a condition in a rule with which the server has no
involvement but claiming the server is involved. If I remove the stop
clause then the warning doesn't appear when clicking Apply; however,
that means subsquent rules may fire on the same e-mail resulting in side
effects in OR'ing together multiple fired rules.