r.barclay--- via Postfix-users:
> Hello,
>
> Does Postfix support specifying multiple lookup tables for
> check_recipient_access?
> (If there's no match in the first table, look up in the next one.)
>
> smtpd_recipient_restrictions =
> reject_unauth_pipelining,
> reject_invalid_helo_hostname,
> reject_unknown_recipient_domain,
> reject_unknown_sender_domain,
> reject_non_fqdn_recipient,
> reject_non_fqdn_sender,
> permit_mynetworks,
> reject_unauth_destination,
> reject_unverified_recipient,
> check_recipient_access btree:/etc/postfix/first_table
> btree:/etc/postfix/second_table, <----
> ...
Documentation unleashed:
check_recipient_access type:table
Search the specified access(5) database for the resolved
RCPT TO address, domain, parent domains, or localpart@, and
execute the corresponding action.
"the specified access(5) database" is clearly singular form.
You could specify
check_recipient_access btree:/etc/postfix/first_table
check_recipient_access btree:/etc/postfix/second_table
...
Postfix has map aggregators (pipemap and unionmap), but no aggregator
that searces a list of tables. It should not be difficult to
implement, but I doubt if it would really be better than multiple
check_recipient_access entriies as shown above.
Wietse
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
