How to fix dmarc policy none on Adobe Commerce (Magento)

Steps for Adobe Commerce (Magento)

1. Adobe Commerce sends transactional email via a configured SMTP server. Go to Admin → Stores → Configuration → Advanced → System → Mail Sending Settings and confirm you are routing through an authenticated SMTP relay (SendGrid, Mailgun, Amazon SES, etc.).
2. Complete DKIM setup with your SMTP relay provider and publish the DKIM public key DNS record they provide, plus add their include to your SPF record, at your DNS host.
3. At your DNS provider, edit the _dmarc.yourdomain.com TXT record — change p=none to p=quarantine.
4. Review rua reports (tools like EasyDMARC, Dmarcian, or Postmark's free report reader help), fix any misaligned senders, then change p=quarantine to p=reject.

What is dmarc policy none?

DMARC (Domain-based Message Authentication, Reporting & Conformance) is a DNS record that tells the world's email providers what to do when they receive an email claiming to be from your domain. The policy tag (`p=`) controls the action: `none` means "do nothing — just watch," `quarantine` means "send suspicious mail to the spam folder," and `reject` means "refuse to deliver it at all." Right now your record is set to `p=none`, which is a read-only monitoring mode — it collects reports but never protects anyone. Moving to `p=quarantine` and eventually `p=reject` turns DMARC into an actual shield against email fraud.

With `p=none`, anyone in the world can send email that appears to come from your domain — your customers' inboxes, your suppliers, even your staff — and mail servers will deliver it without question. This is the primary technique used in phishing and business email compromise (BEC) attacks, where criminals impersonate your brand to steal money or credentials from your customers. Beyond security, Google and Yahoo now require a DMARC policy (at minimum `p=none` with reporting, but ideally stricter) for bulk senders, and staying in monitor-only mode signals poor email hygiene that can hurt your domain's sender reputation and deliverability. Moving to `p=reject` demonstrably reduces phishing abuse of your brand, protects customer trust, and is increasingly expected by enterprise buyers and payment processors performing vendor security assessments.

See the complete Dmarc policy none guide for every platform and the full background.