[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <010a01c6e659$65a7a040$0225a8c0@Wednesday>
Date: Mon, 2 Oct 2006 12:31:39 -0700
From: "jdow" <jdow@...thlink.net>
To: "Linus Torvalds" <torvalds@...l.org>, <Valdis.Kletnieks@...edu>
Cc: "linux-kernel" <linux-kernel@...r.kernel.org>
Subject: Re: Spam, bogofilter, etc
From: "Linus Torvalds" <torvalds@...l.org>
> On Mon, 2 Oct 2006, Valdis.Kletnieks@...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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists