Skip to content
Comcast (Xfinity)

ODM00001: rejected by Xfinity's own DMARC policy

Xfinity's outgoing mail servers refused the message under Xfinity's own published DMARC policy, because it passed neither DKIM nor SPF for the domain.

Comcast
Provider
Sources checked
Author

At a glance

Code
ODM00001
Who has to act
The sender. The fix is on the sending side: your domain, your server or your list.

What it means

ODM00001 comes from Xfinity's outbound mail servers, the ones Xfinity customers send through. Xfinity says the message was refused under its published DMARC policy because it passed neither DKIM nor SPF for the domain. DMARC needs at least one of the two to pass, aligned with the domain in the From address, so a message that fails both counts as unauthenticated. Xfinity does not list what usually triggers it, so the cause has to be found by comparing the From address with the server and account the message actually went out through.

Common causes

  • The message passed neither DKIM nor SPF for the domain, which is the condition Xfinity names.
  • The From address uses a domain whose SPF and DKIM do not cover the server or account the message was sent through.

How to fix it

  1. 01Check which address appears in From and which domain it belongs to.
  2. 02Send mail from an Xfinity address through Xfinity webmail or smtp.comcast.net with sign-in.
  3. 03If an app or service sends in your name, set it to send through your signed-in account rather than its own servers.
  4. 04If you need more help, use Report an issue under Postmaster on Xfinity's Customer Security Assurance site.

Sources

What this page rests on, checked on 20 Oct 2026. The explanation is ours; the reply text is the server's.

  1. DM000001Rejected by the sender's DMARC policy.Xfinity rejected the message because it passed neither SPF nor DKIM for the sending domain, and it applied that domain's published DMARC policy.Comcast

Further reading

All 33 Comcast codesEvery code in the wikiPaste your own bounce

Beat · paid monitoring

A heartbeat for your email.

Beat runs every check on this site on a schedule: 41 checks, 33 blacklists and real inbox placement. The moment something breaks, it tells you what broke, why it matters, and the exact fix.

example.comWatching
  • SPFpass
  • DKIMpass
  • DMARCp=none
  • Blacklists0 of 33

Illustrative. Your domain, every few hours.

Also from us:Pulse: your own sending infrastructureConsulting: $65/hr, no retainer