Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email firstname.lastname@example.org
Re: using type:table lookup w/ smtpd_hard_error_limit
From: mouss (usebsdfree.fr)
Date: Sat May 27 2006 - 20:21:45 CDT
Victor Duchovni wrote:
> On Tue, May 23, 2006 at 09:16:00PM -0400, Wietse Venema wrote:
>> Kurt Lieber:
>>> On 5/23/06, Wietse Venema <wietseporcupine.org> wrote:
>>>> Kurt Lieber:
>>>>> Does smtpd_hard_error_limit support a type:table lookup? I tried
>>>> Does the documentation say sy?
>>> I'll take that as a 'no', then. At the risk of further feather
>>> ruffling, it would be helpful if there was some explanation in the
>>> documentation of what parameters can and cannot use type:table lookups
>>> as, at least to someone relatively new to postfix, it appears
>>> arbitrary and, therefore, confusing.
>> I will not list all the parameters that do not accept type:table.
> A parameter may support type:table lookups when:
> - The parameter only supports type:table values and implements
> an optional lookup table. Examples: transport_maps, canonical_maps,
> virtual_alias_maps, ...
This is when postfix needs an: argument => value
> - The parameter defines the members of an unordered set, lookup
> tables in this context are used only to check for membership, never
> to find all the members. Examples: mynetworks, virtual_alias_domains,
> relay_domains, ...
"unordered" may be interpreted the wrong way. because order can still be
implemented externally (sql/ldap statements).
I'd say it's a "set" defintion (C belongs to mynetworks, D belongs to
BTW, I'd propose
domain_maps = .... (or is it domain_class_maps?)
with the map containing
foo.example unix (or "local" if you prefer)
bar.example mailbox (or virtual_mailbox_domain if you prrefer)
didi.example alias (or "virtual_alias_domain" if you prefer)
yahoo.example foreign (or $void, to be able to specify a parent
domain as relay, ....)
- people won't list a single domain in multiple classes
- extensible: can later add new classes without needing to add new
> The purpose of "type:table" is not ad-hoc storage of main.cf variable
> assignments in a database. Rather, the type:table parameters are ones
> that enable custom behaviour for a subset of values of a variable that
> ranges over a large set (all IP addresses, all domains, ...).
another benefit of maps is to be able to reconfigure without editing