From: (no name) (no email)
Date: Mon Feb 23 2004 - 10:08:06 EST
On Mon, 23 Feb 2004, /dev/rob0 wrote:
> As I accumulate more and more hostnames, now with two, count-'em two,
> wildcard MX domains (and two more on the way!) I need to streamline
> management of $mydestination.
Why do you need the entire domain hierarchy in "mydestination". Do you
really deliver all mail for the domain and all subdomains locally? Is the
"localpart" namespace for all the domains and subdomains in question
really flat?
>
> Google brought up some talk of using a regexp table, which I presume
> would be called like this in main.cf:
> mydestination = regexp:/etc/postfix/destination
>
The "mydestination" parameter is a "string" matchlist. No parent domain
lookups are performed when matching domains against mydestination. This is
because Postfix evolved gradually, and "mydestination" was invented before
the "parent_domain_matches_subdomains" parameter.
Perhaps now with parent domain matching by default using a leading dot
(except when requested otherwise via the "p...d...m...s..." parameter) the
mydestination setting could become a "domain" match list, but this has
performance consequences since the frequently used resolve_local()
interface which determines whether a domain is local would need to do a
lot more lookups, this would in turn require the implementation of a
resolve_local() cache to compensate for the extra cost, but caching would
mean that the trivial-rewrite service needs to be restarted if tables
listed in mydestination are changed. If Postfix had a time (as well as
space) bounded cache, the need to restart could be traded for a
propagation delay limit.
> But I am not clear on what /etc/postfix/destination should look like,
> the syntax. Yes, I [sort of] understand regular expressions. I'm
> confused about the "flags result" part of the "/pattern/flags result"
> example given in the regexp_table(5) page/ sample file.
>
man regexp_table
man pcre_table
-- Viktor.
|
|
|