Tired of Being Screwed By Cox (no pun intended)

[Craig White]

On Tue, 2003-06-17 at 18:32, Thomas Cameron wrote:
> ----- Original Message ----- 
> From: "Adrian Mink" <adrian@minkland.com>
> To: <plug-discuss@lists.plug.phoenix.az.us>
> Sent: Tuesday, June 17, 2003 8:16 PM
> Subject: Re: Tired of Being Screwed By Cox (no pun intended)
> 
> 
> > Yes, but the main issue in my mind is reliability. I trust my own local
> mail
> > server to be up when I need it more than
> > I trust Cox's mail server.
> 
> I mean no offense by this at all, but be realistic:  What if your mail
> server smokes a power supply while you are at work/in the dentist's
> chair/whatever...  You're screwed.  If the Cox SMTP server tanks, they have
> a dedicated group to getting it back up, and I'd bet a donut (maybe two)
> that they have a failover system that works reasonably well.
> 
> > If I have to use a 3rd party to re-route my mail
> > I am left having to rely on their uptime.
> 
> I will be the first to admit that when big ISPs have outages, it is usually
> a spectacular failure and leads to much wailing and gnashing of teeth.  But
> the fact is, they are typically few and far between, and recovered from
> quickly.
> 
----
A whole 2 donuts? Doesn't sound very confident to me.

I would imagine that cox could just change dns to point
smtp.west.cox.net to a different server to handle the load - perhaps a
round robin dns type setup.

I can tell you for sure that when I moved in March, I got the cox
residential service and port 25 and port 80 were already blocked. So
were NetBIOS and ping - I can't ping jack from here. I don't know how
many other ports are blocked but considering bandwidth that I am getting
versus the price I am paying, I am just keeping my yap shut and learning
to love the beast.

Craig