linux-kernel - Re: Spam, bogofilter, etc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200610021822.k92IMo44008167@turing-police.cc.vt.edu>
Date:	Mon, 02 Oct 2006 14:22:50 -0400
From:	Valdis.Kletnieks@...edu
To:	Linus Torvalds <torvalds@...l.org>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	"Martin J. Bligh" <mbligh@...igh.org>,
	Lee Revell <rlrevell@...-job.com>,
	Matti Aarnio <matti.aarnio@...iler.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Spam, bogofilter, etc

On Mon, 02 Oct 2006 11:02:36 PDT, Linus Torvalds said:

> > MX checking is as broken or more broken than bayes.
> 
> I have to say, OSDL has been doing MX checking, and it's effective as 
> hell. Most importantly, when it _does_ break, it's not because some 
> "content" is considered inappropriate, it's because some ISP does 
> something technically wrong.

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?

Content of type "application/pgp-signature" skipped