On Wed, Jan 23, 2002 at 01:18:06AM +0100, Andreas Jellinghaus wrote: > 1.) "rm -f /etc/aliases.db" > 2.) "newaliases" > both is terrible wrong. > first, you have only an assumption what /etc/aliases.db is, and > an assumption that you can delete and regenerate it. both is wrong, > the file could be something different or a not-so-easy to generate file.
>From policy (11.6): /etc/aliases is the source file for the system mail aliases (e.g., postmaster, usenet, etc.), it is the one which the sysadmin and postinst scripts may edit. After /etc/aliases is edited the program or human editing it must call newaliases. All MTA packages must come with a newaliases program, even if it does nothing, but older MTA packages did not do this so programs should not fail if newaliases cannot be found. Note that because of this, all MTA packages must have Provides, Conflicts and Replaces: mail-transport-agent control file fields. It is, nonetheless, arguable that /etc/aliases.db could be something completely different. > second, you think that newaliases will regenerate the alias file. > this is the bigger problem, because this acutaly fails. > i moved aliases to /etc/postfix, which is absolutely legal, and > thus newaliases has to be called with that file as parameter. > also, you don't know if i have a db file aliases at all - a textfile > would not need "newaliases". Properly configured, newaliases _will_ regenerate the alias database. Make sure that if you change alias_maps, that you change alias_database to reflect what maps newaliases should rebuild. > so, either parse the config file, or don't do all this magic at all. > currently it is broken. Postfix does parse the config file. The postinst should evenutally be fixed to remove the needed files based on alias_database as well. lamont -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
