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 /
var/spool/mqueue-client.

I've googled quite a bit, but it looks like my file permissions are
correct (pasted down below).


Here's the results of 'mailq':
# mailq
MSP Queue status...
/var/spool/mqueue-client (3 requests)
-----Q-ID----- --Size-- -----Q-Time----- ------------Sender/
Recipient-----------
l3REshtH026057 5 Fri Apr 27 10:54 root
(Deferred: 421 4.3.0 collect: Cannot write ./
dfl3REsh3X026058)
kingstom@newschool.edu
l3RD6Pft017497 5 Fri Apr 27 09:06 root
(Deferred: 421 4.3.0 collect: Cannot write ./
dfl3REe16G030087)
kingstonm
l3R9034w009993 1719 Fri Apr 27 05:00 MAILER-DAEMON
(Deferred: 421 4.3.0 collect: Cannot write ./
dfl3REe12Z030101)
root
Total requests: 3
MTA Queue status...
/var/spool/mqueue is empty
Total requests: 0

[Is it weird that the Q-ID doesn't match up with the name of the file
trying to be written?)


Here's what happens when I manually send a message:
# mail -v kingstom@newschool.edu
Subject: test
test
..
Cc:
kingstom@newschool.edu... Connecting to [127.0.0.1] via relay...
220 www.matthewkingston.com ESMTP Sendmail 8.13.8/8.13.8/Debian-3;
Fri, 27 Apr 2007 10:54:43 -0400; (No UCE/UBE) logging access from:
http://www.matthewkingston.com(OK)-w...ewkingston.com [127.0.0.1]
>>> EHLO www.matthewkingston.com
250-www.matthewkingston.com Hello www.matthewkingston.com [127.0.0.1],
pleased to meet you
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-8BITMIME
250-SIZE
250-DSN
250-DELIVERBY
250
>>> MAIL From:<root@www.matthewkingston.com> SIZE=47
250 2.1.0 <root@www.matthewkingston.com>... Sender ok
>>> RCPT To:<kingstom@newschool.edu>
>>> DATA
250 2.1.5 <kingstom@newschool.edu>... Recipient ok
354 Enter mail, end with "." on a line by itself
>>> .
421 4.3.0 collect: Cannot write ./dfl3REsh3X026058 (bfcommit, uid=0,
gid=102): Permission denied
>>> QUIT
kingstom@newschool.edu... 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

I also see in my /var/log/mail/mail.err the following:

Apr 27 11:35:23 www sm-mta[19565]: NOQUEUE: SYSERR(root):
opendaemonsocket: daemon MSA: cannot bind: Address already in use
Apr 27 11:35:23 www sm-mta[19565]: daemon MSA: problem creating SMTP
socket
Apr 27 11:35:28 www sm-mta[19565]: NOQUEUE: SYSERR(root):
opendaemonsocket: daemon MSA: cannot bind: Address already in use
Apr 27 11:35:28 www sm-mta[19565]: daemon MSA: problem creating SMTP
socket
Apr 27 11:35:33 www sm-mta[19565]: NOQUEUE: SYSERR(root):
opendaemonsocket: daemon MSA: cannot bind: Address already in use
Apr 27 11:35:33 www sm-mta[19565]: daemon MSA: problem creating SMTP
socket
Apr 27 11:35:38 www sm-mta[19565]: NOQUEUE: SYSERR(root):
opendaemonsocket: daemon MSA: cannot bind: Address already in use
Apr 27 11:35:38 www sm-mta[19565]: daemon MSA: problem creating SMTP
socket
Apr 27 11:35:43 www sm-mta[19565]: NOQUEUE: SYSERR(root):
opendaemonsocket: daemon MSA: cannot bind: Address already in use
Apr 27 11:35:43 www sm-mta[19565]: daemon MSA: problem creating SMTP
socket
Apr 27 11:35:48 www sm-mta[19565]: NOQUEUE: SYSERR(root):
opendaemonsocket: daemon MSA: cannot bind: Address already in use
Apr 27 11:35:48 www sm-mta[19565]: daemon MSA: problem creating SMTP
socket
Apr 27 11:35:53 www sm-mta[19565]: NOQUEUE: SYSERR(root):
opendaemonsocket: daemon MSA: cannot bind: Address already in use
Apr 27 11:35:53 www sm-mta[19565]: daemon MSA: problem creating SMTP
socket
Apr 27 11:35:58 www sm-mta[19565]: NOQUEUE: SYSERR(root):
opendaemonsocket: daemon MSA: cannot bind: Address already in use
Apr 27 11:35:58 www sm-mta[19565]: daemon MSA: problem creating SMTP
socket
Apr 27 11:36:03 www sm-mta[19565]: NOQUEUE: SYSERR(root):
opendaemonsocket: daemon MSA: cannot bind: Address already in use
Apr 27 11:36:03 www sm-mta[19565]: daemon MSA: problem creating SMTP
socket
Apr 27 11:36:08 www sm-mta[19565]: NOQUEUE: SYSERR(root):
opendaemonsocket: daemon MSA: cannot bind: Address already in use
Apr 27 11:36:08 www sm-mta[19565]: daemon MSA: problem creating SMTP
socket
Apr 27 11:36:08 www sm-mta[19565]: NOQUEUE: SYSERR(root):
opendaemonsocket: daemon MSA: server SMTP socket wedged: exiting
Apr 27 11:40:01 www sm-mta[30552]: l3RFe16k030552: SYSERR(root):
collect: Cannot write ./dfl3RFe16k030552 (bfcommit, uid=0, gid=102):
Permission denied
Apr 27 11:40:01 www sm-mta[30574]: l3RFe1CH030574: SYSERR(root):
collect: Cannot write ./dfl3RFe1CH030574 (bfcommit, uid=0, gid=102):
Permission denied
Apr 27 11:40:01 www sm-mta[30580]: l3RFe1Fp030580: SYSERR(root):
collect: Cannot write ./dfl3RFe1Fp030580 (bfcommit, uid=0, gid=102):
Permission denied
Apr 27 11:40:02 www sm-mta[30585]: l3RFe1iS030585: SYSERR(root):
collect: Cannot write ./dfl3RFe1iS030585 (bfcommit, uid=0, gid=102):
Permission denied
Apr 27 11:40:02 www sm-mta[30594]: l3RFe2IX030594: SYSERR(root):
collect: Cannot write ./dfl3RFe2IX030594 (bfcommit, uid=0, gid=102):
Permission denied
Apr 27 11:40:02 www sm-mta[30598]: l3RFe2Y0030598: SYSERR(root):
collect: Cannot write ./dfl3RFe2Y0030598 (bfcommit, uid=0, gid=102):
Permission denied
Apr 27 11:40:02 www sm-mta[30611]: l3RFe2hk030611: SYSERR(root):
collect: Cannot write ./dfl3RFe2hk030611 (bfcommit, uid=0, gid=102):
Permission denied
Apr 27 11:40:02 www sm-mta[30613]: l3RFe2Vr030613: SYSERR(root):
collect: Cannot write ./dfl3RFe2Vr030613 (bfcommit, uid=0, gid=102):
Permission denied
Apr 27 11:40:02 www sm-mta[30617]: l3RFe2cS030617: SYSERR(root):
collect: Cannot write ./dfl3RFe2cS030617 (bfcommit, uid=0, gid=102):
Permission denied

Any thoughts? Thanks, Matt

In news:1177688628.853841.141260@r35g2000prh.googlegr oups.com,
Matt <hitormiss@gmail.com> 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
> /var/spool/mqueue-client.
>
> I've googled quite a bit, but it looks like my file permissions are
> correct (pasted down below).
....
> kingstom@newschool.edu... 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

${source}/sendmail/SECURITY states:

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.

In article <59es3oF2kke5dU1@mid.individual.net> "ynotssor"
<ynotssor@example.net> writes:
>In news:1177688628.853841.141260@r35g2000prh.googlegr oups.com,
>Matt <hitormiss@gmail.com> 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
>> /var/spool/mqueue-client.
>>
>> I've googled quite a bit, but it looks like my file permissions are
>> correct (pasted down below).
>...
>> kingstom@newschool.edu... 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
>
>${source}/sendmail/SECURITY states:
>
>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).

--Per Hedeland
per@hedeland.org

Am Fri, 27 Apr 2007 08:43:48 -0700 schrieb Matt:

> I just upgraded (via apt-get) to the new Stable (etech) version of
> Debian (from sarge).

[...]

> Any thoughts? Thanks, Matt

Upgrade documentation for Sendmail ships with the new Debian release.
Please read and follow it.

Alexander