All email must comply with all relevant RFCs.
Comcast performs an rDNS check on the IP of the sending server. If the sending server does not have a PTR record and a MX or an A record set up properly, the connections will not be accepted.
A large number of undeliverable emails sent to Comcast will result in a sending IP being blocked. All “Not Our Customer” NDNs should be treated as an unsubscribe request.
Enforce AUPs and mitigate compromised accounts and machines. Dictionary or Directory Harvest attacks are treated seriously and will quickly lead to the sending IP being blocked.
Dynamic IP space is a common haven for compromised machines used in bot networks. As a result, in keeping with industry best practices, Comcast does not accept mail from dynamic IP space. If email appears to be coming from dynamic IP space then it will not be accepted.
Overall IP reputation is key to successfully sending to Comcast. If Comcast, or another reputable organization repeatedly receives spam, spyware or other malicious attacks, phishing efforts or other deceptive emails from a certain IP address, Comcast is more likely to block future messages from that IP address. Ensure the overall sending reputation of the sending mail system is as clean as possible.
Comcast allows 25 simultaneous connections per sending IP address.
Comcast allows 100 recipients per message.
Comcast will employ a limit of 1000 messages an hour per netblock for senders using IPv6.
Most blocks are temporary in nature and mail can be retried when the block period expires. Perpetual issues with IP Blocks for an IPv6 address should be escalated to Customer Security Assurance at 888-565-4329.
This page was designed to address questions on the following topics:
All policies and thresholds on this page are subject to change. This site will be updated when such changes are implemented.