8 Feb
2023
8 Feb
'23
9:29 p.m.
Another user who reported this simply removed the underlying files. Turned out for whatever reason a couple of malformed messages (missing headers and message bodies) were stuck there. Of course, the program tries to parse those messages into the held messages view. That's likely generating your error.
On my 3.3.3 installation I had similar errors related to permissions so it was easier to identify where the messages were stored on disk and correct the permissions. Don't recall off the top of my head where the held messages are stored on disk tho...