Most of our customers do not need to do anything because of this change.

That is the most important thing you need to know. The second most important thing to know is that you should not add a DMARC policy to your domain without coordinating with Trail Blazer.

In the coming weeks we will release some more information regarding DMARC and its associated components. If you opt to configure DMARC on your domain, we can provide some guidance. For now, we want to ensure that no one is configuring DMARC without an understanding of how that can impact your mass email campaigns.

The shortest way to explain DMARC is that it tells email servers to accept, quarantine, or reject emails from your domain when the message is sent from a server that you have not specifically authorized.

The intent is to prevent someone from spoofing your domain and summarily using it to trick the recipient into providing sensitive information because they believe they are communicating with someone that they trust.

Our default setting for sending mass emails is for us to send it on your organization’s behalf from one of our domains (tbmail2.com). Our DMARC records are configured correctly and have been for many years. If your organization or campaign uses our default settings, you do not need to change anything because we have taken care of it for you.

In short, again, you do not need to do anything if you have not implemented DMARC on your domain already.

If your organization implements DMARC without coordinating with Trail Blazer, it is highly probable that your messages will get rejected or quarantined by the receiving server. It is almost certain they will get rejected or quarantined by Gmail, Yahoo!, Microsoft, etc. Your organization must add content to your DNS records that authorizes our servers to send on your behalf when DMARC is added.

If you would like to implement DMARC for your domain please contact our Systems Administrator, Kevin Piatt by dialing our general support number (above) or via email: kpiatt@trailblz.com. There are several benefits to implementing it on your domain, but, and we cannot stress this enough, it is not required when sending emails through Trail Blazer.