[86860] in North American Network Operators' Group
Re: AOL Postmaster contact?
daemon@ATHENA.MIT.EDU (Suresh Ramasubramanian)
Sun Nov 20 00:42:36 2005
Date: Sun, 20 Nov 2005 11:12:08 +0530
From: Suresh Ramasubramanian <ops.lists@gmail.com>
To: Mark Costlow <cheeks@swcp.com>
Cc: David Hubbard <dhubbard@dino.hostasaurus.com>, nanog@nanog.org
In-Reply-To: <bb0e440a0511192139hd0979c1n8c9fa24d695314dd@mail.gmail.com>
Errors-To: owner-nanog@merit.edu
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.
srs
On 11/20/05, Suresh Ramasubramanian <ops.lists@gmail.com> 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.
>
