From: "jdow" <jdow@earthlink.net>
To: "Linus Torvalds" <torvalds@osdl.org>, <Valdis.Kletnieks@vt.edu>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: Spam, bogofilter, etc
Date: Mon, 2 Oct 2006 12:31:39 -0700 [thread overview]
Message-ID: <010a01c6e659$65a7a040$0225a8c0@Wednesday> (raw)
In-Reply-To: Pine.LNX.4.64.0610021129150.3952@g5.osdl.org
From: "Linus Torvalds" <torvalds@osdl.org>
> On Mon, 2 Oct 2006, Valdis.Kletnieks@vt.edu wrote:
>>
>> How did OSDL's MX checking deal with split in/out configurations like ours,
>> where our MX points at a load-balanced farm of Mirapoint front end appliances
>> with 1 IP address, but our main off-campus *outbound* comes from a different
>> address?
>
> Hey, if I knew what I was doing, I'd be in MIS.
>
> As it is, I just criticise other peoples patches.
DK or DKIM comes to mind. SpamAssassin 3.1.5 handles it neatly.
Off hand expecting a list to maintain perfect anti-spam is rather
difficult. Distributed processing works better. Folks should have
their own anti-spam tools and train them to their own preferences.
(It helps with a list like this one to have a SpamAssassin meta
rule that boosts the scores for BAYES_80 and above while reducing
scores for BAYES_40 and below. It also helps to run a lot of the
SARE, SpamAssassin Rules Emporium, rule sets. Pick and choose for
your particular needs. http://www.rulesemporium.com/rules)
{^_^} Joanne
next prev parent reply other threads:[~2006-10-02 19:32 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 14:23 Spam, bogofilter, etc Lee Revell
2006-09-29 14:29 ` Ismail Donmez
2006-10-01 23:23 ` Chris Wedgwood
2006-10-02 0:41 ` Kasper Sandberg
2006-10-02 10:03 ` Matti Aarnio
2006-10-02 15:21 ` Lee Revell
2006-10-02 15:24 ` Martin J. Bligh
2006-10-02 15:48 ` Lee Revell
2006-10-02 17:39 ` Erik Andersen
2006-10-03 3:37 ` dean gaudet
2006-10-03 4:05 ` Neil Brown
2006-10-02 16:40 ` Linus Torvalds
2006-10-02 17:49 ` Alan Cox
2006-10-02 17:19 ` David Lang
2006-10-02 18:02 ` Linus Torvalds
2006-10-02 18:07 ` Martin Bligh
2006-10-02 18:22 ` Valdis.Kletnieks
2006-10-02 18:29 ` Linus Torvalds
2006-10-02 19:31 ` jdow [this message]
2006-10-02 19:31 ` Antonio Vargas
2006-10-02 21:58 ` Alan Cox
2006-10-04 22:41 ` Adrian Bunk
2006-10-03 17:32 ` Mariusz Kozlowski
2006-10-02 21:33 ` Horst H. von Brand
2006-10-03 8:08 ` John Graham-Cumming
2006-10-03 8:52 ` Howard Chu
2006-10-03 9:40 ` Devdas Bhagat
2006-10-03 9:43 ` Helge Hafting
2006-10-03 10:50 ` Gordon Cormack
2006-10-02 17:34 ` Thomas Davis
2006-10-03 16:42 ` Mariusz Kozlowski
2006-10-27 22:30 ` Oleg Verych
-- strict thread matches above, loose matches on Subject: below --
2006-10-03 6:08 Paul Zimmerman
2006-10-03 12:51 ` Valdis.Kletnieks
[not found] <20061003060346.55869.qmail@web80821.mail.yahoo.com>
2006-10-03 7:01 ` Neil Brown
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='010a01c6e659$65a7a040$0225a8c0@Wednesday' \
--to=jdow@earthlink.net \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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