On Monday 08 March 2010 11:50:56 Sven Moritz Hallberg wrote: > > However, this still doesn't work because the header doesn't contain Content > > Type = application/pgp, it is text/plain, which is absolutely crazy and I have > > no idea what the enigmail developers are thinking... > > In fact I think this might be a design decision on the part of PGP, where the > original thinking went something like this: It should be possible to use it > with ANY mailer, even those that do not know about it. Thus the support for > "inline PGP", i.e. a PGP message embedded within the text of a regular email. > >From this standpoint it makes sense to keep the Content-Type as text/plain. > Imagine your recipient's MUA has no idea how to handle application/pgp. With > text/plain, she's still able to copy/paste into a separate PGP application. > > The merit of this design decision is debatable, but I think that's the way it > came to be. > > So, I'd say it's unlikely Enigmail is going to change the header. I'd also > guess that everyone else is doing it the same way. > > So, actually inspecting the body of the message is the way to go... > > HTH, > pesco > _______________________________________________ > sup-talk mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/sup-talk > > Thank you and Michael for the explanation. Now it all makes sense. I'll just keep watching the git repo in case a patch makes it there. Or this list. If anybody needs help testing such patch - I'm at your service. Coding it myself could be way over my head though...
Thank you, Piotr _______________________________________________ sup-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/sup-talk
