9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: William Josephson <jkw@eecs.harvard.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] spam protection vs. secondary mx'es
Date: Wed, 29 Nov 2006 09:35:03 -0500	[thread overview]
Message-ID: <20061129143503.GA88630@mero.morphisms.net> (raw)
In-Reply-To: <d14a14fa3dea0a030d8547b381c9d057@tombob.com>

On Wed, Nov 29, 2006 at 09:35:19AM +0000, Robert Raschke wrote:
> how do people use greylisting and /mail/lib/sender protection in the
> presence of a secondary MX?

For Unix hosts, consider mail avenger.  On secondary MXes,
mail avenger will contact the primary and reject/defer mail
when the primary MX is up.  Seems to work well in practice
since it is rarely the case that there is a route from the
secondary to the primary and the sender to the secondary but
not the sender to the primary and in that case mail can just
be deferred.  One can also greylist on the secondary as well
as the primary, but most senders (even well behaved ones) will
try the secondary as soon as the primary defers so you end up
with twice the greylisting delay.  I've also found that greylisting
is generally less effective than it was a year ago and that
SMTP call back is not really all that reliable.


  parent reply	other threads:[~2006-11-29 14:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-29  9:35 Robert Raschke
2006-11-29 12:19 ` erik quanstrom
2006-11-29 19:37   ` Dave Lukes
2006-11-29 14:35 ` William Josephson [this message]
2006-11-29 16:24 ` Georg Lehner
2006-11-29 16:33   ` Gabriel Diaz
2006-11-29 16:36   ` William Josephson
2006-11-30 20:53 Steve Simon
2006-11-30 21:05 ` William Josephson
2006-11-30 23:16   ` Michael Batchelor
2006-11-30 23:30     ` William Josephson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061129143503.GA88630@mero.morphisms.net \
    --to=jkw@eecs.harvard.edu \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).