People sometimes run into the "too many DNS lookups" error when rolling out SPF (Sender Policy Framework). It doesn't help that there is a lot of bad guidance on the Internet. This article describes how to fix this issue. Read the rest of this entry »
A common problem many people face when implementing DMARC for the first time is that they are not receiving aggregate XML reports (reports generated for delivery to the rua= tag) in their dmarcian account. These XML reports are the driving force of DMARC. Without them, it's very difficult to get an accurate picture of your domain's usage across the internet.
If you've created a dmarcian account, have published records but have not received data, don't fret! It is typically caused by one (or more) of these three things: Read the rest of this entry »
dmarcian tools are under constant development to make DMARC deployment faster and easier for everyone. This article describes how to best use the tools today. Read the rest of this entry »
A domain's DMARC record can tell the world to send DMARC reports to a different domain. For example, the domain example.org might have a DMARC record of:
v=DMARC1; p=none; rua=mailto:firstname.lastname@example.org
This DMARC record tells people to send reports regarding example.org to the email address of "email@example.com". Before reports are sent, sample.net must tell the world that it is OK to send example.org's reports to sample.net. Otherwise, reports will not be sent to sample.net.
Allowing "external" domains to accept DMARC reports is called "External Domain Verification".
Domain Groups allow dmarcian users to easily group together and manage related domains. Domain Groups are created using the Mission Control interface. Domain Groups are typically used to group together domains by: Read the rest of this entry »
dmarcian users can export Authentiscope data via CSV. When doing so, the CSV will contain the following columns: Read the rest of this entry »
To turn DMARC into something useful to people, dmarcian processes DMARC data using a big pile of rules. These rules identify sources of email, and dmarcian presents users with DMARC compliance information based on email source.
One identified source of email is called "SPF-Identified Servers", and dmarcian users are often curious as to how data ends up in this source. How and why this source works is explained below. Read the rest of this entry »
dmarcian maintains rules to classify DMARC data into 4 high level categories. Our categories are:
- DMARC Capable
- Non-compliant Sources