Email forwarding exeption rule is not working

Question

I need assistance with an issue where an exception rule in Microsoft Outlook is failing to stop an automatic forwarding rule from triggering.

Here are the details of the rule configuration:

• Rule Name: Forwarding to Marketing Comms

Condition: Apply to all messages

Action: Forward to [Marketing Comms]

Exception: Except if Subject includes "Live Tomorrow: Spreadsheets Don’t Scale (Modern SAP Data Governance)"

Other settings: "Stop processing more rules" is checked.

The Issue:

Despite having set the exception criteria to exclude emails containing the specific subject line above, emails with that exact subject string are still being automatically forwarded to the designated recipient. The exception parameter seems to be completely bypassed by the rule engine.

Could you please investigate why this exception rule is not processing correctly, or let us know if there is a known service issue or workaround for this?

I have attached screenshots of the rule configuration for your reference.

Answer 1

Hi Liana, 

Thank you for reaching out and for sharing the screenshots. 

Based on your description, the issue could happen when the character stored in the exception doesn’t match the actual character from the message subject. Therefore, the exception never fires and the forwarding proceeds. 

In this situation, the apostrophe mismatch is the most likely culprit. When someone types the exception into the rule, the keyboard usually produces a straight apostrophe, while the sending system (a marketing or newsletter platform, based on the subject) almost always inserts a curly apostrophe. To the rule engine those are two different Unicode characters, so Don't in the exception will not match Don't in the actual email. 

The subject includes condition is also word based and ignores or mishandles leading special characters, so punctuation heavy strings with a colon, an em dash, and parentheses like yours are exactly the type that fail to match reliably. Instant Search and rule matching both struggle when a term begins with or contains special characters.

Encoding is the third factor. If the incoming subject is transmitted encoded (for example a header that starts with =?utf-8?B?), the raw subject the rule sees is not the readable text you typed into the exception, so the match fails on the original message even though it looks correct to the eye. This is a documented cause of subject rules not triggering on the original email. 

To resolve the issue, I recommend recreating the exception using a short piece of the subject that has no punctuation at all, for example "Modern SAP Data Governance". That keeps the match specific to this campaign while avoiding the apostrophe, colon, dash, and parentheses that tend to cause matching problems. 

If you would prefer to keep the apostrophe, open one of the emails you actually received, copy the word "Don't" straight from that subject line, and paste it into the exception field instead of typing it. That way the exact character from the real message is captured. 

I hope this information is helpful. Please follow the steps above and let me know if it works for you. If not, we can continue working together to resolve the issue.  

If you found the response useful, please consider marking it as accepted, as this may help other community members who are looking for similar guidance.  

Thank you for your patience and understanding. I look forward to continuing the conversation.  

---

If you have extra questions about this answer, please click "Comment". 

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.