whitelisting e2ma with microsoft EOP

  • 0
  • 1
  • Question
  • Updated 2 years ago
  • (Edited)
Archived and Closed

This conversation is no longer open for comments or replies and is no longer visible to community members. The community moderator provided the following reason for archiving: EOL Clean up

I'm am like 1 week experience with EOP and attempting to whitelist.

I am seeing the infamous 550 4.3.2 dropped messages in my traces. I have added e2ma.net to domain allow list in spam filter under protection. I have also added the listed ip ranges into my anti-spoofing rule as exceptions. (pri 0) I added a rule apply if sender domain is e2ma.net set scl bypass (pri 1). I still am seeing the drop message above. anyone have an example rule/guidance/anything?

I'm not confident I have the last rule built properly. well, I'm not confident I have any of the rules built properly but the anti-spoof seems to work for all BUT emma.


Photo of Steven Kiergaard

Steven Kiergaard

  • 3 Posts
  • 0 Reply Likes

Posted 2 years ago

  • 0
  • 1
Photo of Alyssa

Alyssa, Employee

  • 3 Posts
  • 0 Reply Likes
Official Response
Hi Steven, 

My name is Alyssa and I'm on the Deliverability team here at Emma.

While this issue is tough to diagnose because it is occurring within Microsoft, we have an idea of what could be happening. It sounds like you are setting up a rule for Microsoft to bypass SCL when the sender domain is e2ma.net. While the return-path domain is e2ma.net, Microsoft might be checking the friendly from-address, which will be the domain that your organization uses to send mail through Emma. Could you try bypassing SCL for whichever from-domain you are sending your Emma emails from?

You might have already seen this, but this is an article by Microsoft on how to bypass SCL: https://technet.microsoft.com/en-us/library/dn798345

If you see any email come through to the Junk or Spam folder, it will be super helpful if we can obtain the long header information for that message: https://support.office.com/en-US/article/View-e-mail-message-headers-CD039382-DC6E-4264-AC74-C048563D212C . This information will help us analyze the way that Microsoft is interpreting your message and its headers.

Ultimately, consulting with Microsoft will be the best way to resolve the issue with them. But please feel free to reach out to delivery@myemma.com if you have any further questions!