NevarMail

Set up SPF, DKIM and DMARC for your domain

Why mailbox providers need your domain verified, what records to add, and how to tell when it has worked.

Domains in NevarMail represent the sending domains you use for email delivery. Proper domain configuration ensures high deliverability and protects your sender reputation.

Why domain verification matters

Email providers and receiving mail servers use DNS records to verify that you are authorized to send email from a domain. Without proper configuration, your emails are more likely to be flagged as spam or rejected entirely.

NevarMail automates the setup of three critical DNS record types:

RecordPurpose
SPFSpecifies which mail servers are authorized to send email for your domain
DKIMAdds a cryptographic signature to verify message integrity
DMARCTells receiving servers what to do when SPF or DKIM checks fail

Add a domain

Navigate to the Domains page in the dashboard and add your sending domain. NevarMail will:

  1. Register the domain with your connected provider
  2. Fetch the exact DNS records that provider requires for this domain, live from the provider's own API
  3. Monitor verification status automatically

DNS record setup

After adding a domain, NevarMail shows you the exact DNS records to add to your domain's DNS configuration. These records are retrieved live from your provider at add-domain time -- NevarMail does not maintain its own static list of per-provider record requirements, since a provider can change what it requires. The records typically include CNAME entries for DKIM authentication and for the return-path (bounce) host your provider uses for SPF, but the specifics come from the provider's response.

DMARC

Your provider's records cover SPF and DKIM. DMARC is a record you publish about your own domain, and providers never check it, so a domain can show Verified with no DMARC at all. Gmail and Yahoo require a DMARC record from bulk senders.

Each domain card has a DMARC policy section, refreshed every time the domain is checked:

BadgeWhat it meansWhat to do
PublishedYour domain already has a DMARC record at _dmarc.<domain>, or a subdomain is covered by the record on its parent domainNothing. Keep your record as it is.
Duplicate recordsMore than one TXT record starting v=DMARC1 at the same name. Receivers ignore all of them, so no policy is in effectRemove all but one of them at your DNS provider
MissingNo DMARC record covers the domainAdd the TXT record shown: host _dmarc.<domain>, value v=DMARC1; p=none;
Not checkedThe domain hasn't been checked yetClick verify, or add the record if you know you have none

p=none turns DMARC on in monitor-only mode: it asks receivers to report and blocks nothing, so it is safe to add before you have looked at any traffic. Tighten it to p=quarantine or p=reject once your reports show only your own mail.

Getting DMARC reports

Receivers only send DMARC reports when the record names a mailbox for them with rua=. Enter one address under Report address (optional) in the DMARC section and click Save. Only members who can manage domains see the field. Leave it empty to remove it.

  • Your domain has no DMARC record: the recommended record gains rua=mailto:<address>;, for example v=DMARC1; p=none; rua=mailto:dmarc@example.com;.
  • Your domain already has a record: NevarMail leaves it alone and tells you to add rua=mailto:<address>; to it yourself.
  • The mailbox is on another domain (a reporting service, for example): receivers only send reports there if that domain allows it. Add a TXT record <your domain>._report._dmarc.<mailbox domain> with the value v=DMARC1; at the mailbox domain's DNS provider. The section shows the exact name.

The address must be a single email address. NevarMail never adds ruf= (forensic reports), because those carry copies of individual messages.

NevarMail never asks you to replace a DMARC record you already have. A domain must have only one: with two TXT records starting v=DMARC1 at the same name, receivers ignore both. If you already publish one, edit it rather than adding another.

When your DNS provider supports automatic setup, the Set up automatically button adds the p=none record for you, but only when no DMARC record covers the domain. If one already does, automatic setup adds only your provider's records and leaves DMARC alone.

Why there is no SPF record to add on your domain

SPF is checked against the envelope sender (the return-path), not the From address you see. Your provider sends from its own return-path subdomain, set up by the CNAME records above, and SPF passes there. DMARC then passes through DKIM, which is signed for your domain. An SPF TXT record on your From domain does nothing for mail sent through NevarMail. If your domain already has an SPF record for other mail (your office mailbox, for example), leave it alone, and never add a second v=spf1 record: two make SPF fail for everything.

Verification status

After adding DNS records, NevarMail periodically checks verification status. Domain states include:

StatusDescription
pendingDNS records have been generated but not yet verified
verifiedAll DNS records are correctly configured
failedDNS verification failed (records may be missing or incorrect)

Branded tracking host

A domain can carry a branded tracking host, url####.<your domain>, that the provider serves tracking from. Today it is used for one thing: open tracking on inbox mail, which is only allowed once the host is verified and serves HTTPS. Click Enable under Branded tracking host on the domain, publish the records shown, and turn on SSL for the link branding in your provider's settings. Verify re-checks both the DNS records and HTTPS.

Best practices

  • Verify before sending -- Always wait for domain verification to complete before sending production emails
  • Use a subdomain -- Consider using a subdomain like mail.yourdomain.com for transactional email to isolate your sending reputation
  • Monitor DNS -- DNS changes can take up to 48 hours to propagate, though most complete within minutes
  • One domain per use case -- Separate marketing and transactional email onto different subdomains for better deliverability control

On this page