Ralph Geier muttered: > I found the following bug in Mutt 1.2.5 / 1.3.24 > > - first, save your 'mbox'-file (i.e. the folder where read mail is > saved), it will be corrupted after trying the following! > > - assume you have 1 new message in your spool mailbox (i.e. incoming > mail) > > - call mutt, have a look at the message, go back to the index, but do > not leave mutt > > - now call a 2nd instance of mutt, you can see the message (as new), > now delete the message and quit this instance of mutt > > - go back to the program you called first, no quit this, too > > -> a message appears "Reopening mailbox..." - and nothing else > happens > > -> hitting 'q' a second time quits mutt > > -> some Status lines are appended to the 'mbox'-file, nothing else > (i.e. not the whole mail, which would be wrong anyway, because we > deleted the message) > > (Interestingly, if you started with an empty mbox, you will find the > following: while mutt will recognize it as corrupted under normal > circumstances - if you repeat the procedure above, the error is > obscured now, so remove your mbox to reproduce the bug again!) > > OS: ReliantUNIX-Y
Ralph, I could not verify this behavior. I fact I do what you describe all the time. In the 2nd instance of mutt the message disapears and I get the following message: Mailbox was externally modified. Flags may be wrong. OS: Linux with Kernel 2.4.3 > Configuration: see app. While quickly reading your muttrc, I could not find something fishy. HTH, Michael -- PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key
