Reverting to net-mail/mailbase-0.00-r5 fixes the problem. Evolution is =mail-client/evolution-2.0.2.
Also breaks mutt -- mailbox is opened in read-only mode. Reverting to -r5 fixed both evolution and mutt for me.
chmod 1777 /var/spool/mail fixes the problem
Same happens with net-www/mozilla-1.7.3. Changing the permissions of /var/spool/mail to 1777 fixes that as well.
Daniel, I saw your name in bug #16749. CCing you to see if you can help with the issue?
I've been on -r6 since July, use both Evolution-2.0.2 and mutt on different boxes and haven't seen this problem at all. langthang asked me to note this.
pulling this in last night left me with nightmares. changing to 1777 works again. but as bug 8029 mentions, other distros works. What gives?
*** Bug 74847 has been marked as a duplicate of this bug. ***
Many mail clients needs to be recompiled after this change. For example mutt has a configure check for it, and if it has 775, it installs sgid wrapper (mutt_dotlock). On my machine, at least mutt, mozilla and evolution work with 775 without any problems.
That may work for mutt, but recompiling pine and uw-imap don't fix their whining (as those were what I reported were broken in bug 74847).
I cannot confirm what was stated in comment #8. On my machine mozilla-1.7.3 and mozilla-1.7.5 do not work with permissions 775 on /var/spool/mail. Recompilation did not help.
can any of the net-mail herd comment ? Obviously there is some sort of problem here introduced by the new mailbase. If it's a permission issue, what is the reason not to revert the change ?
I just installed a new gentoo system and evolution works with mailbase-0.00-r6.
Neither pine nor uw-imap are going to work correctly without a 1777 mail spool unless you use an external setgid-mail locking utility, such as mlock. See http://www.washington.edu/imap/IMAP-FAQs/index.html#7.10 which also applies to pine. The uw-imap ebuild installs /usr/bin/mlock, but doesn't make it setgid mail. See bug 16749 for background on why the default perms were changed. I think it was pretty short-sighted to change the perms without verifying that the clients still worked, but there ya go.
The permissions set by mailbase are correct. I've pinged some evolution and mutt users (i use mutt with no problems) and they have no problems with that permissions. I think mutt and evolution check those permissions at compilation time and there is nothing we can do about it. Is anyone still having this problem ? Cheers, Ferdy
Hello, now, everything seems to work fine with the following versions: - evolution 2.0.4 - mailbase 0.00-r8 Thanks Jo
Hello, now, everything seems to work fine with the following versions: - evolution 2.0.4 - mailbase 0.00-r8 Thanks Joël
I think this one was probably related to older versions of evolution/mailbase or something like that. It's something we just can't fix. Reopen if you still get a non-expected behavior. Cheers, Ferdy