crtdude's profile

New Poster

 • 

6 Messages

Sun, Jan 10, 2021 1:00 AM

Added to Spamhaus ZEN

So, for some time now, my home IP address (Comcast assigned) has been listed on the Spamhaus mail server blacklist monitor.  The modem is an XB3 and there is no logical reason for the issue to have started in the first place.  There are no servers running here nor has there ever been.  Now I find out the block was put on by Comcast itself - Spamhaus PBL is a DNSBL database of end-user IP address ranges which should not be delivering unauthenticated SMTP email to any Internet mail server except those provided for specifically by an ISP for that customer's use.

 

So Spamhaus can't pull the block since Comcast started it.  And I cannot request a new IP address for the XB3 since it is a rental.

 

Anyone have any ideas?  I am trying to avoid swapping XB3s because the rocket scientists @Comcast will probably reissue the same IP on the new box once I hook it up.

Responses

BruceW

Gold Problem Solver

 • 

22.4K Messages

5 m ago

As employee @ComcastSPAAbuse stated in https://forums.xfinity.com/t5/Email-Web-Browsing/Outbound-Email-Policy-of-Comcast-for-this-IP-range-... :

 

All [Comcast] residential IP addresses are listed on the PBL.

New Poster

 • 

6 Messages

5 m ago

That's a valid reason however the email I sent was from a webmail client using my @panomedia.net email address to a gmail recipient.  This has NOTHING to do with hosting web sites within a Comcast home environment.  So whoever created the particular block should revise it or create an appropriate filter that works properly.  The blanket answer you supplied is irrelevant to this issue.

BruceW

Gold Problem Solver

 • 

22.4K Messages

5 m ago


@crtdude wrote: ... the email I sent was from a webmail client using my @panomedia.net email address to a gmail recipient. ...

When email sent using a webmail client is rejected because your your public IP is listed in the PBL, it means the rejecting mail system is not working correctly. The PBL listing shouldn't matter unless a user is attempting to send mail directly from a mail server operating on their Comcast Internet connection.

 

Which system rejected the mail you sent? You may need to examine the raw source of the bounce message to find that out.

 

New Poster

 • 

6 Messages

5 m ago

The recipient has an @gmail.com email address.  The webmail sending domain was @panomedia.net, which is my domain hosted on SiteGround.  Mail is exchanged through mx10.mailspamprotection.com, mx20.mailspamprotection.com, mx30.mailspamprotection.com who are all listed as Google services servers.

BruceW

Gold Problem Solver

 • 

22.4K Messages

5 m ago


@crtdude wrote: ... @gmail.com email address ... webmail ... my domain hosted on SiteGround ...

It does not appear that Comcast's mail servers were involved in that path. You'd need to determine which system improperly rejected your email and take up the problem with them.

 

Official Employee

 • 

2.9K Messages

5 m ago

Greetings, @crtdude! I appreciate you taking the time to reach out to us here on the forums. I hope you are having an amazing day! I apologize to hear of the issues you are having with the emails bouncing back. At this time you can double-check with our Customer Security Assurance (CSA) Team at 1-888-565-4329 to see if there is in fact anything being blocked by us. If there is not, then you would need to follow the advice from BruceW.

New to the Community?

Start Here