It's possible, that gmail changed something to non-standard, yet, supported by most mainstream mail clients. So called "corporate spoiling" of standards, i.e. enforcing adapting to your shitte, just because you're popular. I'm not sure if it's the case here, but it is very suspicious, that problems started to appear in sync with google adding a new "feature" (no matter if you want it or not).

OTOH, it is possible, that modest "gmail" automatic configuration was already "spoiled" by bending to some non-standards things, that were changed, lately. In this case, not only setting gmail to work via pop3 (we already confirmed it's working), but also *manually* (avoiding automatic setup for gmail!) adding imap account for gmail, typing ports by the hand etc, should help. I haven't tried it yet, it's just a theory.

BTW, I got hit by that bug, too. Strangely, in my case, it happened with old mail that was already opened in the past - one with attachement. Other old mails, without attachements, are working fine (for nowj.

It would reinforce point about fault geing on gmail's side, due to some changes they introduce. (or, modest *was* bugged after all, but gmail change just triggered that bug). In any case, google sux

/Estel