Forum Discussion
Solved
Exchange Rule Flow exception not working
Hi everyone,
I'm relatively new to all of this. Recently, we've had an influx of phishing attempts where a random third party email with the display name of a particular co-worker will prompt new hires to send personal info. Warning new employees and prepending warnings into the subject and body hasn't stopped them from responding to the phishing attempts, so I started to route any external email with that display name to myself where I can look at them and forward them on if they are legit. I've created some exceptions where we use a site that will send something on their behalf (such as asking to sign a document, etc), but the exceptions don't get honored, and they still all get routed to me. Does anyone have any idea why the exceptions aren't working?
Attached below is a screenshot of the setup. Thanks for any insight you may have!
Bryan
- I would suggest using the same type of condition for both the match and don't match logic, and also make sure that the "Match sender address in message:" option is set to Header and Envelope. You can also enable auditing on the rule and run some message traces to see what's happening.
2 Replies
- I would suggest using the same type of condition for both the match and don't match logic, and also make sure that the "Match sender address in message:" option is set to Header and Envelope. You can also enable auditing on the rule and run some message traces to see what's happening.
- Thanks for your response Vasil!
Updating the "Match sender address in message:" from Envelope to both Header and Envelope seems to have been the fix.
