Technical Email Strategy DMARC Project Guide

Implementing a compliant DMARC DNS entry that protects your domain from SPOOF attack and therefore reduces organisational risk will adversely effect your email reputation if not implemented correctly. Being the first email service provider to have mandated DMARC in 2017 we have had more experience than most so we wanted to share this guide to help you on your journey.

DMARC Project Guide

Technical Email Strategy

Put as much mail through one source as possible (not via the MX). For example notifications, invoices, web sign-ups, Apps, campaigns etc should all go through an MTA. By splitting these functions you are reducing the consistency of regular email and by doing so you are making it very easy for email administrators to block or disregard your email.

The mail receivers don’t like campaign only email sources, it will hurt your domain reputation or at very least it will fluctuate and confuse analysis. By having too many sources of email you will not be able to pinpoint where reputational damage is occurring.

We do NOT recommend a dedicated IP address for under 750,000 million emails per month. Even then 1.5 million makes more sense. Why? Because when you have a dedicated IP you should use RDNS and that means you must register and manage the feedback loops etc.

Finally, do an audit of your apps and make sure you can route the emails via an SMTP gateway that is connected to your campaign platform, try and avoid CNAME SPF as it oftem causes SPF errors.

Too many sources will hurt reputation