Missing MX records for em.atlassian.com

[Prem Chudzinski _extensi_]

Mails from community-do-not-reply@em.atlassian.com are being rejected by some providers as MX records are missing for em.atlassian.com

For example namecheap.com

User: remote
Domain:
Sender: community-do-not-reply@em.atlassian.com
Sent Time: May 2, 2017 10:55:22 PM
Sender Host: smtp.lithium.com
Sender IP: 208.74.204.5
Authentication: unauthorized
Spam Score: 0
Recipient: XZY
Delivery User: XYZ
Delivery Domain: XYZ
Delivered To:
Router: reject
Transport: *rejected*
Out Time: May 2, 2017 10:55:22 PM
ID: 1d5epw-000Afx-Bp
Delivery Host: smtp.lithium.com
Delivery IP: 208.74.204.5
Size: 0 bytes
Result: Sender verify failed

https://toolbox.googleapps.com/apps/dig/#MX/

for atlassian.com MX records are ok
id 42889
opcode QUERY
rcode NOERROR
flags QR RD RA
;QUESTION
atlassian.com. IN MX
;ANSWER
atlassian.com. 299 IN MX 10 mxa-001d9801.gslb.pphosted.com.
atlassian.com. 299 IN MX 10 mxb-001d9801.gslb.pphosted.com.
;AUTHORITY
;ADDITIONAL

for em.atlassian.com the MX records are empty
id 23501
opcode QUERY
rcode NOERROR
flags QR RD RA
;QUESTION
em.atlassian.com. IN MX
;ANSWER
;AUTHORITY
atlassian.com. 736 IN SOA ns10.dnsmadeeasy.com. dns.dnsmadeeasy.com. 2009013822 43200 3600 1209600 1200
;ADDITIONAL

Expected Result
send mailing from community-do-not-reply@atlassian.com

[Prem Chudzinski _extensi_]

Furthermore, an A record is missing as well

[Monique vdB]

Thanks! We think this is part of what is underlying the email delivery issues some users have been experiencing and are working with our DNS team to try and resolve.

Thanks for the detailed information, this is very helpful!

[Prem Chudzinski _extensi_]

https://ecosystem.atlassian.net/servicedesk/customer/portal/14/DEVHELP-535

[wroot]

Not sure if this is already fixed, but i have found messages from May 13 in my spam filter still referring to missing DNS entries. So i had to add Atlassian email address to the whitelist..

[Prem Chudzinski _extensi_]

Nope

[Monique vdB]

There is a cluster of issues that we believe are affecting email delivery.  I should be getting more information today; I don't know the details yet.  

[Prem Chudzinski _extensi_]

OK the issue has been resolved by adding the "A record".

I'm able to recieve community emails again on namecheap.com hosting.

Thx