On 2011-09-26 12:53:17 +0200, Santiago Vila wrote: > Of course there was no such file. If you were using mutt at the same > time, then mutt probably moved the file somewhere to Mail/Maildir/cur/*, > as that's how Maildir works.
Of course, I checked that the mail wasn't moved to cur (and I grepped the whole Maildir directory recursively). (Or for some reason, Mutt moved the mail to "cur" then deleted it in my back.) > > Of course, I can't exclude a file system bug or a bug in Mutt (which > > I was using at the same time). Does procmail avoid any race condition > > with MUA's by doing the right thing when dealing with maildir? > > Yes, and by design. That's the very reason Maildir exist. procmail > puts new emails in "new". MUAs simply move the files to "cur". I fear that's not sufficient: putting an e-mail in "new" must be done in an atomic operation, usually by using "tmp" first. But anyway, according to the timestamps, procmail seems to use it. > If you lost email, I'm very sorry, but filing a critical bug against > procmail (or any other package) without a way to reproduce the bug > is pretty useless. Unfortunately, this may be very difficult to reproduce. I suppose that there is some race condition somewhere. I don't know either if I lost other mail I didn't expect. I think the best I can do is to make Mutt log all its file operations in a Maildir folder in case the problem occurs again, and check that all non-explicitly deleted file is still present via cron. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <http://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
