From: Daiki Ueno <dueno@redhat.com>
To: 9862-done@debbugs.gnu.org
Cc: "Sébastien 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: Mon, 07 Nov 2011 15:15:08 +0900 [thread overview]
Message-ID: <m3fwi0ihlf.fsf-dueno@redhat.com> (raw)
In-Reply-To: <87ehy0rrmf.fsf@karaba.cepremap.org> ("Sébastien Villemot"'s message of "Wed, 26 Oct 2011 12:09:44 +0200")
Sébastien Villemot <sebastien.villemot@ens.fr> writes:
> Using git I get exactly the same output than Daiki Ueno: the boundary
> problem has gone, and another problem has appeared.
>
> So I guess that if you close this bug, then another needs to be opened
> for the new problem.
As I said in <m3ty6wldhe.fsf-ueno@unixuser.org>, I think the other
problem is misuse of the MML language, not a bug. Though it would be
nice to warn if there is no RFC822 header lines following <#mml
type=message/rfc822...>. If you care about this, feel free to open a
new bug.
Closing.
Regards,
--
Daiki Ueno
next prev parent reply other threads:[~2011-11-07 6:15 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3fwi0ihlf.fsf-dueno@redhat.com \
--to=dueno@redhat.com \
--cc=9862-done@debbugs.gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.