From: "Georg C. F. Greve" <greve@gnu.org>
Subject: Buggy boundary type in forwarded mail
Date: Wed, 10 Oct 2001 18:13:56 +0200 [thread overview]
Message-ID: <m37ku3h3qz.fsf@reason.gnu-hamburg> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 255 bytes --]
Hi all,
a friend of mine and I semm to have discovered a bug in the gnus
boundary types when forwarding mails with attachment.
I'll try to explain what happens.
The header of the mail defines <Boundary A> as boundary and the body
looks like:
[-- Attachment #1.2: Type: text/plain, Size: 401 bytes --]
--<Boundary A>
Content-Type definition; Boundary B definition
--<Boundary B>
Forwarding blabla... text... whatever
--<Boundary B>
forwarded mail; header defines <Boundary A2>
--<Boundary A2>
Text of forwarded mail
--<Boundary A2>
Attachment of forwarded mail
--<Boundary A2>--
<Boundary B>
End of my blabla
--<Boundary B>--
--<Boundary A>
GPG Signature
--<Boundary A>--
[-- Attachment #1.3: Type: text/plain, Size: 456 bytes --]
Unfortunately, A2 = A, although they *should* be different, I believe.
So this looks like the MIME signing part doesn't check properly
whether its boundary type is already used within the mail somewhere.
Regards,
Georg
--
Georg C. F. Greve <greve@gnu.org>
Free Software Foundation Europe (http://fsfeurope.org)
Brave GNU World (http://brave-gnu-world.org)
[-- Attachment #2: Type: application/pgp-signature, Size: 268 bytes --]
next reply other threads:[~2001-10-10 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 16:13 Georg C. F. Greve [this message]
2001-12-30 0:39 ` 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=m37ku3h3qz.fsf@reason.gnu-hamburg \
--to=greve@gnu.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).