U

Visitor

 • 

7 Messages

Tuesday, May 27th, 2025 5:10 PM

e-mail to msn.com bounces due to missing DMARC

Messages sent to msn.com on 5/26/2025 are bounced with this response (e-mail address edited to remove personal data):

SG1PEPF000082E8.mail.protection.outlook.com rejected your message to the following email addresses:

XXXXX (xxxxx@msn.com)
Your message wasn't delivered because the recipient's email provider rejected it.

SG1PEPF000082E8.mail.protection.outlook.com gave this error:
Access denied, sending domain [COMCAST.NET] does not pass DMARC verification and has a DMARC policy of reject. [SJ2PR20MB6636.namprd20.prod.outlook.com 2025-05-27T16:20:46.164Z 08DD99A7D0F89A78] [SG2PR06CA0219.apcprd06.prod.outlook.com 2025-05-27T16:20:46.271Z 08DD9C9A81E6A4A3] [SG1PEPF000082E8.apcprd02.prod.outlook.com 2025-05-27T16:20:46.273Z 08DD9A2A1761D63A]

Why does this happen and how can it be fixed?

Official Employee

 • 

946 Messages

2 days ago

Good morning @user_a3ee3e, and thanks for reporting your email issue. Are you getting this message for all emails you send to MSN accounts? 

Visitor

 • 

7 Messages

I have just one person with an MSN.COM address. I still get the DMARC error today. There is Diagnostic information for administrators included in the bounce message I can provide to you if that is of value.

Official Employee

 • 

110 Messages

I appreciate the info. Are these emails you're sending being sent directly from our Xfinity Connect email portal, or a third-party client service such as Outlook or Apple's native mail service?

Visitor

 • 

7 Messages

I normally use Thunderbird to send through Comcast's servers.

I just tried a test message from the Comcast web portal and I received a similar DMARC error message.

Official Employee

 • 

110 Messages

I appreciate you testing it on both! Based on the error messaging you're receiving, and the fact that you're getting the same error from the Xfinity Connect portal would definitely indicate there's some sort of filter set up from the recipients MSN side that isn't allowing the message to be received.

If this is the only email address that's populating that rejection error for you, you may want to test sending that same recipient a message from a second email if you can, or even ask if the recipient recently changed any of their email filtering settings. If this is an email address you've messaged before with no issue, especially recently, then there would be no reason why the message wouldn't be properly authenticated once sent as it's always been prior.

Visitor

 • 

7 Messages

The recipient says they have no filter rules and even claims they don't know how to setup a filter rule. After my last post I used my Gmail account to send a message and the recipient confirmed it was received. I also sent one from Yahoo Mail - no error bounce however I cannot verify it was received.

The prior e-mail I sent to the MSN.COM address was March 8, 2025, February 18, 2025, January 27, 2025 and a bunch of times in 2024.

I don't know what changes Comcast or Microsoft might make to their mail servers which would allow a message on 3/8/2025 to be delivered and messages after 5/25/2025 to be rejected.

The MSN.COM domain is an alias (I think that's the right term) for OUTLOOK.COM as I understand things. Is it possible the alias has something to do with the DMARC error?

Would you like the additional Diagnostic information included in the bounce message? 

forum icon

New to the Community?

Start Here