Thanks for reading, and thanks for the feedback! HTML mail is certainly a problem - editing HTML in that way is not nearly as easily done (nor reversed) as pla

Thanks for reading, and thanks for the feedback! HTML mail is certainly a problem - editing HTML in that way is not nearly as easily done (nor reversed) as plain text. This is a loose end in the current proposal. Like many techies, I'm somewhat guilty of wishing HTML mail would just go away... However, in all fairness, HTML mail is not often used with PGP today and is somewhat of a "luxury" item, not a critical part of how people communicate. I did consider embedding a full message/rfc822 part instead, and that is also what Werner (the GnuPG author) prefers as well. If PGP/MIME had been implemented that way in the first place, and clients had evolved with that in mind, I'd probably just be happily using that. Unfortunately, the way message/rfc2822 attachments are handled by current mail clients, is not nearly streamlined enough that I'd be happy making people jump through those hoops for every single message. I'm trying to find a sweet spot of working well enough with existing PGP-aware clients, better with PGP-unaware clients, and addressing the limitations of PGP/MIME at the same time. It's a bit of a balancing act and so far the easy/elegant solutions don't seem to pass muster when used in the real world. But I'd love to be proven wrong about that.