Starting up sendmail I get:
Starting sm-client: can not chdir(/var/spool/clientmqueue/): Permission denied Program mode requires special privileges, e.g., root or TrustedUser.
I assume the user used for sm-client is smmsp. However, that user has /var/spool/mqueue as homedir and I added him to the trusted users list. FYI, that user has disabled login (which should be okay) and the group has a pre-encrypted password by default. On Suse the client queue runner is run by user mail:mail which also has login disabled but no password for the group.
What do I need to change, so that sm-client runs okay on CentOS?
Kai
Am Mi, den 22.03.2006 schrieb Kai Schaetzl um 18:17:
Starting up sendmail I get:
Starting sm-client: can not chdir(/var/spool/clientmqueue/): Permission denied Program mode requires special privileges, e.g., root or TrustedUser.
I assume the user used for sm-client is smmsp. However, that user has /var/spool/mqueue as homedir and I added him to the trusted users list.
No! Please don't add user smmsp to the trusted users.
FYI, that user has disabled login (which should be okay) and the group has a pre-encrypted password by default. On Suse the client queue runner is run by user mail:mail which also has login disabled but no password for the group.
What do I need to change, so that sm-client runs okay on CentOS?
Kai
Typical reason is you broke the permissions of the sendmail binary. Check that it is
$ ls -al /usr/sbin/sendmail.sendmail -rwxr-sr-x 1 root smmsp 732248 21. Feb 2005 /usr/sbin/sendmail.sendmail
(Security update pending - hope package gets soon through.)
Alexander
Alexander Dalloz wrote on Wed, 22 Mar 2006 19:27:05 +0100:
Typical reason is you broke the permissions of the sendmail binary. Check that it is
$ ls -al /usr/sbin/sendmail.sendmail -rwxr-sr-x 1 root smmsp 732248 21. Feb 2005 /usr/sbin/sendmail.sendmail
It's exactly like this. I didn't touch any of that at all. I replaced the sendmail.cf, though, with my own one from Suse systems with 8.12. Everything seemed to be working fine until I installed MailScanner which doesn't check for the existance of sm-client.pid and restarts sm-client each time while sendmail seems to only start it when the pid file is missing. I see if reverting to the old sendmail.cf fixes this. No, same problem, so my sendmail.cf isn't the problem. I also found that there was no .hoststat directory in the queue directory and sendmail barked about that as well. Is this normal for CentOS?
Kai
Am Mi, den 22.03.2006 schrieb Kai Schaetzl um 23:03:
Alexander Dalloz wrote on Wed, 22 Mar 2006 19:27:05 +0100:
Typical reason is you broke the permissions of the sendmail binary. Check that it is
$ ls -al /usr/sbin/sendmail.sendmail -rwxr-sr-x 1 root smmsp 732248 21. Feb 2005 /usr/sbin/sendmail.sendmail
It's exactly like this. I didn't touch any of that at all. I replaced the sendmail.cf, though, with my own one from Suse systems with 8.12.
Very bad idea. If you really want to migrate settings from a SuSE install then take the sendmail.mc settings and rebuild the sendmail.cf from those settings on your CentOS host. And be sure you understand what settings you activate.
Everything seemed to be working fine until I installed MailScanner which doesn't check for the existance of sm-client.pid and restarts sm-client each time while sendmail seems to only start it when the pid file is missing. I see if reverting to the old sendmail.cf fixes this. No, same problem, so my sendmail.cf isn't the problem. I also found that there was no .hoststat directory in the queue directory and sendmail barked about that as well. Is this normal for CentOS?
It is normal that Sendmail on CentOS runs out of the box. It is too "normal" that hoststat isn't configured by default within sendmail.mc. But there is no problem to activate this yourself. You need to understand how MailScanner mangles the Sendmail setup as it splits the queue and runs own queue runner from its own.
Kai
Just copying over SuSE Sendmail setup will not work.
Alexander
Alexander Dalloz wrote on Wed, 22 Mar 2006 23:21:17 +0100:
Very bad idea. If you really want to migrate settings from a SuSE install then take the sendmail.mc settings and rebuild the sendmail.cf from those settings on your CentOS host. And be sure you understand what settings you activate.
That's what I did, I always use my custom m4 and mc files to build the cf, sorry, if that wasn't clear.
I finally found the reason for the problem. I had moved over the mail spool with a tarball and for a reason I don't remember I tarred spool/mail from var and when untarring on the other machine that removed some privileges from /var/spool. Sorry for taking your time.
Kai
-
Alexander Dalloz -
Kai Schaetzl