Hi! I'm revisiting debian packaging of postfix, and noticed that a lot of stuff is done in quite sophisticated, twisty, or outright wrong way due to a simple issue: many postfix utilities require certain parameters to be set.
One example is `newaliases' run at the end of the startup procedure in debian, - it has numerous rather complex workarounds, and yet there are open bug reports still, for many years. The simple thing is: newaliases, or postalias, or postmap, or a few other aux utilities, require valid myhostname, or network_interfaces, to be set, to a sane values. But a package might be installed from another system for example (bootstrapping) where host name is not required to be set, or during regular system setup when host name part hasn't been done yet, or in numerous other contexts, where the environment isn't set up (yet). Another example is postmulti -- for example, in order to just list all configured instances - like for a simple call to `postmulti -l`, network_interfaces parameter should already be valid: # postmulti -l postmulti: fatal: config variable inet_interfaces: host not found: eth0 but this might be early system startup when networking hasn't been set up yet. Due to this, debian multi-instance setup (implemented in an ad-hoc way which I'm revisiting now), uses `postconf -h multi_instance_directories` instead of using `postmulti -l`, and tries to get instance names using `postconf -c $dir' - not even handling instance enabled/disabled state. At the same time, there's postconf which does not require valid config to be present, -- at least this one can be used to perform some configuration. Can't at least some tools be made to not require complete valid configuration? Thanks, /mjt _______________________________________________ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
