opensubscriber
   Find in this group all groups
 
Unknown more information…

c : courier-users@lists.sourceforge.net 25 January 2006 • 10:02AM -0500

[courier-users] Re: Completely turning off hard SPF bounces (webadmin)
by Sam Varshavchik

REPLY TO AUTHOR
 
REPLY TO GROUP




Lloyd Zusman writes:

> Sam Varshavchik <mrsam@cour...> writes:
>
>> Lloyd Zusman writes:
>>
>>> Sam Varshavchik <mrsam@cour...> writes:
>>>
>>>> Lloyd Zusman writes:
>>>>
>>>>> In using webadmin under the latest version of Courier, it is impossible
>>>>> to completely turn off hard bounces in the "Bounces" section of the
>>>>> "Sender Policy Framework" page?  If I uncheck all the boxes in that
>>>>> section and then click on "Save", the '"Softfail" is a hard bounce'
>>>>> and '"Fail" is a hard bounce' come back as being checked.  If I turn
>>>>> them all off except '"Fail" is a hard bounce', then that setting remains.
>>>>> What do I have to do in order to completely disable bounces, even in
>>>>> the case of SPF "Fail" results?  I want to do additional processing in
>>>>> my courierfilters before rejecting these messages.
>>>>
>>>> Put:
>>>>
>>>> opt BOFHSPFHELO=all
>>>> opt BOFHSPFMAILFROM=all
>>>> opt BOFHSPFFROM=all
>>>>
>>>> into the bofh file.
>>> Thanks.  I already have the following in bofh (it was set up this way
>>> by
>>> webadmin, based on my settings there).  Do these three lines cause
>>> Courier to behave differently from the three lines above?
>>>   opt BOFHSPFHELO=pass,fail,none,neutral,softfail,error,unknown
>>>   opt BOFHSPFMAILFROM=pass,fail,none,neutral,softfail,error,unknown
>>>   opt BOFHSPFFROM=pass,mailfromok,fail,none,neutral,softfail,error,unknown
>>
>> Should be the same thing.
>
> OK.  Thanks.
>
>
>>> Webadmin also set these two lines in bofh.  Should I alter or get rid
>>> of
>>> one or both of these?
>>>   opt BOFHSPFHARDERROR=fail
>>>   opt BOFHSPFTRUSTME=1
>>> Thanks again.
>>
>> You should get rid of them, but they don't make any difference.
>
> Well, there is a difference in the BOFHSPFHARDERROR setting.  It causes
> an SPF error to return either a 517 message or a 417 message, depending
> on whether the error condition is matched.
>
> But what I want is _neither_ to be returned during the SPF step.  What I
> want to do is to have all the SPF checking to be performed and then for
> the SPF-Received headers to be set, and for the message to be passed to
> the next processing steps as if no error occurred, even in the case of
> an SPF failure.  Then, I want to look at the SPF-Received headers within
> my courierfilter, and to decide at that point whether I want to accept
> the message, bounce it with a 5xx error, reject it with a 4xx error, or
> whatever.
>
> Is there any way to do that?

Yes -- by listing all possible SPF status results as acceptable, using =all.


Bookmark with:

Delicious   Digg   reddit   Facebook   StumbleUpon

opensubscriber is not affiliated with the authors of this message nor responsible for its content.