M>
M>Could you please forward a few complete messages that M>incorrectly get an SPF fail with the patch applied.
M>
M>The patch has no effect on SPF_HELO tests.
M>
M>
M>Daryl
M>
Looks like I have to put mail.apache.org as a trusted server for this list
to pass the spf test, the email direct from you passed but the one via the
list failed:-
Direct:
Return-Path: <[EMAIL PROTECTED]>
Received: from mta10-winn.mailhost.ntl.com (smtpout18.mailhost.ntl.com
[212.250.162.18])
by marti.mine.nu (8.12.6/8.12.6/SuSE Linux 0.6) with ESMTP id
j3C78AP5020927
for <[EMAIL PROTECTED]>; Tue, 12 Apr 2005 08:08:10 +0100
Via list:
Return-Path: <[EMAIL PROTECTED]>
Received: from mta09-winn.mailhost.ntl.com (smtpout17.mailhost.ntl.com
[212.250.162.17])
by marti.mine.nu (8.12.6/8.12.6/SuSE Linux 0.6) with ESMTP id
j3C78Wvx020936
for <[EMAIL PROTECTED]>; Tue, 12 Apr 2005 08:08:33 +0100
Martin, the mail didn't go through the same server. Is it possible that you've omitted 212.250.162.17 from your list of trusted_networks? This would cause an SPF failure.
When I set my trusted_networks to 212.250.162.0/24 and run these messages through, they both get SPF_PASS.
This is under 3.1, but 3.0 shouldn't be any different.
Daryl
