give it a try, anyway ;) you can see what SpamAssassin thinks of the relays in the message, using "spamassassin -D -L -t < message" and reading the debug lines output.
more info: http://wiki.apache.org/spamassassin/TrustPath http://wiki.apache.org/spamassassin/TrustedRelays --j. decoder writes: > So adding the line > > trusted_networks 134.96.254.200 > > to local.cf will fix this problem and this mail would be recognized > correctly (as in pass SPF) ? > > Thanks > > > Chris > > Justin Mason wrote: > > it's trusted_networks -- SpamAssassin doesn't know that it can > > trust mail.cs.uni-sb.de. > > > > --j. > > > > decoder writes: > >> today I saw a strange SPF bug occuring. The original mail header > >> was: > >> > >> Return-Path: <[EMAIL PROTECTED]> Received: from > >> mail.cs.uni-sb.de (mail.cs.uni-sb.de [134.96.254.200]) by > >> wjpserver.cs.uni-sb.de (8.12.11.20060308/8.12.11) with ESMTP id > >> k7T8rU6P012050; Tue, 29 Aug 2006 10:53:30 +0200 Received: from > >> mail-eur1.microsoft.com (mail-eur1.microsoft.com > >> [213.199.128.139]) by mail.cs.uni-sb.de (8.13.8/2006081400) with > >> ESMTP id k7T8rT98004989; Tue, 29 Aug 2006 10:53:29 +0200 (CEST) > >> Received: from xxxxx.europe.corp.microsoft.com ([65.53.193.xxx]) > >> by mail-eur1.microsoft.com with Microsoft SMTPSVC(6.0.3790.1830); > >> Tue, 29 Aug 2006 09:53:29 +0100 > >> > >> (Some unrelated privacy details replaced with xxx). > >> > >> Now what SPF should do is (as far as I understood): > >> > >> - - Get the mail server that sent this (mail-eur1.microsoft.com) > >> - - Check that its IP is in the allowed SPF record of > >> microsoft.com > >> > >> This check passes as you can see here: > >> > http://www.dnsstuff.com/tools/spf.ch?server=microsoft.com&ip=213.199.128.139 > >> > >> > >> Now SpamAssassin did something else, it took mail.cs.uni-sb.de as > >> the mailserver that sent, and tried to match it against > >> microsoft.com's SPF records which produced a SOFTFAIL: > >> > >> 1.4 SPF_SOFTFAIL Sending host does not match SPF-record > >> (softfail) [SPF failed: Please see > >> > http://www.openspf.org/why.html?sender=xxx%40microsoft.com&ip=134.96.254.200&receiver=This%20account%20is%20currently%20not%20available] > >> 2.4 SPF_HELO_SOFTFAIL HELO-Name does not match SPF-record > >> (softfail) [SPF failed: Please see > >> > http://www.openspf.org/why.html?sender=xxx%40microsoft.com&ip=134.96.254.200&receiver=This%20account%20is%20currently%20not%20available] > >> > >> > >> Can someone explain me this failure? > >> > >> Thanks > >> > >> > >> Chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 > >> (GNU/Linux) Comment: Using GnuPG with Mozilla - > >> http://enigmail.mozdev.org > >> > >> iD8DBQFE+BcYJQIKXnJyDxURAl22AJ9D1gsr9/mjmevWVe63mRcdOkeWqACgxYs8 > >> S2NysNSm5mdscg2H2OsSsiI= =ghdo -----END PGP SIGNATURE----- > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.5 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFE+BxWJQIKXnJyDxURAhQ1AKCsicr906Fy7RkBZtU3TduR/cgFHgCfWJGe > 2KZKNwn4ZfYBx4yh/xUwoHw= > =AtZw > -----END PGP SIGNATURE-----
