Thanks Ted for responding. FYI, Comcast has fixed this issue. It was affecting many of their customers. Here is a quote from Comcast (a message sent out to those of us affected). This issue took a few days to reach a high-level Comcast engineer but once it did, it got resolved. There were just so many levels to go thru before you reached someone who knew what was going on.

Also I think the advice I got about not relying on ISP mail was right on.

<start quote>

It looks like at some point late last week, some number of messages from Charter were marked as spam.  When a sufficient volume of this happens from a single IP, the platform can institute a temporary block to keep that IP from sending additional messages to protect users.  I talked with Charter briefly about it, and we've manually removed the block.  Charter also provided a list of outbound IPs, and we've marked the IPs as protected to keep some policies (including this particular one) from being enforced in the future.  To further complicate things, Charter may not send Delivery failure notices in all situations, which is why the senders weren't seeing that the messages didn't go through.

<end quote>

On 1/8/24 10:01 PM, Ted Mittelstaedt wrote:
This is standard a lot of spam filters just automatically blacklist blocks of 
dynamically assigned IP addresses.  Charter uses specific
IP subnets for DHCP and Spamhaus ZEN likely knows about those subnets.  Charter 
might have even reported them to Spamhaus.

Ted

-----Original Message-----
From: PLUG <plug-boun...@lists.pdxlinux.org> On Behalf Of 
markcasi...@comcast.net
Sent: Thursday, January 4, 2024 10:13 PM
To: 'Portland Linux/Unix Group' <plug@lists.pdxlinux.org>
Subject: Re: [PLUG] email issues

I put my charter IP address into http://mxtoolbox.com/SuperTool.aspx and 
received info that my IP address was blacklisted ... on the Spamhaus ZEN 
blacklist. I have no idea what that means. I assure you no one in this 
household is doing bad stuff on the internet.

Charter support told me to contact my router manufacturer (Why, I wonder?).

The quote I got from Charter was
"There is no way to assign this issue as it does not involve accessibility of 
services. And would not be able to further escalate the issue."
I see it as involving accessibility of services ... my charter email does not 
work, but I have had no success explaining that.

Have I lost Charter as my cable provider? Does anyone have advice on what I can 
do?

  -mark

-----Original Message-----
From: PLUG <plug-boun...@lists.pdxlinux.org> On Behalf Of Ben Koenig
Sent: Tuesday, January 2, 2024 1:02 PM
To: Portland Linux/Unix Group <plug@lists.pdxlinux.org>
Subject: Re: [PLUG] email issues

On Tuesday, January 2nd, 2024 at 12:10 PM, markcasi...@comcast.net 
<markcasi...@comcast.net> wrote:

I am unable to send charter ==> comcast

But I can send
charter ==> IEEE, which is auto forwarded ==> comcast.

That makes it look like comcast is having an issue specifically with charter. I 
would be curious to know if you can receive mail from other charter accounts. 
Is there anyone else you know on that service who can send you a test?

What's also odd is that you are not having issues with forwarded emails or the 
PLUG mailing list. PLUG sends emails on behalf of the sender which can cause 
some email services to silently reject the message. I have a similar issue on 
this proton account when other proton users post to PLUG.

It is possible that comcast is refusing to accept that the issue is on their 
end because something they expect to see is missing from your charter message 
headers. The trick is getting past their T1 support team and getting someone 
who will actually diagnose the issue. Failing that, your only other option is 
to lawyer up.
-Ben


Reply via email to