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 r.david.murray
Recipients r.david.murray, sdaoden
Date 2011-05-05.15:47:03
SpamBayes Score 9.798091e-05
Marked as misclassified No
Message-id <1304610424.6.0.254596604566.issue11935@psf.upfronthosting.co.za>
In-reply-to
Content
Steffen, your sense of humor is great, but oftentimes I have no clue what you are talking about.  Where does ftruncate factor in?

I was asking what mutt does when it modifies a file in the hopes that it had some pithy algorithm for making sure the mailbox atime and utime conform to the semi-standard you are talking about, so we could steal it.

I'd like to see a solution to this issue.  My two problems with your patch are (1) it feels wrong to set the atime earlier than the last actual atime and (2) unconditionally doing the work in flush means it might get set even when there wasn't an intended "new mail" condition.

In other words, I think the fix is ugly :).  However, neither of those concerns are necessarily blockers.  Practicality beats purity in many cases, and this may be one of them.
History
Date User Action Args
2011-05-05 15:47:04r.david.murraysetrecipients: + r.david.murray, sdaoden
2011-05-05 15:47:04r.david.murraysetmessageid: <1304610424.6.0.254596604566.issue11935@psf.upfronthosting.co.za>
2011-05-05 15:47:03r.david.murraylinkissue11935 messages
2011-05-05 15:47:03r.david.murraycreate