On 25 Jan 2008 16:29, Alessandro Vesely wrote:
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.
That's very informative, excellent, thank you.
Missing a dot between "mx" and "xxxxx"? For
+a:mx2.xxxxx.com.au, you should check with
# dig mx.xxxxx.com.au
No such host. It's actually for this domain...
bankwest.com.au. TXT "v=spf1 +a:mx2.bankwest.com.au +a:mx1.bankwest.com.au
include:spf.messagelabs.com -all"
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.
I couldn't find a related message to this particular SPF
fail log entry but, separate issue, wouldn't the message
be rejected before courierd got a hold of it?
Now here is one that came in from the same IP, with a
From: address from another domain that does not have a
SPF record at all, and it was successfully delivered...
--markc
9 messages in net.sourceforge.lists.courier-usersRe: [courier-users] SPF
