North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: AOL Postmaster contact?

  • From: Suresh Ramasubramanian
  • Date: Sun Nov 20 00:40:38 2005
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta;; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ZzRUjp7hKZGCJNuKT7h7iZR2EjrWzZIa5xbyyIn9ZSmSK7ktDC4CH3TWO+hyz6JO8LcUO48AslV0sdRxEYZh50EYUSnv92CK6Cx/kccW9ixO5r1JxEGQ9V624yuNPNiQ9vLIHRKTA0lNT616kKr/JlaKYxB0YnNetjUOkkqC8BM=

On 11/20/05, Mark Costlow <[email protected]> wrote:
> Someone might look at the ticket Monday.  Meanwhile, I've got thousands of
> queued messages frrom users that are upset with ME because I can't get
> their mail to AOL.

AOL's whitelist + feedback loop is not really a whitelist

If the numbers theyre seeing on your servers get too high .. they'll
start rate limiting you down by putting in anywhere upto 48 hour
tempfailing of your IPs

The last time this happened to us, it got very quickly resolved when
we ran numbers on our scomp complaints from AOL to see what was going

Turns out the reason was a lot of users with .forwards to AOL
accounts, then reporting .forwarded email as spam.  This email was
also going out through our standard outbound mail relays, and the
combination of our outbound spam levels (pretty low for an ISP our
size) AND .forwarded email tipped the balance.

So what we did was to set things up so that .forward traffic was
routed out a separate IP.  And we told AOL what that IP was and also
told them that the only thing coming out of it would be .forward

They took that into account I guess, because the haven't gone and
4xx'ed us since we set this up (and when they do 4xx it hurts - we're
just over a third their size so there's a substantial amount of email
traffic from our users to AOL ..)

Suresh Ramasubramanian ([email protected])