Now, one really needs to wonder why the agreement could not be reached
*prior* to the depeering on 10/5
It's not rocket science.
It's only as complex as one makes it out to be. (one can attempt to explain
away the complexities, but they apparently were able to *finalize* an
agreement in 3 weeks
DISCLAIMER: From one of the clueless
During this entire debaucle, I never saw any mention of:
1) Cogent sending "transit" traffic to Level3, which leads me to believe
that all the traffic from Cogent through the peering points was actually
*destined* for Level3 customers. Does the routing
FYI, happened again this morning for (at least) 12/8
duration approx 30 minutes
starting at 5:45 AM PDT.
the bounces from a client employee. It comes not from AOL, but from the
outbound SMTP server stating that
Delivery failed 20 attempts: [EMAIL PROTECTED]
SMTP connection failed
-e-
- Original Message -
From:
Eric Louie
To: [EMAIL PROTECTED]
Sent: Friday, July 22, 2005
I have a client
who is experiencing problems with sending mail to AOL. I
am not resposible for their email service (yet) but I'd like to know if AOL has
changed their policy on anti-spam / mail receipt for their customers (RBL,
SORBS, rDNS validation), or if there's a real problem with AOL
- Original Message -
From: "Chris Adams" <[EMAIL PROTECTED]>
To:
Sent: Monday, April 18, 2005 10:35 AM
Subject: Re: Jonathan Yarden @ TechRepublic: Disable DNS caching on
workstations
That's what most Unix/Linux/*BSD boxes do unless they are running a
local caching name service of some
