North American Network Operators Group

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

Re: Outbound mail filtering on large mail / web server farms - just an idea or two that I have

  • From: Suresh Ramasubramanian
  • Date: Sun Nov 20 22:26:52 2005
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=sWNX6Ji+qgA+mpY69jw5G1DM5Y1rme2Ak9SCK6TqlMzAGZxwE17PQ24TIM04TCH4Z8OVJFA+X74zhK2wQryBhTI0t1KTQBFs1SQkKOHj1X5sZ5K3nl2/6G6nVclKolumFgYSP0QTKUIyN4A0Ra29XMcnalAWwe/PtEH431gkKu0=

On 11/20/05, Michael Loftis <mloftis@wgops.com> wrote:
> quite often, which they already do to our normal mail systems even when
> things are going well, again, because of forwards.  I'd imagine there's a
> way I could get just the (AOL) forwarded mail pushed to a separate machine

The difference is of course that when you separate .forward traffic to
a separate IP you tell AOL its a forwarding server. And setup reverse
dns + hostname for that box that says something like
"dotforward.wgops.com" ...

Once you do that you should be reasonably good to go

> with our current (older version) Postfix setup but I haven't actually
> looked into it.  We use SQL based tables for everything in order to make
> automation much simpler on our end.

Implementing these suggestions is much simpler once you do that

--
Suresh Ramasubramanian (ops.lists@gmail.com)