Mistake: setting up SPF/DKIM but leaving DMARC at p=none

Mistake: setting up SPF/DKIM but leaving DMARC at p=none
People check the SPF and DKIM boxes, see green, and stop. DMARC sits at p=none or isn't published, so Gmail's stricter bulk-sender rules treat you as half-authenticated and quietly downrank.

The fix: publish a DMARC record and move to at least p=quarantine once your reports are clean. MXToolbox or Dmarcian validates alignment — the common trap is DKIM passing but not aligning to the From domain.

Pros / Cons of enforced DMARC:
— Pro: meets Gmail/Yahoo bulk-sender requirements
— Pro: blocks spoofers riding your domain
— Con: misconfigured alignment can quarantine your own mail
— Con: requires reading aggregate reports before tightening

Verdict: 4.5/5. Authentication isn't done at DKIM; alignment is the part everyone skips.

Who it's for: senders who 'set up authentication' a year ago and never enforced it.