Jerry Amundson wrote:
On Thu March 30 2006 13:17, Bill Taroli wrote:
Jerry Amundson wrote:
Subject occurs with user trying to send to me. Line from maillog:
Mar 30 09:24:46 athena courieresmtpd:
error,relay=::ffff:192.206.149.20,from=<us...@cogeco.ca>: 417 SPF
error us...@cogeco.ca: DNS MX lookup failed.?
Courier has set:
BOFHSPFMAILFROM=pass,none,unknown,softfail,neutral
I think the test against the MX is a different one. Perhaps the
complete specification from etc/bofh would help here. IIRC, the MX
test is actually controlled with BOFHCHECKHELO and BOFHSPFHELO.
I see. Yes, looks like
BOFHSPFHELO=0
would be one direction to go. But, I shy away from making expections
like this, so I suggested the user use an office (local) address, or
actually authenticate to cogeco.ca to go through their server. Simple
fix... ;-)
Personally, I have found BOFHCHECKHELO causes too many delivery problems
for me. It got to be an increasingly full time job to monitor log
reports, add manual exceptions to the rule, and follow up with admins
who couldn't apparently figure out how to get their MTA's and DNS'es to
agree... and some of these weren't small (like Yahoo). In the end, I
left this check turned off and let my other filters catch mail. The
other SPF checks are beginning to come alive as more domains supply DNS
records... quite effective too!
Bill
6 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Re: 417 SPF error...
