On 07.05.24 17:13, Дилян Палаузов via Postfix-users wrote:
I try to understand the difference between alias_database and alias_maps.
Or, does postalias/newaliases use is alias_database as input, ignoring
alias_maps, while local ignores alias_databases and uses alias_maps?
Precisely.
alias_maps is for local(8) to know which database(s) to read.
They don't need to be writable (e.g. nis:mail.aliases)
alias_database is for newaliases/postalias to know which database to
reindex.
...because not all databases in aliases can be indexed by postfix programs.
when the same table is supposed to be used by local and postaliases, the
same value (filename) must be set to alias_database and alias_maps?
If you want postfix to work properly, yes.
I think it would be better to have only one parameter: alias_maps, and
newaliases should either update, what is pointed to by alias_maps, or
This may not be possible for NIS maps, LDAP maps etc etc.
That's why there are separate parameters.
report an error on failure. In any case the presence of the two options
currently suggests that there are use cases to have for both options two
different local files as value and the documentation does not elaborate
whether this is a good or bad idea.
perhaps the default value for alias_maps could be something like:
alias_maps = $alias_database, nis:mail.aliases
But the rest still applies.
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Silvester Stallone: Father of the RISC concept.
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
