Hide Forgot
postfix is perfectly fine using alias_database = ${default_database_type}:/etc/postfix/aliases unfortunately /etc/init.d/postfix insists on running postaliases `postconf -h alias_database` that fails in this configuration. The correct solution is to run newaliases instead or not try to update the aliases db at all.
If you modify your alias database you have to run newaliases afterwards.
Correct, one has to run newaliases after modifying the aliases file, so why does /etc/init.d/postfix insist on it's broken implementation of newaliases?
The postalias call is there to check if the alias_database entry is correct: - syntactically valid - file/files existance - correct permissions - valid db files If there is an other way to check this, then I will replace it.
alias_database = ${default_database_type}:/etc/postfix/aliases is syntactically valid but causes the current initscript to fail aliases_database is AFAIK only used by newaliases, the MTA processes use the databases defined in alias_maps postfix runs fine without an alias_database, even without alias_maps
Ok, then this bz is the same as #149657. *** This bug has been marked as a duplicate of 149657 ***