On Friday 25 January 2008 20:18:02 Alessandro Vesely wrote:
Well, the message is rejected after the MAIL FROM command
even if it was the helo name that failed, but the 517
response line quotes the address that failed. In your
case it was the domain "bankwest.com.au".
Is it possible that the DNS changed after Jan 25 10:33:19
and before we manually checked it?
I don't think so.
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...
The above came through via the same IP from a domain
without an SPF record (to be expected, indicating nothing
is wrong with the transport route) and yet any messages
from bankwest.com.au (via that same IP) which does have
what appears to be a (possibly) legit SPF record is blocked.
The SPF=HELO check should have passed with "none", since
mail191.messagelabs.com has no TXT record. Did that
message use "bankwest.com.au" in the MAILFROM?
As pointed out, the 2nd example immediately above was from
a different domain without any SPF record at all.
BOFHSPFFROM defaults to "off", according to the docs,
thus no Received-SPF for SPF=FROM should be present.
Up till 48 hours ago I did have this additional entry in
/etc/courier/bofh...
opt BOFHSPFFROM=pass,unknown,error,none,neutral,mailfromok
but it seemed to cause a different set of problems, for
a different situation altogether, and that was resolved
when I removed the above line (which had been put in
only a 2 days earlier to solve yet another problem with
mailing-lists).
--markc
9 messages in net.sourceforge.lists.courier-usersRe: [courier-users] SPF
