[neomutt-users] One or more messages could not be displayed... (?)

[Baron Fujimoto]

On Fri, 18 Jan 2019, Andrew Sullivan wrote:

> On Sat, Jan 19, 2019 at 04:59:28AM +0100, tuxic at posteo.de wrote:
>> Then - while searching - the message pops up, saying:
>> "One or more messages could not be displayed." I have
>> identified that message and could display it with a
>> normal text editor. Permissions are set correctly.
>> The message is not displayed in the listing even if not
>> as result of a search. It seems to be permanently
>> "hidden".
>
> My experience is that this is always a corrupt cache, either the
> headers or the body.  I just go in and blow away the cache (or if I'm
> ambitious, the particular cache entry, but usually I'm in too much of
> a hurry to debug that far) and it works.

I use the following for these quick cache fixes. I notice my cache usually seems to get corrupted when my system loses its connection to the IMAP host (GMail, in my case, and not uncommon for whatever reason)[*]

Quit mutt, then execute (is there a way to get neomutt to reread the cache without quitting and restarting?):

     find ~/.mutt/cache -size 0 -exec rm {} \

I've created a function for it in my bash resource files

function fix_mutt_cache () {
     find ~/.mutt/cache -size 0 -exec rm {} \;
}

[*] FWIW, mutt seemed to be much more robust than neomutt about not being susceptible to or recovering from these glitches. It's currently the most annoying "feature" of neomutt in my experience. But MacPorts has supplanted mutt with neomutt for its "mutt" port so...