From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: Re: [9fans] dealing with spam
Date: Thu, 8 Jan 2009 20:34:58 +0000 [thread overview]
Message-ID: <733a79633d40d9a5c3fa636ecd4ef99d@quintile.net> (raw)
In-Reply-To: <56f6e94ee07d87b86ea8389e2fd461b1@coraid.com>
I will go with erik on this.
I am using the standard smtpd with -D and the greylisting,
and also a modified validateserder which probably qualifies as an
earlier incarnation of erik's (he sent me the code before nupas
was finished and I hacked it a bit).
I get 1 or 2 spams a day.
I plan to try nupas as soon as I get a timeslot.
-Steve
next prev parent reply other threads:[~2009-01-08 20:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 19:55 John Floren
2009-01-08 20:23 ` erik quanstrom
2009-01-08 20:27 ` Francisco J Ballesteros
2009-01-08 20:31 ` erik quanstrom
2009-01-08 20:34 ` Steve Simon [this message]
2009-01-08 20:49 ` erik quanstrom
2009-01-08 23:14 ` Kenji Arisawa
2009-01-08 23:43 ` erik quanstrom
2009-01-10 19:41 ` john
2009-01-10 19:50 ` erik quanstrom
2009-01-10 20:35 ` john
2009-01-10 20:57 ` erik quanstrom
2009-01-13 23:36 ` John Floren
2009-01-13 23:52 ` erik quanstrom
2009-01-14 20:33 ` John Floren
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=733a79633d40d9a5c3fa636ecd4ef99d@quintile.net \
--to=steve@quintile.net \
--cc=9fans@9fans.net \
/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).