Subject: postfix permissions
To: NetBSD Cobalt list <port-cobalt@NetBSD.org>
From: Brian McEwen <bmcewen@comcast.net>
List: port-cobalt
Date: 12/03/2005 06:29:55
postfix worked for me as built with 1.6.1, but with the -current  
build there are permission problems.

I'm not sure if I need to set something for the postfix executable or  
if I need to just open up permissions on some directories.  I looked  
a bit and I'm not sure why it didn't just set everything up the way  
it needs as it did before.

For example, with a -current system from July 2005,  and a pkgsrc  
from about 3 weeks ago, postfix will build, run, listen on ports fine,
neither sendmail or postfix will be able to send messages-- they  
don't have permissions for neede ddirectories, but opening up  
permissions give me warnings about dangerous permissions and things  
still fail.

For example:

Dec  3 06:04:02 bmcewen postfix/postfix-script: starting the Postfix  
mail system
Dec  3 06:04:02 bmcewen postfix/master[24815]: daemon started --  
version 2.1.5
Dec  3 06:04:50 bmcewen sendmail[25332]: NOQUEUE: SYSERR(root): can  
not chdir(/var/spool/clientmqueue/): Permission denied
Dec  3 06:18:17 bmcewen sendmail[25013]: NOQUEUE: SYSERR(root): can  
not chdir(/var/spool/clientmqueue/): Permission denied
Dec  3 06:20:00 bmcewen sendmail[25485]: NOQUEUE: SYSERR(root): can  
not chdir(/var/spool/clientmqueue/): Permission denied

and opening up the directory gives:

Dec  3 06:21:31 bmcewen sendmail[25234]: NOQUEUE: SYSERR(root): can  
not write to queue directory /var/spool/clientmqueue/ (RunAsGid=17,  
required=0): Permission denied
Dec  3 06:21:31 bmcewen sendmail[25234]: dangerous permissions=40775  
on queue directory /var/spool/clientmqueue/

How am I supposed to invoke postfix to that it works properly?  And,  
the system sendmail had the same problem at initial setup of the  
system, but I didn't care as I was goign to switch to postfix anyway...

thanks,

Brian