From: David Engster <deng@randomsample.de>
To: ding@gnus.org
Subject: Parsing Content-Type with repeated attributes
Date: Mon, 11 Oct 2010 14:11:17 +0200 [thread overview]
Message-ID: <m21v7xexp6.fsf@randomsample.de> (raw)
I just got a mail with the following Content-Type:
Content-Type: application/x-pkcs7-mime;smime-type=signed-data;name=smime.p7m; smime-type=signed-data; name="smime.p7m"
This belongs to a base64 encoded mail with S/MIME signing. Now, this
Content-Type was obviously produced by some strange mail software
(*cough* X-MimeOLE: Produced By Microsoft Exchange V6.5 *cough*), but
when you run that Content-Type through `rfc2231-parse-qp-string', it
produces
("content-type:application/x-pkcs7-mime"
(name . "smime.p7msmime.p7m")
(smime-type . "signed-datasigned-data"))
I first thought this was a bug, but it seems the above rfc2231 function
concats those strings very deliberately... Gnus also actually tries to
verify the mail, but with the old mm-view-pkcs7-verify and I'm using EPG
with gpgsm.
-David
next reply other threads:[~2010-10-11 12:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 12:11 David Engster [this message]
2010-10-11 18:21 ` Lars Magne Ingebrigtsen
2010-10-12 18:51 ` David Engster
2010-10-12 21:33 ` Lars Magne Ingebrigtsen
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=m21v7xexp6.fsf@randomsample.de \
--to=deng@randomsample.de \
--cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).