Either pine-4.21-8 or filesystem-1.35-1 needs to be fixed to not complain that /var/spool/mail should be set 1777: [Mailbox vulnerable - directory /var/spool/mail must have 1777 protection] but filesystem-1.35-1 sets /var/spool/mail 775
I can't reproduce that warning here (4.21-17, but I don't think I've changed anything related to this) The directory should of course be 1775
If you are sure that /var/spool/mail should have permissions 1775, somebody (you) should upload a new version of filesystem to errata. This is the same bug as 10687. http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=10678 cu andreas
$ rpm -vv -ql filesystem ... filesystem-1.3.5-1 ... drwxrwxr-x 1 root mail 1024 Feb 6 1996 /var/spool/mail It looks like someone needs to make the call that either pine or the filesystem package is correct about what the perms on /var/spool/mail/ should be and get them to agree. Right now they do not. Depending on the configuration of sendmail, either 1777 or 775 is valid, but the other mail programs need to be checked (imap/pop referenced in the previously mentioned bugzilla entry, pine in this one) to verify correct operation given the "correct" permissions. that setup.
Sorry, I thought you were talking about rawhide. Anyway, I cannot reproduce your warning on a 6.2 system either: It just doesn't happen here. Can you attach your .pinerc for one last check?
Sorry if I made this impression, but *I* do not use pine. I only know the same error-message from bug 10687 (imapd), which still has Status: NEW. (Perhaps the original submitter used pine as imap-client, which forwarded imapd's error-message?) Perhaps you could close 12356 and reassign 10678 to Component: filesystem or fix it and close it. thank's and cu andreas
Created attachment 638 [details] sample pinerc
I can not reproduce the pine problem at all with the Rawhide packages (nor with the 6.2 ones). Closed. I'll have look at the other issue - I don't think we want 1777.
This is NOT a bug and you don't need to solve it, yes the message is annoying, but you will need to think further if you think that eliminating this message does really solve this problem. Please read the following thread in comp.mail.pine in order to understand why you should not supress this annoying message. http://x60.deja.com/threadmsg_ct.xp?AN=714347127.1&mhitnum=0&CONTEXT=979262262.1692729372
The standard for locking mail spool files on Red Hat Linux is lockf, not .lck-files - and all things touching the file have been fixed to use that (everything distributed with the distribution, at least - we obviously don't control what people install in additon to this). Since there is no need to create files, the permissons shouldn't be 1777 and the message is silenced.