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: Mon Nov 21 01:22:30 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=M1iqd0rIMO1igIfWD/UeEDerzCWl8UUqb62IGeh3gg/aBKBSrC5zuL6Axn9OHhsBRmhzURdSIMHEyrsS5WgBU3DsuhXDJRD3pKXxQg6n6pEp+xkyDpUqbflcRCpNlVW8Rdld0OxLdV2d8FOkv+prDY9/wCo2FBLaTyIcbdEmheU=

On 11/21/05, Michael Loftis <[email protected]> wrote:
> Oh I understand the concept perfectly well.  It's just that I can't see
> through to an implementation easily.  The system I'm referring to has no
> internal way of telling the difference easily between forwarded mail and
> 'other' mail, it's all passed into the same set of virtual tables and the
> only difference is local versus remote delivery.  I can't classify .forward

Separate your MXs from your outbound servers

And have local traffic rewritten to an internal domain (say just for local delivery .. all other outbound
traffic on your MXs can be assumed to be either

* Bounces  [route em out of a separate host as well - tracking those
helps block a ton of spam]

* Forwarded emails

Your outbounds of course go out via a separate set of boxes.

Multiple machines. Or multiple postfix instances on the same box. Whatever