From: piotr.kempa@wp.eu
To: sup-talk@rubyforge.org
Subject: Re: [sup-talk] PGP INLINE - can't make it work
Date: Mon, 8 Mar 2010 12:20:02 +0100 [thread overview]
Message-ID: <201003081220.03154.piotr.kempa@wp.eu> (raw)
In-Reply-To: <1268044814-sup-4847@khjk.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
next prev parent reply other threads:[~2010-03-08 11:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 17:08 kosmici-atakuja
2010-02-26 17:43 ` Sven Schober
2010-03-02 10:49 ` piotr.kempa
2010-03-02 13:59 ` Michael Stapelberg
2010-03-02 14:19 ` piotr.kempa
2010-03-08 10:18 ` piotr.kempa
2010-03-08 10:29 ` piotr.kempa
2010-03-08 10:41 ` Michael Stapelberg
2010-03-08 10:50 ` Sven Moritz Hallberg
2010-03-08 11:20 ` piotr.kempa [this message]
2010-03-09 17:06 ` Michael Stapelberg
2010-03-10 10:53 ` Piotr Kempa
2010-03-10 11:14 ` Michael Stapelberg
2010-03-10 14:41 ` Piotr Kempa
2010-03-10 21:21 ` Michael Stapelberg
2010-03-02 14:12 ` Sam Hall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201003081220.03154.piotr.kempa@wp.eu \
--to=piotr.kempa@wp.eu \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox