On 28 Feb 2021, at 1:35, JF Mezei wrote:
I last posted here some 11 years ago and it didn't end well, hoping to
restart on better foot,
Situation: OS-X Snow Leopard server, with Postfix that came built by
Apple.
According to postconf -d , Mail version: Postfix 2.5.14
Before I continue, I just have to say:
EWWW!
Also, I should add that I run a production (albeit small and
research-focused) Postfix+Dovecot server on i386 Snow Leopard and have
done so for many years.
----------------
Thurst of first question: find out what options Apple used to built :
do postconf -a and -m yield all options I need to be concerned about,
or
are there many other portions I need to check to ensure that what I
build from source (3.5.9) has the same functionality as what Apple had
provided last decade?
postconf -a
cyrus
dovecot
velo:perl-5.32.1 $ postconf -m
btree
cidr
environ
hash
pcre
proxy
regexp
static
unix
My SASL goes though DOvecot. From what I read, this is all done
through
pipes, so I assume both are independantr of each other when one is
upgraded ?
If you have MacOS X "Server" installed, see
/Library/Server/Mail/Config/postfix/makedefs.out
Otherwise, if you're just using the standard build of Postfix on MacOS
X, see /private/etc/postfix/makedefs.out
Secondly, what is the recommended/best practice to document the build?
If you build in a normal way, you will get a makedefs.out file. See
above
[...]
Now, second big question:
just upgraded openssl to 1.1.1j and it sits in /usr/local hiearchy
(leaving the original elderly Apple version in /usr).
This is first time I upgrade a core component used by other software,
so
pardon my newbie question.
Consider yourself pardoned :)
While the $PATH is set to put /usr/local/bin ahead of /usr/bin, I am
not
aware of what mechanism exists to tell "make" where to find the new
libraries against which to link Postfix. ( looks in the install page
and
didn't find such reference). Any pointer ?
(I know of the main.cf parameter openssl_path but that appears to be
for
run time casual use, not encryption libraries which I assume are
linked
at build time).
My recommendation is to use MacPorts: https://www.macports.org
As Viktor suggested, there's also the "Homebrew" package management
system, but for a number of reasons too arcane for this mailing list, I
prefer MacPorts.
You *CAN* keep track of all the little build-time and runtime gotchas
yourself if you are a seasoned sysadmin and really feel a need to DIY,
but life really is too short and it is simpler to let Josh, Ryan, Ken,
Mojca, the other MacPorts committers, and (to a minor extent) myself
keep the ports working in response to changes in the software and
problem reports by users.
Third question: Install location.
I know of the shlib_directory option. However, if I do a "make
upgrade"
does this imply that it will replace the original Apple-supplied
executables in directories that are now SIP protected (Snow Leopard
doesn't have SIP, but would still want to know). Is there an easy
mechanism to get the "make upgrade" to send everything to /usr/local
equivaent of the original?
Yup, that's why I recommend MacPorts. Everything gets installed under
/opt/local and all the dependencies and link issues get worked out for
you (with your help, if you want to help) and it Just Works.
Thanks for any/all advice.
Definitely consider Viktor's response as well.
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire
