Prev: SASL Authentication per recipient domain
Next: Selective outbound relaying II
From: Philipp Leusmann on 9 Jul 2010 20:33

Am 09.07.2010 um 22:37 schrieb Wietse Venema:

> Victor Duchovni:
>> On Fri, Jul 09, 2010 at 04:04:59PM -0400, Wietse Venema wrote:
>>
>>>> Either your Postfix source is modified, miscompiled, the binaries are
>>>> corrupted, or CPU is mal-functioning.
>>>
>>> Or he is running a Postfix version before 2.6.
>>>
>>> Citing the access(5) manpage:
>>>
>>> DEFER optional text...
>>> Reject the address etc. that matches the pattern. Reply with
>>> "$access_map_defer_code optional text..." when the optional text
>>> is specified, otherwise reply with a generic error response mes-
>>> sage.
>>>
>>> This feature is available in Postfix 2.6 and later.
>>
>> Oops, I thought this was older. He reported running 2.5.5, so that
>> would explain the whole mess. In 2.5 "DEFER" is not an access(5) action
>> and so falls through to generic_checks, with the reported symptoms.
>
> For the record:
>
> Postfix has always supported
>
> smtpd_mumble_restrictions = ... defer other_restrictions...
>
> And access map lookup results of
>
> ... defer other_restrictions...
>
> But only Postfix 2.6 and later support acces map lookup results of
>
> defer optional-text-for-sender

Ok, then this Problem should be solved for me.

Thanks for all your help, guys.

Philipp

First  |  Prev  | 
Pages: 1 2 3 4
Prev: SASL Authentication per recipient domain
Next: Selective outbound relaying II