Ralf Hildebrandt wrote:
>
> On Tue, Apr 02, 2002 at 08:20:20PM +0400, Michael Tokarev wrote:
>
> > > check_recipient_access btree:/etc/postfix/recipient_checks,
> > > check_sender_access btree:/etc/postfix/sender_checks,
> > > rhsbl:/etc/postfix/rhsbl_sender_domain,
> > > check_client_access btree:/etc/postfix/client_checks,
> >
> > In this context, rhsbl:/etc/postfix/rhsbl_sender_domain evaluated for
> > RECIPIENT, not sender. You're talking about smtpd_RECIPIENT_restrictions.
>
> Nah, I actually found a bug. BTW, this was copied from the appropriate
> README file by Josef, where he also uses
> check_sender_access rhsbl:/etc/postfix/rhsbl_sender_domain in
> smtpd_RECIPIENT_restrictions.

I'm sorry for repeating this stuff, but this shouldn't confuse others,
and you, Ralf. Every check_something_access accepts ONE maptype:mapname
argument -- exactly ONE, regardless of indentation. And bare "maptype:mapname"
in smtpd_mumble_restrictions means "check_mumble_access maptype:mapname".

In the smtpd_recipient_restrictions, your rules really looks like:

smtpd_recipient_restrictions = ...
    check_recipient_access btree:/etc/postfix/recipient_checks,
    check_sender_access btree:/etc/postfix/sender_checks,
    check_RECIPIENT_access rhsbl:/etc/postfix/rhsbl_sender_domain,
    ...

It's too easy to be confused here, esp. with the above indentation.

Regards,
  Michael.
-
To unsubscribe, send mail to majordomopostfix.org with content
(not subject): unsubscribe postfix-users

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]