5 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Problems connecti...
FromSent OnAttachments
Greg EarleJun 27, 2005 12:14 pm 
Sam VarshavchikJun 27, 2005 12:26 pm 
Randall ShawJun 27, 2005 12:28 pm 
Greg EarleJun 27, 2005 2:56 pm 
Randall ShawJun 27, 2005 3:29 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] Problems connecting to authdaemon after upgrading (0.44.2 -> 0.50.0)Actions...
From:Randall Shaw (cour@randallshaw.com)
Date:Jun 27, 2005 12:28:49 pm
List:net.sourceforge.lists.courier-users

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?

-Randall Shaw

Greg Earle:

I'm trying to upgrade my home e-mail setup from 0.44.2 to 0.50.0 and it's not going very well.

Jun 27 11:49:35 isolar courieresmtpd: error,relay=::ffff:24.130.129.94, ident=root,from=<ear@my.work.do.main>,to=<ear@isolar.DynDNS.ORG>: 450 Service temporarily unavailable. Jun 27 11:49:35 isolar courieresmtpd: authdaemon: s_connect() failed: No such file or directory Jun 27 11:49:35 isolar courieresmtpd: [ID 702911 mail.error] error, relay=::ffff:24.130.129.94,ident=root,from=<ear@my.work.do.main>, to=<ear@isolar.DynDNS.ORG>: 450 Service temporarily unavailable. Jun 27 11:49:35 isolar courieresmtpd: [ID 702911 mail.error] authdaemon: s_connect() failed: No such file or directory Jun 27 11:49:35 isolar courieresmtpd: [ID 702911 mail.info] error, relay=::ffff:24.130.129.94,ident="root",msg="502 ESMTP command error",cmd: DATA Jun 27 11:49:35 isolar courieresmtpd: [ID 702911 mail.error] error, relay=::ffff:24.130.129.94,ident=root,from=<ear@my.work.do.main>, to=<ear@isolar.DynDNS.ORG>: 450 Service temporarily unavailable. Jun 27 11:49:35 isolar courieresmtpd: [ID 702911 mail.error] authdaemon: s_connect() failed: No such file or directory Jun 27 11:49:35 isolar courieresmtpd: [ID 702911 mail.info] error, relay=::ffff:24.130.129.94,ident="root",msg="502 ESMTP command error",cmd: DATA

When I tried to use my existing SysV init script (this is Solaris 9), "authdaemond" complained:

Error: authdaemond no longer handles its own daemonizing. Use new startup script.

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.)

(In a perhaps related vein, the shutdown script isn't working, either - "courier stop" is writing a "STOP" to the .../path/to/courier/var/tmp/trigger named pipe, but "courierd" isn't stopping. The "courier stop" times out - SIGALRM - and I have to kill "courierd" manually.)

- Greg

_______________________________________________ courier-users mailing list cour@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users