On 01/31/2013 04:31 PM, Ludwig Hügelschäfer wrote: > On 31.01.13 22:05, Daniel Kahn Gillmor wrote:
>> If a "prominent MUA" cannot deal with PGP/MIME, please name it
>> explicitly, so we can pressure its vendor or authors to fix it (or,
>> in the case of free software, so we can fix it ourselves).
>
> MS Outlook, at least out of the box.
Thanks, that's helpful! What happens when an MS Outlook user receives a
PGP/MIME-signed message? What do they see?
Is this true with all versions of MS Outlook? If not, how prominent are
the affected versions?
> Nice demonstration ;-) You caught me. Wanted to say that Thunderbird
> cannot display inline images from HTML messages when it converts them
> to plaintext for display.
Thanks for clarifying! You're helping me think through the problem
space here.
But I think that might still not be what's going on here. I don't think
that thunderbird does any conversion on its own; It's simply choosing
which part of a multipart/alternative message to display. If the sender
had made the message structure like this, i suspect thunderbird would
have displayed the images:
└┬╴multipart/alternative
├┬╴multipart/mixed
│├─╴text/plain
│├─╴image/png inline
│└─╴text/plain
└─╴text/html
(or maybe it would have reverted to the text/html part anyway, since the
other top-level alternative is now multipart/mixed instead of text/plain)
> I don't find it "bad". It's just "be caucious, you might spoil your
> setup when not used right". Unintended mouseclicks or keystrokes happen.
Yep, i agree with you entirely on this, and i think your warning here
"be cautious; you might break things here" is the right message to give
people.
Regards,
--dkg
signature.asc
Description: OpenPGP digital signature
_______________________________________________ enigmail-users mailing list [email protected] https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
