On Wed, 2003-06-18 at 00:27, der.hans wrote:
> Am 17. Jun, 2003 schwätzte Craig White so:
> 
> SpeedChoice/Sprint couldn't build a decent mail server if their collective
> lives depended on it. I used them as a smarthost, then discovered how dumb
> it was to rely on them and went to direct delivery. The service in general
> sucks, but loses all semblance of working for days at a time when it goes
> down.
----
and they gave up a long time ago, switching to Earthlink to handle their
mail as part of their abortive attempt to partner Sprint with Earthlink.
The mail remains handled by Earthlink.
----
> Currently Cox business services thinks it's OK to change things on static
> accounts with a generic "we'll be doing service in your area" notification
> shortly before the changes happen. @HOME used to cache DNS stuff for a
> couple of weeks and I'm told AOL still does. Cox, who as noted above used to
> use @HOME, thinks 5 days is enough time for that 2 week cache to expire.
> They musta hired enron and worldcom accountants to do their networking.
> 
> I have only talked to one support engineer at Cox. He seemed to be
> knowledgeable and was able to accurately answer my questions, so there is a
> glimmer of hope :).
----
Things are much improved since Cox took over from @home.
I have only had one business account get switched since cox took over.
Not really been pervasive but always a hassle.
----
> Complete blocking of ping is bad, IMO. I've not heard of a problem pinging
> from Cox connections. Are you sure you're not remembering a FastQ
> connection? I've talked to Dan about that. He won't budge. I still disagree
> with him and won't recommend FastQ until he changes that policy.
----
I can't ping jack but perhaps it's the cheapo speedstream router that I
bought when I moved, but I don't think so. It's not important enough to
worry about but I used to use ping a lot - not any more. I've not seen a
problem pinging from any other cox connection at friends or customers.

Craig