bike...@cox.net writes:
I have just built up a new server using RHEL4 update 4 and have Courier 0.54.2
and Courier Authlib 0.59 installed.
The Courier packages were installed using rpmbuild -ta to create rpms and the
rpm -ivh was used to install Authlib and Courier. rpmbuild was executed as a
standard user. The rpm install was run as user = root. Defaults were used all
the way through.
Jan 25 21:17:24 srvr courieresmtpd: started,ip=[::ffff:138.163.0.38]
Jan 25 21:17:28 srvr courieresmtpd:
error,relay=::ffff:138.163.0.38,from=<firs...@navy.mil>,to=<use...@mycompany.org>:
450 Service temporarily unavailable.
Jan 25 21:17:28 srvr courieresmtpd: authdaemon: s_connect() failed: Permission
denied
That indicates that the permissions/ownership on the authdaemon socket are
broken.
That should not happen, with an rpm build with default options.
You _did_ install the courier-authlib, and courier-authlib-devel rpms first,
before building the courier rpms, correct?
If so, check if something is corrupted:
rpm -V courier-authlib
rpm -V courier
Presuming that rpm -V comes up clean, look at who owns
/var/spool/authdaemon and who owns
/usr/lib/courier/libexec/courier/modules/esmtp/courieresmtpd
Both /var/spool/authdaemon (directory) and ../courieresmtpd (binary) should
be owned by the same userid.
2 messages in net.sourceforge.lists.courier-usersRe: [courier-users] 450 Service tempo...
