https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6403
Peter Alfredsen <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #9 from Peter Alfredsen <[email protected]> 2010-04-11 06:27:54 EDT --- I am experiencing the same problem with spamassassin 3.3.1, with trusted_networks set to include gmail's internal networks. To me, the problem seems to be that spamassassin is incapable of detecting that Received: headers like the following: Received: from joi (aces5.neoplus.adsl.tpnet.pl [83.9.194.5]) by mx.google.com with ESMTPS id k29sm5581025fkk.45.2010.04.10.12.55.35 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 10 Apr 2010 12:55:37 -0700 (PDT) indicates that google authenticated the user. Adding something to Received.pm to detect this would probably work. This snippet seems to solve the problem for me: --- Received.pm.orig 2010-04-11 12:20:35.000000000 +0200 +++ Received.pm 2010-04-11 12:29:47.000000000 +0200 @@ -394,2 +394,7 @@ } + # GMail should use ESMTPSA to indicate that it is in fact authenticated, + # but doesn't. + if (/by mx.google.com with ESMTPS id [a-z0-9]{1,4}sm[0-9]{4,9}[a-z]{3}\.[0-9]{1,2}\.[0-9]{4}\.(?:[0-6][0-9]\.){4}[0-6][0-9]/) { + $auth = 'GMail'; + } # Courier v0.47 and possibly others -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
