Victor Duchovni:
> On Fri, Jul 09, 2010 at 07:25:45PM +0200, Philipp Leusmann wrote:
>
> > Jul 9 19:15:25 s15277780 postfix/smtpd[22232]: dict_tcp_lookup: send: get
> > [email protected]
> > Jul 9 19:15:25 s15277780 postfix/smtpd[22232]: dict_tcp_lookup: recv: 200
> > DEFER%20User%20over%20quota
> > Jul 9 19:15:25 s15277780 postfix/smtpd[22232]: dict_tcp_lookup: found:
> > DEFER User over quota
> > Jul 9 19:15:25 s15277780 postfix/smtpd[22232]: check_table_result:
> > tcp:localhost:1337 DEFER User over quota [email protected]
>
> So far, so good.
>
> > Jul 9 19:15:25 s15277780 postfix/smtpd[22232]: >>> START Recipient address
> > RESTRICTIONS <<<
>
> It should never get here, the code in check_table_result() handles strings
> starting with "DEFER <SPACE or TAB> ..." directly, without delegating
> to the "generic_checks" code.
>
> 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.
Wietse
