Mark Constable wrote:
> Jan 25 10:33:19 mail courieresmtpd: error,
> relay=::ffff:216.82.241.83,
> from=<[EMAIL PROTECTED]>:
> 517 SPF fail [EMAIL PROTECTED]:
> Address does not pass the Sender Policy Framework
>
> # dig +short txt xxxxx.com.au
> xxxxx.com.au. TXT "v=spf1 +a:mx2.xxxxx.com.au +a:mx1.xxxxx.com.au
> include:spf.messagelabs.com -all"
>
> so they use a messagelabs.com cluster and 216.82.241.83 is
> returned from a lookup of the MX for this domain (in the
> ADDITIONAL SECTION section) which I presume would be returned
> as part of include:spf.messagelabs.com part ?
The include:spf.messagelabs.com actually evaluates
spf.messagelabs.com, which happens to have a TXT rec
"v=spf1 exists:%{ir}.nets.messagelabs.com"
In the macro, "i" stands for IP, "r" for reverse, thus
that becomes "exists:83.241.82.216.nets.messagelabs.com".
That record actually exists (127.0.0.2), thus the test
should have passed, as far as the MAILFROM is concerned.
> a:mx2.xxxxx.com.au +a:mx1.xxxxx.com.au
>
> # dig mx xxxxx.com.au.
Missing a dot between "mx" and "xxxxx"? For
+a:mx2.xxxxx.com.au, you should check with
# dig mx.xxxxx.com.au
> opt BOFHSPFHELO=pass,unknown,error,none,neutral
What was the HELO name they used? Perhaps you can
retrieve the "newmsg" log entry for that message.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
