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:43:26 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=p+jDY4tJD1o266Mmx0OjTD4c67HgzZxcFY0B6CDL8u1pUtYSSqMjh2Y1NpEfURjkUAd6suV0c1JefILoVJR+OXLNO5Bnxbst6QeCAZOwkJ89LABZ5QL4WKVTCFdkEmAxwjZSUDwNPCn7oU82LD32TlbN6cd8RsBNbkoGAYgseQE=

Oh - I forgot the other advantage of doing this.

When you aggregate all .forward email out through a single box, stuff
that's slipping through your filters starts to stick out like a sore
thumb when you analyze the mail queues on that box, so you can tune
your inbound filters better.  Quite a useful thing to do, really.


On 11/20/05, Suresh Ramasubramanian <[email protected]> wrote:
> 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
> traffic.