Michael Tokarev via Postfix-users:
> 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).
What about this: don't run any Postfix commands until the machine
is ready. I prefer to start any Postfix activity only after DNS,
networking, etc. are configured/running. That has always workded
well for me.
Postfix would not work well if it wakes up with a queue full of
messages and networking or DNS still needs to be figured out.
> 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.
That really depends on how postconf is invoked ('show settings'
requires tat parameters have a sane value, versus 'write/delete
settings' which cares less).
> Can't at least some tools be made to not require complete valid configuration?
That will be difficult, given that many settings have dependencies
on parameters whose vakues are determined dynamically. We'd d have
to stop using $name expansion.
Wietse
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
