From: nicolas.pouillard@gmail.com (Nicolas Pouillard)
Subject: [sup-talk] gpg signing issue
Date: Wed, 27 Feb 2008 09:39:38 +0100 [thread overview]
Message-ID: <1204101423-sup-3529@ausone.inria.fr> (raw)
In-Reply-To: <1204081553-sup-4470@aconcagua>
Excerpts from Jan Spakula's message of Wed Feb 27 04:40:54 +0100 2008:
> Hello,
>
> I have an issue with gpg signing emails with sup. The header of sent
> emails look like this:
> Content-Type: multipart/signed; protocol=""application/pgp-signature""; boundary="=-1204074034-949437-9467-7738-1-="; micalg="pgp-sha1"
> Note the double quotation marks around
> application/pgp-signature. (I checked it in the "Sent", and of course on
> my other e-mail account.) Apparently they throw off at least mutt and
> claws-mail, so that they don't recognize the protocol for the
> attachment. However, if I manually edit the header to have only one set
> of quotation marks, the signature is recognized.
>
> I took a peek on the sources (crypto.rb), and I don't know how the
> double quotation marks could be created. Anybody else having this
> problem?
That's a ruby-mail bug with a working patch [1], however ruby-mail is no
longer actively maintained :(
[1]: "[2661] set_boundary doubles quotes in params which already contained a quote"
http://rubyforge.org/tracker/index.php?func=detail&aid=2661&group_id=446&atid=1756
--
Nicolas Pouillard aka Ertai
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20080227/94488b5f/attachment.bin
next prev parent reply other threads:[~2008-02-27 8:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 3:40 Jan Spakula
2008-02-27 8:39 ` Nicolas Pouillard [this message]
2008-02-27 17:50 ` William Morgan
2008-02-27 18:56 ` Jan Spakula
2008-02-28 17:09 ` William Morgan
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=1204101423-sup-3529@ausone.inria.fr \
--to=nicolas.pouillard@gmail.com \
/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