Date: 21 Nov 2002 08:47:40 -0600 From: Kirk Strauser <kirk@strauser.com> To: freebsd-questions@freebsd.org Subject: Re: Reacting to spam targetted to freebsd.org [was: Re: PLS GET BACK TO ME.] Message-ID: <877kf7kmib.fsf@pooh.lan.honeypot.net> In-Reply-To: <20021121140056.GA30746@kierun.org> References: <20021121031809.GA77831@tao.thought.org> <Pine.BSF.4.05.10211210844210.23313-100000@buffnet11.buffnet.net> <20021121135803.GB11980@gothmog.gr> <20021121140056.GA30746@kierun.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At 2002-11-21T14:00:56Z, Yann Golanski <yann@kierun.org> writes: > Would it be possible for the owners of the lsit to install something > like SpamAssassin so that those messages actually don't get to us? Erm, I'm roughly 99.999% against that idea. What if someone's writing to ask how to secure their FreeBSD box that's currently being used as a spam relay (and is on many blackhole lists)? For what it's worth, I run SpamAssassin locally, and use it to *mark* possible spams, but never drop them. Then I configured my client to filter based on the `X-Spam-Status' header into a spam folder that I periodically check. Once a month or so, I find a piece of mail that *should* have passed but was marked, so I have to adjust my rules and/or whitelist accordingly. -- Kirk Strauser In Googlis non est, ergo non est. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?877kf7kmib.fsf>