On Thu, Jun 24, 2010 at 10:29:25PM +1000, Erik Christiansen wrote: > On Thu, Jun 24, 2010 at 01:08:07PM +0100, Chris G wrote: > > > > > I'm getting the feeling that, maybe, very few people are now using > > mutt with mbox so that an 'out of the box' installation of mutt on > > Linux works fine with maildir but if you switch to mbox it all goes > > very much awry. > > Oh-oh, that's not good news. I have 710 mbox mail files, with more than > 3000 posts in some of them. I suppose I could convert each mbox to a > directory of the same name, but then I'd have to muck for days tuning my > .muttrc, I fear. :-( > > Is mbox actively deprecated by the developers, or has it just become a > corner case? > I wasn't saying I was *sure* of this (mbox not getting tested too well because it's not used much now) but it's just a feeling I am getting as I too had problems moving from 1.4.x to 1.5.x which, at the time, I fixed by moving to maildir.
I am now setting up a new system and decided to move back to mbox (hence my recent posts on this subject) as the advantages *still* outweigh the disadvantages for me. Since my mail delivery goes through a filter script of my own I can 'fiddle' things so that new mail is recognised by mutt. Getting back to your problem I have just realised something, when you copy a mail message to another mailbox it *is* a new message in that mailbox. I have just tried it and I get exactly the same symptoms that you report. However, in my case I never see it because the mailboxes to which I copy mail are not in the 'mailboxes' line in my muttrc. I have just tried the same on my (old) maildir setup and there it *doesn't* seem to think old mail saved in a different mailbox is new mail. -- Chris Green
