From: Magnus Bäck (magnusdsek.lth.se)
Date: Thu May 04 2006 - 13:21:02 CDT

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

On Thursday, May 04, 2006 at 06:31 CEST,
     Andrej Ricnik-Bay <andrej.groupsgmail.com> wrote:

> Yes, this isn't the output of postconf -n, but then postconf -n
> silently ignores the deprecated virtual_maps while postfix
> honours them .... I feel it's ok to post this instead.

Change virtual_maps to virtual_alias_maps. As you say yourself, the
former one is deprecated. virtual_maps still works because of the
default value of virtual_alias_maps:

   $ postconf -d virtual_alias_maps
   virtual_alias_maps = $virtual_maps

"postconf -n" lists the known configuration parameters set in main.cf,
but since virtual_maps is not a known configuration parameter in Postfix
2.0 and later, it is not displayed.

[...]

> virtual_maps=dbm:/etc/mail/aliases,btree:/etc/postfix/recipient_canonical,regexp:/etc/postfix/manual_recipient_canonical
> message_size_limit = 51200000
> inet_interfaces = DD.DDD.D.DD
>
> Now: the person who set this up has decided that aliases should
> be part of virtual; it uses aliases (5) format, however. Is that a
> problem?

No, the format does not matter. However, even if the file follows the
format of aliases(5), the lookup rules of virtual(5) will be applied.

> It appears to be working (for as long as I don't introduce
> my own virtual domain to main.cf).
> And what tool (postmap or postalias) would I be using on
> /etc/mail/aliases in the virtual_maps above?

If the file is in aliases(5) format, use postalias(1).
If the file is in virtual(5) format, use postmap(1).

--
Magnus Bäck
magnusdsek.lth.se

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