Forum Discussion
Microsoft Defender for Email Whitelisting (Best Practice?)
Hello JimmyWork,
to be fair, the problem you describe is not yours to solve. If you have DMARC check enabled, you should kindly ask the client to include their 3rd party mail send infrastructure, it's their responsibility to hand over newsletters in a safe manner.
If this isn't possible, you could try adding a new mail flow rule, bypassing DMARC just for the domain of the newsletter and also whitelist it so it won't end up in the junk. But again, this should not be your problem, but the sender's.
Hope this helped.
Hello JimmyWork,
to be fair, the problem you describe is not yours to solve. If you have DMARC check enabled, you should kindly ask the client to include their 3rd party mail send infrastructure, it's their responsibility to hand over newsletters in a safe manner.
If this isn't possible, you could try adding a new mail flow rule, bypassing DMARC just for the domain of the newsletter and also whitelist it so it won't end up in the junk. But again, this should not be your problem, but the sender's.
Hope this helped.
What if I add the email to the whitelist, and have domain impersonation on the same domain or user impersonation, would I end up with the same issue as the DMARC is wrongfully configured by the 3rd party.
