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 chrisisbd
Recipients chrisisbd
Date 2010-08-10.16:40:04
SpamBayes Score 2.27449e-10
Marked as misclassified No
Message-id <1281458408.75.0.432136903483.issue9559@psf.upfronthosting.co.za>
In-reply-to
Content
When you call mailbox.mbox.add() the old mbox file is copied, the new file is modified and then renamed to the name of the'old' mbox file.

This breaks the way that many MUAs detect and manage new mail in an mbox, in particular I discovered this with mutt.  If the python process writing the mbox and mutt are on the same system writing a local file then you get the message "Mailbox was externally modified. Flags may be wrong." from mutt (and various odd things can happen).  If mutt is reading the mbox over NFS then you get a "Stale NFS file handle" error.

This should be strongly noted in the documentation for mailbox.mbox, in addition it would be really nice if there was a mailbox.mbox.append() method which *really* appends the data to the end of the mbox rather than changing it completely.

Most MDAs (all?) do just append new mail to the end of the mbox and I feel that python should really try and do the same.
History
Date User Action Args
2010-08-10 16:40:09chrisisbdsetrecipients: + chrisisbd
2010-08-10 16:40:08chrisisbdsetmessageid: <1281458408.75.0.432136903483.issue9559@psf.upfronthosting.co.za>
2010-08-10 16:40:07chrisisbdlinkissue9559 messages
2010-08-10 16:40:04chrisisbdcreate