A transport rule doesn't behave as expected, another rule seems to override it
Exchange transport rules run in priority order. An earlier rule with 'stop processing' blocks later ones.
support/email-aflevering/transport-rules-conflictsteps: 4
Try this first
- Open Exchange admin, sort transport rules by priority
- Check which rules have 'Stop processing more rules' enabled
- Reorder so specific rules sit above generic ones
- Use message trace to see which rule actually fires
When to bring us in
If rules tangle: document everything in a spreadsheet before refactoring.
See also
- Our emails land in spam for some recipientsAlmost always an SPF, DKIM, or DMARC setting that is wrong or missing, or a sender name that mimics a well-known brand.
- Someone reports receiving phishing emails "from us"Read: spoofing. Someone is abusing your sender name, not necessarily your actual mailbox.
- An email bounces (NDR): delivery failedThe NDR text usually states the exact reason. Reading it is step one.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.