You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by decoder <de...@own-hero.net> on 2006/09/01 13:18:49 UTC

Strange SPF problem/wrong result

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

today I saw a strange SPF bug occuring. The original mail header was:

Return-Path: <xx...@microsoft.com>
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-----


Re: Strange SPF problem/wrong result

Posted by Magnus Holmgren <ho...@lysator.liu.se>.
On Friday 01 September 2006 16:14, Ramprasad took the opportunity to say:
> > This is no real forwarding, but all mail for us gets received by that
> > server first, and this server passes it to us. This is a common
> > structure for a bigger mail setup. The trusted_networks option solved
> > my problems, but it should definetly be included in the wiki somewhere.
> > Maybe we should add a note about trusted_networks being important for
> > SPF in the install manual where SPF installation is explained
>
> <snip>
>
> If 134.96.254.200 is accepting mails for you then you must do all SPF
> checks on that host. SPF checks dont work unless you do the checks on
> the receiving host.

SPF checks work (since the information needed is included in a Received: line 
that can be trusted), but you can't reject mail at SMTP time based on the 
result.

-- 
Magnus Holmgren        holmgren@lysator.liu.se
                       (No Cc of list mail needed, thanks)

Re: Strange SPF problem/wrong result

Posted by Kelson <ke...@speed.net>.
decoder wrote:
> The trusted_networks option solved my problems, but it should
> definetly be included in the wiki somewhere.

How about this page:

http://wiki.apache.org/spamassassin/TrustPath

> The common symptoms of a broken Trust path include:
>  * ALL_TRUSTED matching spam email from the outside or other untrusted mail.
>  * Dialup/Dynamic IP RBLs misfiring for properly relayed mail.
>  * Dialup/Dynamic IP RBLs not catching direct-delivered mail.
>  * whitelist_from_rcvd fails to match.
>  * SPF tests misfiring (failing when they should pass and vice versa)

-- 
Kelson Vibber
SpeedGate Communications <www.speed.net>

Re: Strange SPF problem/wrong result

Posted by decoder <de...@own-hero.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ramprasad wrote:
>>>> Return-Path: <xx...@microsoft.com> 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)
>
> <snip>
>> This is no real forwarding, but all mail for us gets received by
>> that server first, and this server passes it to us. This is a
>> common structure for a bigger mail setup. The trusted_networks
>> option solved my problems, but it should definetly be included in
>> the wiki somewhere. Maybe we should add a note about
>> trusted_networks being important for SPF in the install manual
>> where SPF installation is explained
> <snip>
>
> If 134.96.254.200 is accepting mails for you then you must do all
> SPF checks on that host. SPF checks dont work unless you do the
> checks on the receiving host.
In a big infrastructure, this is hardly possible. This mailserver is
not under our control but belongs to the University directly, not to
our chair.

Chris
>
>
> Thanks Ram
>
>
>
>
>
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFE+ELcJQIKXnJyDxURAn12AJ9OSP19czmLi1KNEmunB37WkWC75wCffMa4
15iEKJqbZOzSycS3nwn4RKU=
=4Exp
-----END PGP SIGNATURE-----


Re: Strange SPF problem/wrong result

Posted by Ramprasad <ra...@netcore.co.in>.
> >>
> >> Return-Path: <xx...@microsoft.com>
> >> 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)

<snip>
> This is no real forwarding, but all mail for us gets received by that
> server first, and this server passes it to us. This is a common
> structure for a bigger mail setup. The trusted_networks option solved
> my problems, but it should definetly be included in the wiki somewhere.
> Maybe we should add a note about trusted_networks being important for
> SPF in the install manual where SPF installation is explained
<snip>

If 134.96.254.200 is accepting mails for you then you must do all SPF
checks on that host. SPF checks dont work unless you do the checks on
the receiving host. 


Thanks
Ram







Re: Strange SPF problem/wrong result

Posted by SM <sm...@resistor.net>.
At 05:54 01-09-2006, decoder wrote:
>This is no real forwarding, but all mail for us gets received by that
>server first, and this server passes it to us. This is a common
>structure for a bigger mail setup. The trusted_networks option solved
>my problems, but it should definetly be included in the wiki somewhere.
>Maybe we should add a note about trusted_networks being important for
>SPF in the install manual where SPF installation is explained

The concept is the same as forwarding.  Maybe you shouldn't be 
running any SPF tests in such a setup.

Regards,
-sm 


Re: Strange SPF problem/wrong result

Posted by decoder <de...@own-hero.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gino Cerullo wrote:
> On 1-Sep-06, at 7:18 AM, decoder wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hello,
>>
>> today I saw a strange SPF bug occuring. The original mail header was:
>>
>> Return-Path: <xx...@microsoft.com>
>> 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?
>
> Spamassassin gave the correct result. It compared the IP address of
> the last received server mail.cs.uni-sb.de (mail.cs.uni-sb.de
> [134.96.254.200]) against the SPF record for Microsoft and did not
> see a match. Result SOFTFAIL
>
> Why do you think it should compare to mail-eur1.microsoft.com
> (mail-eur1.microsoft.com [213.199.128.139]).
>
> SPF compares the IP address of the last server to handle the message
> before it was handed off to a server on your receiving end. If the
> message was sent to someone who is using forwarding and forwarded
> through mail.cs.uni-sb.de (mail.cs.uni-sb.de [134.96.254.200]) then
> this would explain the SOFTFAIL. Forwarding breaks SPF.
This is no real forwarding, but all mail for us gets received by that
server first, and this server passes it to us. This is a common
structure for a bigger mail setup. The trusted_networks option solved
my problems, but it should definetly be included in the wiki somewhere.
Maybe we should add a note about trusted_networks being important for
SPF in the install manual where SPF installation is explained


Chris

>
>
> --
> Gino Cerullo
>
> Pixel Point Studios
> 21 Chesham Drive
> Toronto, ON  M3M 1W6
>
> 416-247-7740
>
>
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFE+C2ZJQIKXnJyDxURAp3eAJ9qvVbNz2OaPygoLghms+3KiPc1SQCgpCpD
splrSRz31hg6UjCgJPWVKhY=
=Sb9E
-----END PGP SIGNATURE-----


Re: Strange SPF problem/wrong result

Posted by Gino Cerullo <gc...@pixelpointstudios.com>.
On 1-Sep-06, at 7:18 AM, decoder wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello,
>
> today I saw a strange SPF bug occuring. The original mail header was:
>
> Return-Path: <xx...@microsoft.com>
> 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?

Spamassassin gave the correct result. It compared the IP address of  
the last received server mail.cs.uni-sb.de (mail.cs.uni-sb.de  
[134.96.254.200]) against the SPF record for Microsoft and did not  
see a match. Result SOFTFAIL

Why do you think it should compare to mail-eur1.microsoft.com (mail- 
eur1.microsoft.com [213.199.128.139]).

SPF compares the IP address of the last server to handle the message  
before it was handed off to a server on your receiving end. If the  
message was sent to someone who is using forwarding and forwarded  
through mail.cs.uni-sb.de (mail.cs.uni-sb.de [134.96.254.200]) then  
this would explain the SOFTFAIL. Forwarding breaks SPF.


--
Gino Cerullo

Pixel Point Studios
21 Chesham Drive
Toronto, ON  M3M 1W6

416-247-7740