Contributor
•
39 Messages
Xfinity is apparently blocking some legitimate e-mail from being sent to my Xfinity account.
I'm a former Trustee for my local school board. In recent times, any e-mail sent to me from my local school's domain, bellevilleschools.org, is being blocked by Xfinity's servers. I do not have any filters in place and this block is happening at the top level of Xfinity's e-mail system and not by me. My local school board IT department has shown me the bounce-back/rejection notices they are receiving when anybody in their domain tries to e-mail me. This problem has been happening apparently for the last several weeks. And now I have to wonder how many other legitimate (non-spam) entities are also being blocked by Xfinity without my awareness or consent. I've been an Xfinity customer from the inception of your company going back to the days even before Comcast was created. I do expect your technical support to contact me asap to help resolve this problem. Our school board's IT staff has told me that some of our students use bots in the effort to blacklist our district so that their teachers' e-mails also get blacklisted giving students plausible deniability in denying that they received homework assignments, etc. adding that this has now become nearly a daily problem forcing our IT department to notify all the major ISP's to whitelist bellevilleschools.org. It would be very helpful to all the adults in our district if Xfinity would contact me directly so I can further discuss this potential problem as well as what Xfinity can do to help our school board's IT department have our districts TLD permanently whitelisted. Ty.
XfinityAirelle
Official Employee
•
3.1K Messages
4 hours ago
It would be helpful for your school district’s IT team to review a few key items on their mail server:
They need to ensure their mail system complies with all relevant RFC standards and that proper SPF, DKIM, and DMARC authentication records are configured correctly.
Their sending IP must have proper reverse DNS, meaning a valid PTR record that matches a properly configured A or MX record. If rDNS is missing or misconfigured, connections may be rejected.
They should confirm their sending IP is not listed on major DNS block lists such as Spamhaus or other reputable DNSBL providers. If an IP is listed, that alone can trigger filtering.
They also need to review bounce-back error codes carefully. Comcast error messages typically include information that points directly to why the block occurred. Those codes are critical for remediation.
Mail must not be sent from dynamic IP space. Comcast does not accept mail from dynamic IP ranges.
Sender reputation matters. If their IP has generated spam complaints, high bounce rates, dictionary attacks, or compromised account activity, it can result in temporary or ongoing blocking.
Comcast also enforces connection and recipient limits, including limits on simultaneous connections and number of recipients per message. Excessive volume patterns can impact reputation scoring.
The correct next step for the district’s IT department is to submit a sender reputation or delivery issue request directly through our postmaster and security team. They can do this at:
https://spa.xfinity.com/report
That form routes directly to the appropriate team that handles mail server reputation and filtering reviews.
On your side, if you would still like us to document this on your account and review any associated filtering flags, we can do that as well. We would just need to authenticate the account first by sending a 6 digit verification code to the phone number or email on file. Let us know which you prefer.
We absolutely want legitimate communication flowing properly, but the technical remediation will need to start with the sending domain’s IT team through the proper security channels.
0
0