NevarMail

Domains

Set up sending domains with automated DNS record management for SPF, DKIM, and DMARC.

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. Detect which DNS records are needed based on your configured providers
  2. Generate the exact DNS records you need to add
  3. Monitor verification status automatically

DNS record setup

After adding a domain, you will receive a list of DNS records to add to your domain's DNS configuration. The records vary by provider:

SendGrid

  • CNAME records for DKIM authentication
  • TXT record for SPF

Mailgun

  • TXT records for SPF and DKIM
  • MX records for inbound routing (if using inbound features)

Amazon SES

  • CNAME records for DKIM (DKIM tokens)
  • TXT record for domain verification

Postmark

  • TXT records for SPF and DKIM
  • CNAME record for return-path

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)

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