On Tue, Apr 10, 2012 at 09:36:42AM -0400, btb wrote: > On 2012.04.10 08.32, Wietse Venema wrote: > >>so the relationship between virtual_alias_maps/ > >>virtual_alias_domains is not quite the same as the relationship > >>between virtual_mailbox_maps/virtual_mailbox_domains or > >>relay_recipients/relay_domains? > > > >This is documented in virtual(5). > > thanks for the clarification, i think i understand now. would an > adjustment to ADDRESS_CLASS_README be helpful in highlighting this? > > e.g.: > > >cat ADDRESS_CLASS_README.patch > --- ADDRESS_CLASS_README 2007-03-25 10:53:46.000000000 -0400 > +++ ADDRESS_CLASS_README.mod 2012-04-10 09:20:45.000000000 -0400 > @@ -83,6 +83,10 @@ > * There is no mail delivery transport parameter. Every address must be > aliased to some other address. > > + * Note: virtual_alias_maps will be used with other address classes unless > + a given domain is listed in virtual_alias_domains. see the section on
To me, this confuses things more. virtual_alias_maps will be consulted (and its results applied) regardless of class, and regardless of existence of any virtual_alias_domains. > + VIRTUAL ALIAS DOMAINS in virtual(5) for details. > + > The virtual mailbox domain class. > > * Purpose: final delivery for hosted domains where each recipient > address can -- http://rob0.nodns4.us/ -- system administration and consulting Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
