On Wed, 25 Jan 2006 22:26:29 -0500, Sam Varshavchik <mrs...@courier-mta.com>
wrote:
Lloyd Zusman writes:
OK. So then how can we explain the difference in behavior between
messages going to recipient 1 and recipient 2, as described above?
If you have =all set for all three SPF settings, the message should NOT
bounce with an SPF error for any reason. Setting aside that issue for the
moment, if you do not have a localmailfilter installed in a particular
account, that account is treated as if it has a localmailfilter that
whitelists all mail addressed to it.
So at least the second part of your scenario makes sense -- mail gets
whitelisted, gets past that stage, and gets handed off to courierfilter as
the next step.
So the only question here is why you apparently get a 417/517 SPF error, if
you supposedly set all three SPF checks to =all, that should not happen
under any circumstances.
I cannot reproduce this. With my own server, and default SPF settings, I
get the same SPF error that you do, with that domain with broken SPF
records. If I set the SPF checks to =all, the error goes away.
The only possibibility I can think of -- and this is not documented -- is if
you also set the BOFHSPF variables in the smtpaccess file for certain IP
address ranges only. The settings in the smtpaccess file take precedence
over the bofh file for mail originating from the corresponding IP address
ranges only.
Thanks. Well, I have no BOFHSPF* variables in the smtpaccess file.
I'll keep investigating this mystery, and once I have more info,
I'll post my findings.
.---------, 0__0
/ ( oo'---,
/ oo\
,\ |
| \ ,=__/
\ /
/ /------| /|
|__|-' |__|'
17 messages in net.sourceforge.lists.courier-users[courier-users] Re: Completely turnin...
