<<< Date Index >>>     <<< Thread Index >>>

Update [Re: [IP] AOL blocking Gmail]

Title: Update [Re: [IP] AOL blocking Gmail]



-----Original Message-----
From: Carl Hutzler [mailto:cdhutzler@xxxxxxx]
Sent: Tue 4/25/2006 7:02 AM
To: ip@xxxxxxxxxxxxxx; David Farber
Subject: Update [Re: [IP] AOL blocking Gmail]

As promised, an update.

Late last night around 11pm, we added into our whitelist a number of
Gmail IP addresses for their outbound systems. Evidently gmail had sent
us an email asking for more servers to be added to our whitelist for
protection but had done so at 4:45pm yesterday. The request had not yet
been processed. I esclaated internally and they got it done. So all is
well now.

So now we will have to see if gmail's outbound spam problem is high on
their list to fix or whether they are more interested in adding capacity
to accommodate the increase in outbound spam,  umm mail ;-)

Oh, and one other thing, all their spam is domainkeys signed. This
emergency whitelisting combined with the fact that all their spam is
signed is a little ironic if you have been following the dearaol.com
debate. ;-)

-Carl

--
Carl Hutzler
Director, Host Mail Development
America Online
cdhutzler@xxxxxxx
703.265.5521 work
703.915.6862 cell

You are subscribed as roessler@xxxxxxxxxxxxxxxxxx To manage your subscription, go to http://v2.listbox.com/member/?listname=ip

Archives at: http://www.interesting-people.org/archives/interesting-people/

--- Begin Message ---
Title: Re: [IP] AOL blocking Gmail

I informed our AntiSpam/Postmaster operations team of the possible rate
limits/delays to gmail mail inbound to AOL.

I don't think this is a "clash of the titans". This kind of stuff
happens all the time and is usually resolved quickly by the
organizations involved. We have had spam problems over the years with
much larger titans than gmail and all have been resolved quickly.

And to be honest, AOL has not been perfect at all times either as we
have occasionally had an outbound spam problem to other ISPs. Every ISP
has the responsibility to police their own users to the best of their
ability. And when issues arise, responsible ISPs communicate on the
issue and do everything possible to restore legitimate email delivery as
soon as possible.

I will try and update the list as soon as I have further information if
that is acceptable. (this is my first post, so I hope folks appreciate
the email and I hope I have not broken any protocol)

PS: I think gmail may have an issue of late as the only two spams I have
received in my AOL account in the last week+ have been from gmail mail
servers. Headers below (all 419 scams - one in english and the other in
spanish)

-Carl

--
Carl Hutzler
Director, Host Mail Development
America Online
cdhutzler@xxxxxxx
703.265.5521 work
703.915.6862 cell





Return-Path: <jrossman1@xxxxxxxxx>
Received: from  rly-yi06.mx.aol.com (rly-yi06.mail.aol.com [172.18.180.134]) by air-yi04.mail.aol.com (vx) with ESMTP id MAILINYI42-7da4448b4e5213; Fri, 21 Apr 2006 06:33:23 -0400
Received: from  qproxy.gmail.com (qproxy.gmail.com [72.14.204.234]) by rly-yi06.mx.aol.com (vx) with ESMTP id MAILRELAYINYI64-7da4448b4e5213; Fri, 21 Apr 2006 06:33:09 -0400
Received: by qproxy.gmail.com with SMTP id e11so21868qbe
        for <cdhutzler@xxxxxxx>; Fri, 21 Apr 2006 03:33:09 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:mime-version:content-type;
        b=LejfxPes4IKizTLpNmTUHlwwFPEacQoi1oXo8YmooH3SrppgEt3UzcAJ2NVyxPqITKqa8n4YEeIFgeqkl9rTC1v0r4++KZRsVrbJL8A8KMcZrvrJOh59Z7KU4oc11F0fPGfcrpRbojhb06nFJet83Qf/PrDCCfjN5W2bAnd3w4o=
Received: by 10.70.99.4 with SMTP id w4mr2109177wxb;
        Fri, 21 Apr 2006 03:31:09 -0700 (PDT)
Received: by 10.70.109.8 with HTTP; Fri, 21 Apr 2006 03:31:08 -0700 (PDT)
Message-ID: <6fa817cf0604210331u3054bc14i47eafa6860c8fab0@xxxxxxxxxxxxxx>
Date: Fri, 21 Apr 2006 03:31:09 -0700
From: "jane rossman" <jrossman1@xxxxxxxxx>
To: secretariat@xxxxxxxxxxxx
Subject: EMINENTLY CONFIDENTIAL
MIME-Version: 1.0
Content-Type: multipart/alternative;
    boundary="----=_Part_6822_24948594.1145615469007"
X-AOL-IP: 72.14.204.234
X-Mailer: Unknown (No Version)







Return-Path: <tangoinmortal@xxxxxxxxx>
Received: from  rly-yb03.mx.aol.com (rly-yb03.mail.aol.com [172.18.205.135]) by air-yb01.mail.aol.com (vx) with ESMTP id MAILINYB13-188444a53af2d; Sat, 22 Apr 2006 12:03:10 -0400
Received: from  xproxy.gmail.com (xproxy.gmail.com [66.249.82.203]) by rly-yb03.mx.aol.com (vx) with ESMTP id MAILRELAYINYB32-188444a53af2d; Sat, 22 Apr 2006 12:02:55 -0400
Received: by xproxy.gmail.com with SMTP id h27so427167wxd
        for <cdhutzler@xxxxxxx>; Sat, 22 Apr 2006 09:02:55 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:from:to:subject:date:mime-version:content-type:x-priority:x-msmail-priority:x-mailer:x-mimeole;
        b=VJwS8XCUyQwIvxKPRyEQL82yVeKLAApKzZsz/EZ3Ur49Pki8h/ZjkSnDJm1KUj2gzld9aNxT5oZzQbfiPMR+QOWnvB0VvDhuEYAdtk5Z/6kDMkwmGL0f0q72M4wa/+kY3VJu1Eq6CwYmQgdb6s7ElRcNypdGr+2gwQ6a0uSIRQk=
Received: by 10.70.43.8 with SMTP id q8mr1752239wxq;
        Sat, 22 Apr 2006 09:02:45 -0700 (PDT)
Received: from morgansnuwusq1 ( [201.254.174.89])
        by mx.gmail.com with ESMTP id i12sm1108809wxd.2006.04.22.09.02.38;
        Sat, 22 Apr 2006 09:02:45 -0700 (PDT)
Message-ID: <049801c66626$295e15a0$6401a8c0@morgansnuwusq1>
From: <tangoinmortal@xxxxxxxxx>
To: <Undisclosed-Recipient:;>
Subject: JUBILACIONES Y AFIP
Date: Sat, 22 Apr 2006 12:47:44 -0300
MIME-Version: 1.0
Content-Type: multipart/alternative;
    boundary="----=_NextPart_000_0364_01C6660A.F32D5BA0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-AOL-IP: 66.249.82.203











dave@xxxxxxxxxx wrote:
>
>
> Begin forwarded message:
>
> From: "Jim O'Donnell" <provost@xxxxxxxxxxxxxx>
> Date: April 24, 2006 5:05:08 PM EDT
> To: dave@xxxxxxxxxx
> Subject: AOL blocking Gmail
>
> Dave, just had a lively and interesting conversation with an AOL
> postmaster phone number.  When they get reports from their users of
> spam from a given host, they start rate-limiting mail from that
> source.  When a given source is huge, it's inevitable that there will
> be spam-marked mail from within that space, and even if it's just
> amateur users who mark as spam mail that comes to them that they don't
> want to see, whether it's spam or not:  with two larger user bases, it
> can easily add up to a number of complaints that triggers aol's
> mechanism.
>
> So, net result, if you have a gmail account and try to write to
> aol.com addresses now, you will probably not get through immediately.
> You will probably get a message from google telling you that your
> message has been delayed and giving an aol postmaster address,
> http://postmaster.info.aol.com/errors/421rlynw.html, that tells you
> that your site (i.e., Gmail) is being rate-limited and delayed inbound
> to aol.
>
> AOL's response to a complaint is to tell the Gmail user to tell Google
> that there's a problem.  Clash of the titans?
>
> Jim O'Donnell
>
>
> -------------------------------------
> You are subscribed as cdhutzler@xxxxxxx
> To manage your subscription, go to
>  http://v2.listbox.com/member/?listname=ip
>
> Archives at:
> http://www.interesting-people.org/archives/interesting-people/


--- End Message ---