DMARC / SPF / DKIM checklist

Vetrix doesn't send mail from its own domain by default — you configure an SMTP relay via the admin settings. Deliverability still depends on the configuration of the sending domain at the DNS level. This checklist covers the minimum.

1. SPF record

Publish a TXT record on the domain that appears in the SMTP From header authorising your relay's sending IPs:

@  IN  TXT  "v=spf1 include:_spf.sendgrid.net ~all"

Adjust include: for your relay (SendGrid, Mailgun, SES, Postmark, self-hosted Postfix with a static IP, …).

2. DKIM key

Generate a DKIM key pair with your relay. Publish the public selector as a TXT record:

s1._domainkey.<your-domain>  IN  TXT  "v=DKIM1; k=rsa; p=MIGf…"

Vetrix does not sign mail itself — the relay does. If your relay supports "SMTP submission with inline DKIM signing" (SendGrid + Mailgun do), no additional Vetrix config is needed.

3. DMARC record

Publish the DMARC policy:

_dmarc.<your-domain>  IN  TXT  "v=DMARC1; p=quarantine; rua=mailto:dmarc@<your-domain>"

p=none is fine during initial testing. Move to p=quarantine once the forensic reports show SPF + DKIM pass rates > 99%.

4. From display name

Set email.from_display_name to a human-readable identifier in /admin/settings:

Vetrix at example.com

The From header becomes "Vetrix at example.com" <noreply@example.com> — improves inbox presentation and makes Reply-To routing unambiguous.

5. Reply-To

When the relay's From address isn't monitored (e.g. noreply@), set email.reply_to so legitimate replies reach a human:

support@<your-domain>

Verification

After pointing Vetrix at the relay:

Configure settings, click Test SMTP — the smtp_test row in /admin/email/deliveries must go to status='sent'.
Send to a Gmail address — the received message's "Show original" page must show SPF: PASS, DKIM: PASS, DMARC: PASS.
Send to an Outlook address — the headers must show the same passes.

If any check fails, re-read the relay's onboarding docs; DNS propagation typically takes < 1 hour but can take up to 24.