Comcast checks reverse DNS, refuses dynamic IPs and sender domains that do not resolve, and ties its rate limits to authentication and reputation. It strongly urges TLS and SPF or DKIM rather than requiring them. comcast.net mailboxes are moving to Yahoo Mail through 2026, and neither company has said which sender rules then apply.
| Applies to | Mail to comcast.net addresses |
| Bulk threshold | None published |
| Authentication | SPF or DKIM strongly urged; DMARC p=reject honoured |
| TLS | 1.2 or 1.3 strongly urged |
| Limits | 25 connections per IP, 100 recipients per message, 1,000 messages per session |
| Changing | Mailboxes moving to Yahoo Mail, June 2025 to 2026 |
Check your domain against Comcast Xfinity’s rules
Enter the domain in your From address. What its DNS shows is tested here; for the rest, send one message to our email test.
What every sender needs
- A PTR record for the sending IP, and an MX or A record for the domain, set up properly — otherwise Comcast does not accept the connection.
- Reverse DNS that follows static naming conventions; a generic one gets the IP treated as dynamic (ES000010), and dynamic IP space is not accepted.
- A sender domain with a valid A or MX record (“550 Invalid sender domain” otherwise).
- Mail that complies with the relevant RFCs.
- Every “550 Not our customer” bounce treated as an unsubscribe; large numbers of undeliverable messages, or directory-harvest attempts, get the IP blocked.
- No more than 25 simultaneous connections per IP, 100 recipients per message, 1,000 messages per session and 15 MB per message.
What happens to mail that does not comply
Comcast strongly urges TLS (1.2 or 1.3) and SPF or DKIM, and says going without them will affect throughput, reputation and placement. Its hourly recipient limits depend on authentication and on your Sender Score — from 120 recipients an hour with no score to 60,000 at a score of 86–100 — and new IPs and domains start low.
Mail that fails DMARC where the sender’s domain publishes p=reject is rejected (DM000001). Blocklist listings — Spamhaus ZEN, Cloudmark, Return Path, Vade — are reported in the BL codes.
| The rejection | What it means |
|---|---|
DM000001 | Rejected under the sender domain’s DMARC p=reject policy: the message passed neither DKIM nor SPF for that domain. What to do → |
BL000000 | Blocked for spam-like patterns — the block-removal form applies to this one. |
BL000001 – BL001111 | The IP is on one or more blocklists; the digits show which (Spamhaus ZEN, Cloudmark, Return Path, Vade). |
ES000010 | The IP is treated as dynamic, usually because of generic reverse DNS. What to do → |
RL000001 | Rate-limited by recipients per hour, according to Sender Score and authentication. |
554 PTR lookup failure | The sending IP has no reverse DNS. What to do → |
Comcast Xfinity’s tools for senders
- Xfinity postmaster — the requirements, the error codes and Comcast’s own server ranges
- Block removal — for BL000000 blocks only — usually lifted in under 30 minutes; up to 5 requests per IP a day
- Feedback loop — complaint reports by IP or DKIM domain, for whoever runs the sending server
- Email errors — the codes, as Xfinity’s support site explains them
Recommended, not required
- TLS 1.2 or 1.3, and SPF or DKIM — Comcast’s own words are “strongly urges”.
- A shorter retry interval when throttled, then a look at engagement and list hygiene.
- Low volumes from new IPs and domains, raised gradually.
Common mistakes
- Using the block-removal form for a blocklist code (BL000001 and up): it is only for BL000000 — get off the list itself instead.
- Generic reverse DNS such as 203-0-113-5.provider.net, which makes Comcast treat the IP as dynamic.
- Assuming these rules will last: as comcast.net mailboxes move to Yahoo Mail, meeting Yahoo’s rules too is the safe course.
Setting up the records? The exact SPF include and DKIM records for each service are in our email setup guides, and what each part of a record does is in SPF, DKIM and DMARC explained.
Questions
Does Comcast require DMARC?
Not of senders. It honours a sender’s own p=reject policy — mail that fails it is rejected with DM000001 — but asks for no DMARC record.
Are comcast.net addresses moving to Yahoo?
Yes. Xfinity began inviting comcast.net users to move to Yahoo Mail in June 2025, with invitations rolling out through 2026. Neither Xfinity nor Yahoo has said which sender rules apply to moved mailboxes.
Sources
Checked against Comcast Xfinity’s own documentation on 25 September 2026:
- Xfinity ⋅ Service Policy Assurance — spa.xfinity.com
- Sender requirements — spa.xfinity.com
- Comcast mail errors — spa.xfinity.com
- Troubleshoot Comcast.net email error codes — xfinity.com
- Upgrade your comcast.net email experience to Yahoo Mail — xfinity.com