Bowie Bailey writes:
I built Courier-authlib as a normal user:rpmbuild -tb --define 'xflags --with-mailuser=mailuser --with-mailgroup=mailuser' sources/courier-authlib-0.57.tar.bz2
The courier-authlib spec file does not process the xflags variable. This is ignored.
When I look at the build output, I see:
... --with-mailuser=courier --with-mailgroup=courier ...
Right, that's why.
I don't think it really matters what user the authdaemon uses, but it
would be nice to be able to specify. In any case, this shouldn't affect
my current problem (I don't think).
I then installed the rpms:
rpm -i courier-authlib-0.57-1.x86_64.rpm
courier-authlib-devel-0.57-1.x86_64.rpm
courier-authlib-ldap-0.57-1.x86_64.rpm
courier-authlib-userdb-0.57-1.x86_64.rpm
I extracted the Courier tarball, modified submit.C to remove the header
limit, and modified the courier.spec file to prevent it from dying on
unpackaged files. I then re-created the tarball.
Then, I built Courier from my new tarball:
rpmbuild -tb --define 'xflags --with-mailuser=mailuser
--with-mailgroup=mailuser' sources/courier-0.52.1.tar.bz2
That might be the problem.Although the courier specfile does implement the xflags option, Courier must use the same uid/gid as the courier-authlib package, and, by default, Courier's configure script gets the uid/gid settings from the courier-authlib package, and you overrid them with something else.
This _might_ explain some of your problems.I suggest that you remove just the courier package, leave the courier-authlib packages in place, remove /usr/lib/courier, /var/spool/courier, /etc/courier, then rebuild the courier rpm without any options.
# service courier start
Starting Courier mail server:/var/spool/courier/tmp/courierfilter.pid:
Permission denied
Another thing to check is the permissions on the /var and /var/spool directories.
pgpUOZNWx9chW.pgp
Description: PGP signature
