This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author petri.lehtinen
Recipients akuchling, doko, olau, petri.lehtinen, pitrou, sdaoden
Date 2012-06-18.18:35:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1340044542.39.0.423004859199.issue7359@psf.upfronthosting.co.za>
In-reply-to
Content
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 avoid messing up the mailboxes because of concurrent access.

In Debian, /var/mail is owned by root:mail with mode 2755, and every MUA is setgid mail. See the Debian Policy Manual section 11.6 for more information:

    http://www.debian.org/doc/debian-policy/ch-customized-programs.html#s-mail-transport-agents

If you write a MUA or MTA using Python's mailbox module, your program needs to have write access to /var/mail. That's the only way to do it correctly. It also makes the mailbox module's renaming behavior possible.
History
Date User Action Args
2012-06-18 18:35:42petri.lehtinensetrecipients: + petri.lehtinen, akuchling, doko, pitrou, olau, sdaoden
2012-06-18 18:35:42petri.lehtinensetmessageid: <1340044542.39.0.423004859199.issue7359@psf.upfronthosting.co.za>
2012-06-18 18:35:41petri.lehtinenlinkissue7359 messages
2012-06-18 18:35:41petri.lehtinencreate