[nmglug] Interesting development re Comcast imap servers
Tom Ashcraft
trailerdog234 at comcast.net
Tue Mar 26 13:40:37 PDT 2019
Thanks for the story Peter,
It raises a question or two that someone might want to comment on. But
before I ask, in the interest of truth and clarity I have to acknowledge
my biases and mention a couple of things that embarrass me.
First is the fact I am by nature strongly predisposed to distrust the
motives and pronouncements of just about any large corporate institution
such as Comcast, sight unseen. Which might be to say that often my
default attitude is that I'm perfectly capable of providing my own
arrogance and stupidity, so I don't think I need anyone else's, thank
you very much.
I try hard not to be that way but it gets me into trouble more often
than it should. Generally, the result is some humiliating error of
miss-attribution.
Recently I've had a couple of these episodes with water pipes and a sync
cable that I was righteously convinced were in perfect working order.
It does sometimes happen that not all after-market products are true
functional equivalents.
Several years ago I had lower-than-expected download speeds. I figured
it was a case of false representation and deceptive advertising by
Comcast, but it turned out be a bad crimp on the co-axial cable upstream
of the router.
One question I have is about the 'patch cable' and 'non-patch cable' you
mention below. From looking into my experience with the bad sync cable,
I'm given to understand that some of these actually incorporate internal
electronics in addition to mere incidental differences in resistance and
manufacture. Is something similar what you mean by distinguishing
'patch cable' from 'non-patch cable'?
Comcast can "push" firmware to *your* router?
Tom in Albuquerque
On 3/26/19 10:57 AM, Peter Reed wrote:
> On Sun, 24 Mar 2019 20:57:53 -0600
> Tom Ashcraft <trailerdog234 at comcast.net> wrote:
>
>> Dear NMGLUGers et al,
>>
>> Some of you may remember my consternation and annoyance over that
>> situation I had where I could no longer receive email with any Linux
>> desktop client, most notably Thunderbird, from Comcast imap servers
> We here in ABQ had a huge update to the Comcast network which took down
> my home network. I own all my own equipment including the modem. Having
> purchased the modem and router I have gained complete control of my
> internal network (multiple routers and other devices). Having said that
> whatever they did took my internal network down and in fact it was not
> untill today I figured out that the patch cable from my main router to
> the modem was the problem. A new non-patch cable fixed the problem and
> I can now interface with my router. Took days to figure this out. There
> was new firmware pushed to my modem by Comcrap but I have no control
> over that. Still a mystery to what happend
>
> Peter in ABQ
> _______________________________________________
> nmglug mailing list
> nmglug at lists.nmglug.org
> http://lists.nmglug.org/listinfo.cgi/nmglug-nmglug.org
More information about the nmglug
mailing list