DMARC error messages

 actually use I gmail where I have it forwarded to. Have for years. Just started having issues very recently.

DMARC tells the receiving server that the email is spoofed.  However, it does not distinguish spoofing for good versus spoofing for evil and doesn't make any allowances for the fact that someone may have spoofed their own address for years.

I spoofed email addresses in the 80s and 90s too.  Somewhere around 2010, I noticed that some emails were not getting through.  I believe some email systems were already doing ad-hoc spoofing detection at that time. DMARC has formalized this and is now becoming the norm.  In my case, I was spoofing my own address at my own domain, but I realized this was basically historical, going back to a time when SMTP had no authentication and ISPs were blocking port 25.  But these things had since changed so all I had to do was point my email client at the SMTP server for my domain, and my emails now pass DMARC.

actually use I gmail where I have it forwarded to. Have for years. Just started having issues very recently. It's always worked until very recently.

@ElRoc0_Tha_Gr81​ This would have started several months ago, presuming the destination honors DMARC.  Not all do, and therefore it may have continued to work until now.

I believe Gmail has an option to send messages through our platform when acting as "comcast.net".  If you can't find this option, let me know and I'll dig a bit more.

Good morning @ElRoc0_Tha_Gr81, I hope you are having a good weekend so far. There is some good information in the link that was posted by @BruceW. Have you tried using the Xfinity website to email and see if the issue is happening their also?

Not yet. I will and report back.

@ElRoc0_Tha_Gr81 Let us know how it goes.