This ebuild lacks the knowledge of how courier works... and made clear that its mantainer doesn't use courier. I suggest to read the manpage dot-courier(8) in which is made clear what a .courier file is meant for: "The file $HOME/.courier specifies how messages are delivered to this account. If this file does not exist, default instructions set by the system administrator are used. The system administrator's default instructions specify the location of the account's system mailbox." So if you place a default .courier file in all users HOME you'll disable The system administrator's default instructions! Reproducible: Always Steps to Reproduce: 1. Just Use It 2. 3.
I inherited the ebuild from somebody else, so all I can attest to is that it works. I do use courier at home and (former) work. I've never had any problems. Your point (while rudely stated) does make some sense though. I'll try and track down the original author and see if there was some reason he did it that way.
>I've never had any >problems. Your point (while rudely stated) does make some sense though. Sorry for beeing rude. About the fact that it works, it works well until you do not set DEFAULTDELIVERY in /etc/courier/courierd (with your favourite editor or through the webadmin). Suppose that you want to use maildrop filtering and so you set: DEFAULTDELIVERY="| /usr/bin/maildrop" than you create your .mailfilter and you'll see that it'll simply be ignored. And this is very bad because one of the best features of courier is the fact that you can create filters through the webmail!!!
see my email, but comment here please
Okay, I fixed this in cvs to not install the .courier file anymore. I also made a few other changes to the ebuild, let me know if you have any luck with the new version. BTW, courier-0.44.0 snuck out and I missed it, that's the one you want to try. It may take a little while to hit rsync.
