From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.86.87.8 with SMTP id k8cs28322fgb; Mon, 8 Mar 2010 03:27:41 -0800 (PST) Received: by 10.224.125.212 with SMTP id z20mr2329841qar.221.1268047660546; Mon, 08 Mar 2010 03:27:40 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 6si11119647qwk.42.2010.03.08.03.27.40; Mon, 08 Mar 2010 03:27:40 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 14DDF18582FD; Mon, 8 Mar 2010 06:27:40 -0500 (EST) Received: from m157.home.net.pl (m157.home.net.pl [62.129.253.157]) by rubyforge.org (Postfix) with SMTP id 920C71588077 for ; Mon, 8 Mar 2010 06:20:04 -0500 (EST) Received: from 217.98.91.13 (217.98.91.13) (HELO pk-laptop.localnet) by sigarden.home.pl (79.96.31.244) with SMTP (IdeaSmtpServer v0.70) id 633cb076bdfe1dc7; Mon, 8 Mar 2010 12:20:03 +0100 From: piotr.kempa@wp.eu To: sup-talk@rubyforge.org Date: Mon, 8 Mar 2010 12:20:02 +0100 User-Agent: KMail/1.13.1 (Linux/2.6.32-ck; KDE/4.4.1; x86_64; ; ) References: <201002261808.36354.kosmici-atakuja@wp.pl> <201003081129.47648.piotr.kempa@wp.eu> <1268044814-sup-4847@khjk.org> In-Reply-To: <1268044814-sup-4847@khjk.org> MIME-Version: 1.0 Message-Id: <201003081220.03154.piotr.kempa@wp.eu> Subject: Re: [sup-talk] PGP INLINE - can't make it work X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org 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 > sup-talk@rubyforge.org > 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 sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk