Red Hat Bugzilla – Bug 120196
Wrong permission for /var/spool/mail causes error and problems
Last modified: 2014-03-16 22:43:58 EDT
Description of problem:
After the new filesystem RPM I found the following in my log file
each time there was a pop3 connection:
--- snipp ---
Apr 6 16:42:13 tux ipop3d: Mailbox vulnerable - directory /var/spool/mail must have 1777 protection
--- snapp ---
Version-Release number of selected component (if applicable):
How reproducible & Steps to Reproduce:
1. Install the latest filesystem RPM
2. Do a pop3 connection to receive mails or access mailbox via mutt
3. Get the error - or mutt displays that the mailbox is readonly,
otherwise you find it in the maillog as written above.
The permission to /var/spool/mail is wrong set in the spec file in
the files section.
--- filesystem.spec 2004-03-16 21:49:24.000000000 +0100
+++ filesystem.spec.rsc 2004-04-06 20:30:22.000000000 +0200
@@ -86,7 +86,7 @@
Would be nice if that solution or a better one would be used to
fix the problem. Thank you :-)
Your imap package is broken; it should not be warning about this.
So my (that means your latest build) of mutt is also broken?!
Mutt says here - if /var/spool/mail isn't 1777 - that the mailbox only
is readonly available...
I don't see that. I am able to read, for example,
/var/spool/mail/notting in read-write mode just fine - this is with
What does 'mutt -v' say for you?
Nothing special, but the problem seems to be a (old?) %pre or %post
from a package, that changed all mailboxes to 600 instead of 660 :-(
And then it is correct, that +t for /var/spool/mail is needed *g*
Okay, you are right...notabug, only the package that set the permission
from 660 to 600 has a bug ;-)