Bug 1678220 Comment 18 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

(In reply to Henry Wilkes [:henry] from comment #17)
> Does anyone want this uplifted to esr91? This seems more of a feature change than a defect from my perspective.

Wearing my enterprise hat, I would love to see your patch uplifted to ESR91. Being unable if incoming or outgoing messages have "real" attachments (as opposed to an OpenPGP key attached by default)  is a major annoyance. In practice, e.g. this will make any text-only message from mkmelin look as if it had a file attachment, quite confusing!

> Plus, the patch here depends on the patch for bug 583572, which was marked as wontfix for esr91.

I think uplifting your patch of bug 583572 will be equally beneficial (and with 2 files touched, hopefully not too hard), because not showing vcards in attachment list by default also looks like problematic behaviour given that the vcard might have multiple contacts, entire address books etc.

Thank you Henry for fixing these things! :-))
(In reply to Henry Wilkes [:henry] from comment #17)
> Does anyone want this uplifted to esr91? This seems more of a feature change than a defect from my perspective.

Wearing my enterprise hat, I would love to see your patch uplifted to ESR91. Being unable to tell if incoming or outgoing messages have "real" attachments (as opposed to an OpenPGP key attached by default)  is a major annoyance. In practice, e.g. this will make any text-only message from mkmelin look as if it had a file attachment, quite confusing!

> Plus, the patch here depends on the patch for bug 583572, which was marked as wontfix for esr91.

I think uplifting your patch of bug 583572 will be equally beneficial (and with 2 files touched, hopefully not too hard), because not showing vcards in attachment list by default also looks like problematic behaviour given that the vcard might have multiple contacts, entire address books etc.

Thank you Henry for fixing these things! :-))

Back to Bug 1678220 Comment 18