9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] spam protection vs. secondary mx'es
Date: Wed, 29 Nov 2006 07:19:40 -0500	[thread overview]
Message-ID: <2884d2815389700c3eb2547c74a9aaf4@coraid.com> (raw)
In-Reply-To: <d14a14fa3dea0a030d8547b381c9d057@tombob.com>

i had this problem a while back.  i eventually convinced
my secondary to run greylisting, but in the mean time i
just dropped my secondary mx.

- erik

On Wed Nov 29 04:42:41 EST 2006, r.raschke@tombobWegDamit.com wrote:
> Hiya,
>
> how do people use greylisting and /mail/lib/sender protection in the
> presence of a secondary MX?
>
> My greylisting is roughly 80% useless, since spammers appear to know
> that a secondary MX will effectively bypass the greylist protection.
>
> Having recently started using /mail/lib/senders, I am seeing a lot of
> rejections due to the secondary MX. At the moment it does not really
> look like I am loosing any real mailing list traffic, but it is
> slightly disconcerting, since a network outage near me will probably
> mean I'll be rejecting real traffic once things are back.
>
> I am starting to question my belief in running my own mail server.  Do
> people just use gmail or something and not bother with anything else?
>
> Robby
>
> --
> "Weg damit" is german for "get rid of this".


  reply	other threads:[~2006-11-29 12:19 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 [this message]
2006-11-29 19:37   ` Dave Lukes
2006-11-29 14:35 ` William Josephson
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=2884d2815389700c3eb2547c74a9aaf4@coraid.com \
    --to=quanstro@coraid.com \
    --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).