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=<[EMAIL PROTECTED]>,to=<[EMAIL PROTECTED]>:
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=<[EMAIL PROTECTED]>,
to=<[EMAIL PROTECTED]>: 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=<[EMAIL PROTECTED]>,
to=<[EMAIL PROTECTED]>: 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
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
