On 2023-07-10 at 12:42:24 UTC-0400 (Mon, 10 Jul 2023 17:42:24 +0100)
Ken Gillett via Postfix-users <k...@groups.ukgb.net>
is rumored to have said:
From where is postconf getting its information? Does it have a config
directory hard coded?
Yes. Note:
# strings
/Applications/Server.app/Contents/ServerRoot/usr/sbin/postconf |grep -i
'[a-z]/[a-z]'
/dev/null
open /dev/null: %m
/Library/Server/Mail/Config/postfix/usr/sbin
/Library/Server/Mail/Config/postfix/usr/bin/newaliases
/Library/Server/Mail/Data/spool
btree:$data_directory/postscreen_cache
/Applications/Server.app/Contents/ServerRoot/usr/local/man
/Library/Server/Mail/Config/postfix
dev:/dev/urandom
/Library/Server/Mail/Config/postfix/usr/bin/mailq
/var/mail
/Library/Server/Mail/Config/postfix/usr/sbin/sendmail
hash:/Library/Server/Mail/Config/postfix/aliases
/Library/Server/Mail/Data/mta
[...]
# strings /usr/sbin/postconf |grep -i '[a-z]/[a-z]'
/dev/null
open /dev/null: %m
/var/mail
btree:$data_directory/postscreen_cache
/usr/sbin
/usr/sbin/sendmail
/usr/bin/newaliases
/usr/local/man
/usr/libexec/postfix
hash:/etc/aliases
/var/lib/postfix
/usr/bin/mailq
/etc/postfix
/var/spool/postfix
[...]
Postfix is built with a set of defaults which are embedded in the
executables. These are subject to configuration at build time. You need
to use Postfix binaries like postconf which were built with the same
configuration as the running service.
The basis of the confusion here is that Apple has shipped all versions
of MacOS X with a customized Postfix using "core system" defaults (/etc,
/var, /usr) since ~10.4. That version is built to be used as a local
'null client' and is launched on demand when mail is submitted locally
(e.g. using /usr/sbin/sendmail, which is actually a Postfix interface)
They also have the "Server" package which puts a differently-customized
version in an "add-on software" tree under /Library/ (which is the
"right" choice per Apple/NeXT filesystem layout norms.)
If you intend to stick with Server a while longer, you might want to
edit your .profile (or .login if you use csh) to add the useful paths to
binaries under /Applications/Server.app/Contents/ServerRoot/ to the
start of your PATH so that you use the Server versions by default.
Certainly it does not seem to follow the directory as applied to the
running master process. How can 2 different postconf executables
produce different results and which is correct?
They produce different results because they were built with different
configurations, such that they have different embedded default
parameters, including the default location of config files. Each
'postconf' will provide the configuration truth about the Postfix
installation of which it is a part.
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
