From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.86.87.8 with SMTP id k8cs27258fgb; Mon, 8 Mar 2010 02:51:24 -0800 (PST) Received: by 10.224.17.214 with SMTP id t22mr2302117qaa.194.1268045479826; Mon, 08 Mar 2010 02:51:19 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 6si11777084qwk.12.2010.03.08.02.51.19; Mon, 08 Mar 2010 02:51:19 -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 45D3D1858302; Mon, 8 Mar 2010 05:51:19 -0500 (EST) Received: from atomzentrale.khjk.org (atomzentrale.khjk.org [212.12.50.211]) by rubyforge.org (Postfix) with ESMTP id 8589B18582DF for ; Mon, 8 Mar 2010 05:51:01 -0500 (EST) Received: from pesco by atomzentrale.khjk.org with local (Exim 4.63) (envelope-from ) id 1NoaY4-0001dY-8U for sup-talk@rubyforge.org; Mon, 08 Mar 2010 11:50:56 +0100 From: Sven Moritz Hallberg To: sup-talk In-reply-to: <201003081129.47648.piotr.kempa@wp.eu> References: <201002261808.36354.kosmici-atakuja@wp.pl> <201003021519.23488.piotr.kempa@wp.eu> <201003081118.55543.piotr.kempa@wp.eu> <201003081129.47648.piotr.kempa@wp.eu> Date: Mon, 08 Mar 2010 11:50:56 +0100 Message-Id: <1268044814-sup-4847@khjk.org> User-Agent: Sup/0.11 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: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org > 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