From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Ghtg1-0001GV-6k for garchives@archives.gentoo.org; Wed, 08 Nov 2006 20:05:37 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.8) with SMTP id kA8K4gV9008842; Wed, 8 Nov 2006 20:04:42 GMT Received: from panther.panther.lieber.org (mail.lieber.org [64.147.188.100]) by robin.gentoo.org (8.13.8/8.13.8) with ESMTP id kA8K28ix032034 for ; Wed, 8 Nov 2006 20:02:08 GMT Received: from localhost (localhost [127.0.0.1]) by panther.panther.lieber.org (Postfix) with ESMTP id CAEE9E84021 for ; Wed, 8 Nov 2006 20:02:07 +0000 (UTC) X-Virus-Scanned: amavisd-new at lieber.org X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001] Received: from panther.panther.lieber.org ([127.0.0.1]) by localhost (panther.lieber.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SD3uZXR8pz0V for ; Wed, 8 Nov 2006 20:01:52 +0000 (UTC) Received: by panther.panther.lieber.org (Postfix, from userid 1001) id A5C5CE84022; Wed, 8 Nov 2006 20:01:52 +0000 (UTC) Date: Wed, 8 Nov 2006 20:01:52 +0000 From: Kurt Lieber To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Monthly Gentoo Council Reminder for November Message-ID: <20061108200152.GA4007@mail.lieber.org> References: <20061101134037.6F126649AC@smtp.gentoo.org> <200611061720.50442.vapier@gentoo.org> <20061106223839.GA6332@gentoo.org> <200611061748.34810.vapier@gentoo.org> <45502DEB.20404@gentoo.org> <20061107162459.j8akeyhf0gwg88os@horde.gg3.net> <20061108172955.GY4007@mail.lieber.org> <20061108175413.7a76fd3c@snowdrop.home> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0iexB5Bk8cF8G6DP" Content-Disposition: inline In-Reply-To: <20061108175413.7a76fd3c@snowdrop.home> X-GPG-Key: http://www.lieber.org/kurtl.pub.gpg User-Agent: Mutt/1.5.11 X-Archives-Salt: 6dc93d7d-a8cb-444c-b884-6c7aec001d89 X-Archives-Hash: 775bb4707ed4b96ea1b089e540a95456 --0iexB5Bk8cF8G6DP Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline On Wed, Nov 08, 2006 at 05:54:13PM +0000 or thereabouts, Ciaran McCreesh wrote: > We've identified one very widely used application that interprets SPF > records based upon how they're used by spammers rather than by how the > specification says they should be interpreted. In this case, SA is > entirely reasonable in its behaviour -- SPF makes the classic incorrect > assumption that spammers won't abuse the system. Ciaran, you obviously do not understand the issue, nor do you know what you're talking about. The issue is that SpamAssassin assigns a score of ~1 to any email that FAILS an SPF check for a domain that has a ?all (neutral) rating. I want to stress that it has to FAIL. If it doesn't fail, I believe SA's default behavior is to assign a *negative* score of 0.1. So, in other words, spammers aren't abusing anything related to SPF. They're sending mail using forged return-paths and SPF is highlighting that. Which is exactly what SPF is designed to do. The impact is that some users happen to send mail in a way that ends up looking very similar to a spammer sending an email with a forged return-path. And, because of the way SA has chosen to interpret this, those valid, non-spam emails get assigned a positive spam value, even when the mail administrator has asked them not to. --kurt --0iexB5Bk8cF8G6DP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFUjewJPpRNiftIEYRAo/1AJ9JdRB1tjTbexxkHDXOcejSTqHgzACfadKD b1839owiE5X8CCgkBpdifYI= =mArr -----END PGP SIGNATURE----- --0iexB5Bk8cF8G6DP-- -- gentoo-dev@gentoo.org mailing list