New Function – DMARC Authentication
DMARC stands for Domain-based Message Authentication, Reporting and Conformance, and was created to reduce the abuse of emails. It is based on the well-known authentication technology used for SPF and DKIM. We have told you about these two things already in a previous article. But here you will find out why DMARC can improve your delivery rates even more.
DMARC is the icing on the cake
For those who wish to reach the highest conceivable number of recipients, it is time to employ the best technology. Aside from using whitelisted servers, technologies available today include SPF entries, the use of a Sender ID and DKIM. The next step after this is the use of DMARC technology.
A brief reminder:
With the SPF process (Sender Policy Framework), an entry is made in the domain settings of the owner, which allows certain IP address to send emails under the name of the email domain entered. The IP addresses are checked and this prevents emails being sent from a false / fake address. The address ‘check’ is made between the domain and the address registered with Return Path. In this way, the SPF process establishes who is allowed to send emails.
The Sender ID process is similar to the above, and necessitates an entry to be placed in the domain owner’s DNS settings, in order that outgoing emails can be authenticated. Sender ID authenticates the email by comparing the IP address of the sender with the alleged email address of the owner of the sending domain. For this, the ‘Header From‘ address is used. The Sender ID process is used by providers such as MSN or Hotmail.
The DKIM process (Domain-based Keys Identified Mail) attaches a signature to the email. The server that receives the email compares the signature with the matching public key. The key must already exist in the relevant domain DNS settings. If the signature and key match together successfully, the origin of the email can be verified. This makes it clear that the email stems from the sender and has not been tampered with.
The DMARC process is based on the SPF and DKIM technologies and raises standards. The DMARC process specifies exactly how the authentication process should take place. It does this by allowing you to specify whether one or both of the SPF and DKIM authentication processes should be passed.
Furthermore, the DMARC process offers a feedback channel for the sender. The sender can specify how the receiving server should react if the required authentication fails. DMARC can evaluate the email as completely authentic, providing the email passed the necessary test.
If the email is not judged as completely authentic, the owner can be informed of the possible misuse of their domain, for example.
Advantages of DMARC
Because DMARC is another authentication tool, the biggest benefit it yields is improved and optimised delivery rates. DMARC can prevent misuse of email through phishing, for example. Moreover, senders are forced to improve and develop their own IP reputation. This is advantageous for the sender and the recipient alike. If the email sender’s IP address is used by many different senders, this will affect (negatively) the IP’s reputation and therefore also the delivery rate of the other senders. Using your own IP will eliminate this issue.
Another advantage of DMARC is the feedback. Reports are generated and sent back to the sender. This allows misuse to be identified and holes in the authentication process to be located.
How do I use DMARC when sending my newsletters?
Because of the technical requirements involved, DMARC requires the use of a dedicated IP. Furthermore, authenticated dispatch requires a subdomain to be available from the main domain, in order that a reputation can be built up and the DNS entries to be made.
If you use a dedicated IP with Newsletter2Go, please contact our support team at any time so that they can set up DMARC authentication for you.
The use of DMARC without an own dedicated IP is unfortunately not possible for technical reasons.