-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 01/31/2013 01:05 PM, Daniel Kahn Gillmor wrote: | On Thu 2013-01-31 15:46:32 -0500, Ludwig Hügelschäfer wrote: | |> Some prominent MUAs are known to not be able to cope with |> PGP/MIME. | | 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).
This has been done numerous times, please check the archives. | I'm unaware of any prominent MUA in 2013 that cannot deal with PGP/MIME. It _may_ be true that the latest versions of all "prominent MUAs" handle PGP/MIME appropriately. But that doesn't help the massive installed base of older software that doesn't. I'll save you time on the next response, which is, "Well then those users should upgrade." That's a great theory, but people who want to be able to communicate with that massive installed base don't always have the ability to influence them to upgrade, and therefore must choose to use the method which works well for the people they communicate with. |> Well, that's normal. Plaintext mails just cannot have inline images. | | This is not the case: | | | | | MIME is compatible with inline images and text, as you can see from me | staring out at you creepily above. Plaintext != MIME. You're talking apples and oranges. Doug -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iQEcBAEBCAAGBQJRCt49AAoJEFzGhvEaGryETlwH/AsAk4N5W1RsKhWLdBv5syIz 2vIyV4dyjM24T2poWdI7UdQYq2ZuTpPt5mLuVMYRTrCruqyJktEQH9ihED4FW5qC najcgpO4OsWCJaFNbTSnFv/Rbs8IzHoZw0Nlqh/xGj0k2xyxIsjqI0EmK2Up8+RE xW5goZ9tJHV/2zvdbO8coYA6Fz5uf0kPkxP+vzj90T3uQmw6Axvk1buTWef5mHzu GbfBgVoRO1lDuXesYTG1nao2KNW5lXfQvNwsRxxq9Wlr6/J5AqPVS1D1x75mNRdx 4o+mgNRFl+Si2UDlXsb4zdtvlxHfbT4xEotz8FQTbkaxhatARrSqGxEPG/72OCw= =A7vr -----END PGP SIGNATURE----- _______________________________________________ enigmail-users mailing list [email protected] https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
