Randall Shaw wrote:
The authlib daemon seems to have been split into its own sole entity
in the
newer version of courier. You must start it BEFORE starting courier
now, and
stop it AFTER starting courier.
If you use (or have) ntsysv installed, you can go turn on authlib as a
service to start just like courier.
if you do it manually in the rc.local filess, then you need to have
"service
authlib start" before the "service courier start" lines... inversely
with
the shutdown script (turn off courier before authlib).
Hope that helps.
You did install authlib (courier-authlib-0.56.tar.bz2), right?
I'm on Solaris 9. No ntsysv or rc.local stuff - all /etc/init.d
scripts.
I got authdaemon started manually (will check for an init script now,
thanks), but have a new problem - mail comes in, "submit" gets called,
everything looks OK, "courieresmtpd" logs a message:
Jun 27 13:34:01 isolar courieresmtpd: [ID 702911 mail.info] started,
ip=[::ffff:24.130.129.94]
An "250 Ok. 42C062BB.0001FC6" gets written to the "trigger" socket,
and at some point "submit" writes a "QUIT" back to "courieresmtpd".
But that's it - "courierd" never seems to be contacted (which always
seems to be the next step after "courieresmtpd" gets the initial
incoming connection), and the mail disappears into the bit bucket.
Scratching my head over this one ...
- Greg
5 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Problems connecti...
