Bugzilla

Kai, Maybe you can figure this out since I don't know the openpgp related code. While working on another bug (bug 847356) I'm still seeing what I describe in comment 0 above. An imap url occurs and requests a full body fetch of the message even when fetch parts on demand is enabled. When I first wrote up this bug, I noticed that disabling openpgp fixed the problem (see comment 4 above) but I could never find anything in your code that caused it. But now a couple years later I'm still seeing it.

The bug goes away with ESR 91 if I set pref ```mail.openpgp_enable``` to false. However, that pref is no longer in 102 and later version and not in daily. But in daily, in the file ```mail/base/content/msgMail3PaneWindow.js```, if I comment out the line ```initOpenPGPIfEnabled();``` it fixes the problem and full message fetch doesn't occur.

So maybe you have some idea where in the openpgp or related code that the full message fetch is being requested and, if so, is it really needed?

This may be related to the requirement that mime_parts_on_demand now defaults to false for encryption (see Bug 1629292). However, a user not using encryption should still be able to set this true and have parts/attachments fetched on demand and not always have the full message fetched.

Kai, Maybe you can figure this out since I don't know the openpgp related code. While working on another bug (bug 628646) I'm still seeing what I describe in comment 0 above. An imap url occurs and requests a full body fetch of the message even when fetch parts on demand is enabled. When I first wrote up this bug, I noticed that disabling openpgp fixed the problem (see comment 4 above) but I could never find anything in your code that caused it. But now a couple years later I'm still seeing it.

The bug goes away with ESR 91 if I set pref ```mail.openpgp_enable``` to false. However, that pref is no longer in 102 and later version and not in daily. But in daily, in the file ```mail/base/content/msgMail3PaneWindow.js```, if I comment out the line ```initOpenPGPIfEnabled();``` it fixes the problem and full message fetch doesn't occur.

So maybe you have some idea where in the openpgp or related code that the full message fetch is being requested and, if so, is it really needed?

This may be related to the requirement that mime_parts_on_demand now defaults to false for encryption (see Bug 1629292). However, a user not using encryption should still be able to set this true and have parts/attachments fetched on demand and not always have the full message fetched.