Re: Errors after upgrade to new Debian Stable
- From: per@xxxxxxxxxxxx (Per Hedeland)
- Date: Fri, 27 Apr 2007 19:22:15 +0000 (UTC)
In article <59es3oF2kke5dU1@xxxxxxxxxxxxxxxxxx> "ynotssor"
Matt <hitormiss@xxxxxxxxx> wrote:
I just upgraded (via apt-get) to the new Stable (etech) version of...
Debian (from sarge).
Now my mail delivery is not working -- messages are getting stuck in
I've googled quite a bit, but it looks like my file permissions are
correct (pasted down below).
kingstom@xxxxxxxxxxxxxxxx Deferred: 421 4.3.0 collect: Cannot write ./
dfl3REsh3X026058 (bfcommit, uid=0, gid=102): Permission denied
Closing connection to [127.0.0.1]
Here's the file permissions on my mail queue directories
1 drwxr-s--- 2 smmta smmsp 1024 Apr 26 23:26 mqueue
1 drwxrws--- 2 smmsp smmsp 1024 Apr 27 11:11 mqueue-client
The following permissions should be used:
-r-xr-sr-x root smmsp ... /PATH/TO/sendmail
drwxrwx--- smmsp smmsp ... /var/spool/clientmqueue
drwx------ root wheel ... /var/spool/mqueue
-r--r--r-- root wheel ... /etc/mail/sendmail.cf
-r--r--r-- root wheel ... /etc/mail/submit.cf
[Notice: On some OS "wheel" is not used but "bin" or "root" instead,
however, this is not important here.]
That is, the owner of sendmail is root, the group is smmsp, and
the binary is set-group-ID. The client mail queue is owned by
smmsp with group smmsp and is group writable. The client mail
queue directory must be writable by smmsp, but it must not be
accessible for others.
So this would seem to be fulfilled in the OP's case, the problem is
rather that mqueue isn't owned by root (which matches the fact that the
MSP is logging a problem that the MTA reports, which explains why the
queue IDs are different).
- Prev by Date: Re: sendmail default queue settings
- Next by Date: Re: different server certificate for each daemon
- Previous by thread: Re: Errors after upgrade to new Debian Stable
- Next by thread: Re: Errors after upgrade to new Debian Stable