Get your company implementing DMARC now…
During the past 5-6 years email industry efforts have been pushing the DMARC standard along. It provides the best widely supported and seemingly efficient way to – as a domain-owner – protect the domain from misuse and abuse in terms of spam and phishing attacks.
As sending email has often been a wild-west, and knowing who is a valid sender of email may prove a challenge for many companies – and as most IT developers does seem to care too much about the finer details of email (and production just as bad email headers as HTML markup 🙂 ), implementing DMARC protection on your domain may actually be a challenge.
The DMARC standard provide you 3 powerful tools:
- Using DMARC you have the power (through) DNS to declare which mail-servers are valid senders of email from your domain.
- The DKIM signing of mails allows your to prove to recipients it was sent from a valid server.
- Finally DMARC provides a way for the email receiver to report back to the sender about messages that pass and/or fail DMARC evaluation.
In summary, you have the option to protect the credibility of your domain (by not exposing it to spam and phishing), and you should care now, as Google through Gmail seems to be starting to push harder to signal which email is “safe” (or legitimate at least).
This latter effort will not only remove fake emails pretending to be from your domain, but it will likely also promote your legitimate emails and make them more likely to reach their audience.
Here are a few articles on how to get on with DMARC implementation:
- How to implement DMARC in your organization.
- How to eliminate spam and protect your name with dmarc.
- How to setup DMARC on Google Apps.