From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rms@gnu.org, 9766@debbugs.gnu.org
Subject: bug#9766: 24.0.50; rmail-forward makes attachment that doesn't read right
Date: Tue, 18 Oct 2011 12:28:32 +0200 [thread overview]
Message-ID: <m34nz67fvz.fsf@stories.gnus.org> (raw)
In-Reply-To: <83vcrnufjg.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 18 Oct 2011 05:47:31 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> We have Lars and we have Rainer. I wouldn't worry about that.
Actually, I'm not 100% sure that it was valid MIME.
The structure was basically
---------------------
Headers: Bla bla
--delimiter line
..
--end--
---------------------
Reading RFC2046, the CRLF preceding the delimiter line is part of the
delimiter line. But at the same time, the blank line after the headers
is the thing that delimits the headers from the body, which means that
the same blank line has two different overlapping meanings, which may
make some very strict parsers misbehave.
Adding an additional blank line before the delimiter line should fix
this and make this unambiguously valid MIME.
Unless I'm missing something in RFC2046.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2011-10-18 10:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-16 11:19 bug#9766: 24.0.50; rmail-forward makes attachment that doesn't read right Richard Stallman
2011-10-16 12:54 ` Eli Zaretskii
2011-10-16 21:40 ` Richard Stallman
2011-10-17 5:05 ` Eli Zaretskii
2011-10-17 13:14 ` Richard Stallman
2011-10-17 14:07 ` Eli Zaretskii
2011-10-17 21:42 ` Richard Stallman
2011-10-18 1:00 ` Stefan Monnier
2011-10-18 3:54 ` Eli Zaretskii
2011-10-18 13:01 ` Stefan Monnier
2011-10-18 13:26 ` Eli Zaretskii
2011-10-18 3:47 ` Eli Zaretskii
2011-10-18 10:28 ` Lars Magne Ingebrigtsen [this message]
2011-10-18 10:56 ` Richard Stallman
2011-10-18 3:53 ` Eli Zaretskii
2011-10-16 18:43 ` Lars Magne Ingebrigtsen
2022-04-24 13:53 ` Lars Ingebrigtsen
2022-05-22 20:00 ` Lars Ingebrigtsen
-- strict thread matches above, loose matches on Subject: below --
2011-09-16 7:51 bug#9521: 24.0.50; rmail-forward Kenichi Handa
2012-12-28 19:24 ` bug#9521: This bug is still present in version 24.2; it prevents forwarding correctly essentially any MINE message Mark Lillibridge
2012-12-28 20:46 ` bug#9521: PATCH for bug #9521, *not* bug #9766 Mark Lillibridge
2012-12-28 20:55 ` bug#9521: [RESEND] " Mark Lillibridge
2012-12-28 21:22 ` bug#9766: workaround for 9766 Mark Lillibridge
2012-12-29 8:53 ` bug#9521: [RESEND] PATCH for bug #9521, *not* bug #9766 Eli Zaretskii
2013-01-01 22:10 ` bug#9521: this bug (#10080) also causes an extra blank line to be appended to forwarded messages Mark Lillibridge
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=m34nz67fvz.fsf@stories.gnus.org \
--to=larsi@gnus.org \
--cc=9766@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rms@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.
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).