Greg Earle writes:
So, I compared the new courier.sysvinit script to my existing one, and
installed the new one with a little massaging for my own setup - but
the newer version of the init script doesn't attempt to start
"authdaemond"
at all.
Clearly "courieresmtpd" seems to be trying to connect to an authdaemon
(via a UNIX-domain socket, if my reading of the "truss" output is
correct),
yet there's nobody home. What am I missing? (I even did another
"make install"/"make install-configure" in the courier-authlib 0.56
directory
afterwards, to make sure everything got installed in the right places.)
courier-authlib has its own startup script.
Start courier-authlib first, then start Courier.