Personal email setup for deliverability

SMTP, SPF, DKIM, and DMARC setup baseline before sending from production inboxes.

Why authentication matters for outbound

Mailbox providers score sender trust using DNS authentication and engagement signals. Misaligned SPF, missing DKIM, or absent DMARC increases spam-folder risk before your copy is even read.

SMTP connection baseline

Use authenticated SMTP with valid host, port, username, and app password or OAuth token. Keep TLS enabled and avoid sharing credentials across multiple senders or automation tools.

SPF record alignment

Publish one SPF TXT record authorizing your mail provider. The envelope sender domain should align with the visible From domain recipients see in their inbox.

DKIM signing

Enable DKIM selectors in DNS and verify signature pass rates on real sends after setup. Failed DKIM is a common reason legitimate B2B mail lands in promotions or spam.

DMARC policy progression

Start with monitoring mode (p=none), validate aggregate report quality, then move toward quarantine or reject once SPF and DKIM alignment is stable for 2-4 weeks.

Google and Microsoft specifics

Workspace and Microsoft 365 often handle SPF/DKIM when you send through their SMTP or Graph APIs, but custom SMTP relays and third-party tools still require explicit DNS records. After connecting a mailbox in your outreach tool, send seed messages to Gmail and Outlook test inboxes and inspect Authentication-Results headers.

Common deliverability mistakes

Teams frequently break alignment by using a marketing From domain with a different SMTP relay, rotating untested domains, or skipping DMARC until complaints appear. Fixing authentication after reputation damage takes longer than doing it correctly before day one.

Pre-launch checklist