both 0.40.2 and 0.41 ebuilds of courier probably "forget" to give correct ownership to "/var/run/courier". Giving "mail:mail" to it will fix the problem. Reproducible: Always Steps to Reproduce: 1. Install courier.ebuild and configure it 2. try to run and watch the error message 3. chane the ownership and watch that no error message anymore Actual Results: error message "/var/run/courier/courierfilter.pid: Permission denied" Expected Results: no error message By the way, courier-0.41 really fixes another bug: broken init script of courierfilterd. So, perhaps 0.41 should be unmasked as it has just one minor bug compared to (unmasked) 0.40.2, which has two bugs: one (minor) described above, and another (major) of broken init script. I keep a severuity as normal: it's a minor effort to fix it, but without the fix it's a major system malfunctioning (no mail).
I've gave up on courier by different reasons anyway. Besides, just before I've gave up, I've noticed in recent courier ebuilds that this problem with permissions doesn't happen anymore. So, unless anyoneelse confirm this bug and want to track it furter, I suggest to close it. Sorry for being such a pain.
I have courier(0.41) on 4 different boxes and they all do the same thing. The permissions change fixes it on every one of them. It never occured to me to change the permissions. BTW I know courier and their "developer(s)" are tough to deal with, but you shouldn't hold that against the software.
0.42.2 is on it's way into portage soon which has this permissions fix.
courier-0.42.2 has been added.
