Bowie Bailey wrote: > From: Gordon Messmer [mailto:[EMAIL PROTECTED] > >>Bowie Bailey wrote: >> >>>Same deal. /var/spool/courier/msgq (and msgs) has the proper > > permissions > >>>and ownership. Maybe something got screwed up during the build. Unless >>>someone else can come up with another option, I may remove Courier >>>completely, rebuild the RPMS, and reinstall. >> >>That is what you will have to do. You must make sure that the users >>present on your build system are also available on the >>production systems. > > > The build system IS the production system. > > I just removed all of the courier rpms (except for authlib, which seems to > be > working properly), and rebuilt them from source. Reinstalled and the same > problem occurred again. > > I am building the same way I have on the rest of my servers: > > - extract the tarball > - modify the spec file > %define with_fax 0 > %define _missing_doc_files_terminate_build 0 > %define _unpackaged_files_terminate_build 0 > - modify submit.C to increase the headerlimit > - recreate the tarball > - rpmbuild -tb --define 'xflags --with-mailuser=mailuser > --with-mailgroup=mailuser' courier-0.52.1.tar.bz2 > > The only difference that I can think of is that this is an x86_64 system and > the rest of them have been i386. Would that affect the build process enough > to cause this type of problem? > > Bowie
Have you checked that the mailuser uid and gid exists? Other than that I'm fresh out of ideas. // Fredrik ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
