[issue7359] mailbox cannot modify mailboxes in system mail spool

Mahmoud Hashemi added the comment: Got bit by this, and since it's not a bug, here's "not" a fix: http://boltons.readthedocs.org/en/latest/mboxutils.html#boltons.mboxutils.mbox_readonlydir Been in production for a while, working like a charm. Might there be interest in including this in the st

[issue7359] mailbox cannot modify mailboxes in system mail spool

Petri Lehtinen added the comment: Every program that accesses mailboxes in the system-wide mail spool directory needs to have write access to it. This is because dot-locking is achieved by creating additional files to that directory, and it must be used (in addition to fcntl() locking) to avo

[issue7359] mailbox cannot modify mailboxes in system mail spool

Steffen Daode Nurpmeso added the comment: Issue #11935 becomes gigantic and may even swamp this one over! -- nosy: +sdaoden ___ Python tracker ___ ___

[issue7359] mailbox cannot modify mailboxes in system mail spool

Ole Laursen added the comment: Just got bitten by this too. Renaming is good and all, but as far as I can tell, it will never work with the system spool. It's not just that you can't create a temporary file in the directory, you can't rename files into it either. If I create an empty file so

[issue7359] mailbox cannot modify mailboxes in system mail spool

Antoine Pitrou added the comment: The same remark as in issue7360, that is it is not robust at all to overwrite the file rather than doing an atomic rename from a temporary file. The only possible exception would be if you only /append/ to the mbox file (and that's assuming all mailbox-reading s

[issue7359] mailbox cannot modify mailboxes in system mail spool

New submission from Matthias Klose : no change in behaviour in 2.6 the mailbox module in python 2.5 cannot modify mboxes in read-only directories, e.g. the system mail spool. This is because mailbox._singlefileMailbox.flush() tries to write the modified mailbox to a temporary file and then rena