atom feed5 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 
Subject:Re: [courier-users] Problems connecting to authdaemon after upgrading (0.44.2 -> 0.50.0)
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Jun 27, 2005 12:26:47 pm
List:net.sourceforge.lists.courier-users

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.