Date: Mon, 2 Feb 2004 04:33:27 +0100 From: Lorenzo Perone <lopez.on.the.lists@yellowspace.net> To: ports@FreeBSD.org Subject: /usr/ports/mail/courier 0.44.2 broken? uid: courier? mailnull? Message-ID: <90359758-5530-11D8-87F4-003065D57494@yellowspace.net>
next in thread | raw e-mail | index | archive | help
Hello, I "just" tried to portupgrade, more than one time, to the 0.44.2 port of courier, coming from a 0.42.0. After installation (tried via portupgrade and via make) the esmtpd daemon didn't work (imapd did, and so did mysql authorization, as well as webmail). when starting, I get a: courierfilter: /var/spool/courier/tmp/courierfilter.pid: Permission denied After starting, the log shows the following: Feb 2 03:21:41 mail courierd: Started ./courieresmtp, pid=81013, maxdels=40, maxhost=4, maxrcpt=100 Feb 2 03:21:41 mail courierd: Started ./courierdsn, pid=81015, maxdels=4, maxhost=1, maxrcpt=1 Feb 2 03:21:41 mail courierd: Started ./courieruucp, pid=81017, maxdels=4, maxhost=4, maxrcpt=16 Feb 2 03:21:41 mail courierd: queuelo=200, queuehi=400 Feb 2 03:21:41 mail courierd: Purging /var/spool/courier/msgq Feb 2 03:21:41 mail courierd: Purging /var/spool/courier/msgs Feb 2 03:21:41 mail courierd: Permission denied Feb 2 03:21:41 mail courierd: ABNORMAL TERMINATION, exit status: 1 the command /usr/local/etc/rc.d/courier.sh stop produces an Alarm when trying to shut down courierd, which I have to kill by hand. I tried re-installing several times, and making sure that the courier (uid 62) user is able to read / write in those files/dirs, but it didn't work out. Then I downgraded to 0.44.0, and while it all seemed to work at the beginning, I noticed that esmtpd was producing Permission denied: warnings as well, and also the courierfilter.pid file couldn't be written. So I had a further looked into the /var/spool/courier directory, and noticed that some dirs had (which was a new observation for me) the group 26, 'mailnull'. I think this is new since I installed courier 0.42.0 in november: -r-------- 1 mailnull mailnull 0 Feb 2 03:58 .noident drwxr-x--- 2 mailnull mailnull 512 Oct 5 18:36 allfilters/ drwxrwx--- 2 mailnull mailnull 512 Feb 2 04:10 authdaemon/ -rw-rw-rw- 1 courier courier 524288 Oct 17 00:09 couriersslcache drwxr-x--- 2 mailnull mailnull 512 Oct 5 18:36 filters/ drwxr-x--- 3 mailnull mailnull 512 Feb 2 04:07 msgq/ drwxr-x--- 9 mailnull mailnull 512 Feb 2 04:13 msgs/ -rw-rw-rw- 1 courier courier 0 Feb 2 00:09 sqwebmail.sock.lock -rw-rw-rw- 1 courier courier 6 Feb 2 03:23 sqwebmail.sock.pid drwxrwx--- 6 mailnull mailnull 512 Feb 2 04:10 tmp/ I invited courier to the group 'mailnull' in /etc/group, and now I have no warnings. Also, good thing that I made a backup of my /usr/local/etc/courier, because acceptmailfor and several other files were just OVERWRITTEN by the portupgrade! :( I hope that my information can be useful to fix the port; Which user is now actually used by courier? I am a little confused...! Please take the time to write a warning in case the uid has changed. Also, if You believe I have made any mistake when installing, please let me know. It was a long night... Thanx for Attention, Lorenzo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?90359758-5530-11D8-87F4-003065D57494>