Why would I monitor my eMail flow using DMARC reports

"Two days ago, a university discovered, through DMARC reports, that 30 million emails per day were being sent under their domain name, This was unknown to them and due to a DMARC policy of p=none, which allows domain spoofing." Most IT consultants will leave your DMARC policy to p=none.

"A small business we assisted was being 'spoofed,' leading to a tarnished reputation for their domains, resulting in their emails being ignored by some providers. This was indicated in the DMARC report as “provider” internal policy issue, despite the domain not being listed on public blacklists."

"Help! We are no longer receiving emails from the Contact Form.” The new web developer has implemented changes, and the emails now originate from a different IP address. Our tracking/Monitoring service detected this."

"Help! The ticket system is no longer operational.” Monitoring allow to see that tickets were no longer routed through the same provider and are not signed with DKIM, among other changes."

"Grrr, we are no longer receiving feedback from clients via eBay/Shopify/XYZ.” The platform used no longer directs traffic through the correct IP addresses."

“I just sent 500 emails that all went to people’s quarantine! “ - Normal, monitoring showed me that you sent it from a new eMail platform not specified in your configuration ( authorized email sources)

“our last eMail campaign was rejected from most people!” - Our DNS Monitoring service allowed us to be notified about a new DNS entry someone has created for your domain. Someone you hired(or you ?) added a 2nd DNS TXT (SPF) entry for some new Campaign tool you are using. It’s not technically permitted to have two DNS SPF(TXT) entries for your authorized eMail sources,

“Why suddenly, so many emails we’re sending are being quarantined? “ - When you configured your domain to be compliant, you were using Google Workspace to send eMail and Google was specified as an authorized eMail tool. You just started sending eMail using Microsoft M365 and we never authorized M365 to send eMail on behalf of your domain", tks to eMail monitoring service allowing us to notice that problem.

SOME MORE STORIES HERE : https://www.lastspam.com/blog/email-flow-monitorin-gservice