From: Daiki Ueno <ueno@unixuser.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 9862@debbugs.gnu.org, S=e9bastien Villemot <sebastien.villemot@ens.fr>
Subject: bug#9862: 23.3; [Gnus/EasyPG] Mixing PGP/MIME signature with RFC822 forwarded multipart message results in an invalid MIME message
Date: Wed, 26 Oct 2011 10:59:25 +0900 [thread overview]
Message-ID: <m3ty6wldhe.fsf-ueno@unixuser.org> (raw)
In-Reply-To: <m2obx557kw.fsf@igel.home> (Andreas Schwab's message of "Tue, 25 Oct 2011 19:01:19 +0200")
Andreas Schwab <schwab@linux-m68k.org> writes:
>> --====-=-=
>> Content-Disposition: inline
>> MIME-Version: 1.0
>> Content-Type: multipart/mixed; boundary="====-=-="
>>
>> Foo
>>
>> --====-=-=--
>
> This part is wrong. The boundary line "--====-=-=" needs to be moved
> after the rfc822 headers, like this:
Thanks for pointing out this. But then, I think the MML usage in the
original bug report was wrong. <#mml type=message/rfc822 ...> should
be followed by at least one rfc822 header lines such as "Subject:
foo\n", like this:
<#!secure method=pgpmime mode=sign>
<#mml type=message/rfc822 disposition=inline>
Subject: foo
<#multipart type=mixed>
<#part type=text/plain disposition=inline nofile=yes>
Foo
<#/multipart>
<#/mml>
Anyway, it seems the original bug has already been fixed in the latest
Gnus. Can we close this?
Regards,
--
Daiki Ueno
next prev parent reply other threads:[~2011-10-26 1:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 20:36 bug#9862: 23.3; [Gnus/EasyPG] Mixing PGP/MIME signature with RFC822 forwarded multipart message results in an invalid MIME message S=e9bastien Villemot
2011-10-24 22:07 ` bug#9862: Additional information Sébastien Villemot
2011-10-25 8:16 ` bug#9862: 23.3; [Gnus/EasyPG] Mixing PGP/MIME signature with RFC822 forwarded multipart message results in an invalid MIME message Daiki Ueno
2011-10-25 17:01 ` Andreas Schwab
2011-10-26 1:59 ` Daiki Ueno [this message]
2011-10-26 9:13 ` Sébastien Villemot
2011-10-26 10:09 ` Sébastien Villemot
2011-10-26 19:43 ` Andreas Schwab
2011-11-05 20:21 ` Sébastien Villemot
2011-11-07 6:15 ` Daiki Ueno
2011-10-25 9:49 ` bug#9862: Stéphane Adjemian
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3ty6wldhe.fsf-ueno@unixuser.org \
--to=ueno@unixuser.org \
--cc=9862@debbugs.gnu.org \
--cc=schwab@linux-m68k.org \
--cc=sebastien.villemot@ens.fr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).