From: Eli Zaretskii <eliz@gnu.org>
To: mdl@alum.mit.edu
Cc: larsi@gnus.org, 13329@debbugs.gnu.org
Subject: bug#13329: 24.2 post patch for #9521; Rmail forward does not correctly handle MIME messages containing "From " lines
Date: Tue, 11 Oct 2022 08:20:56 +0300 [thread overview]
Message-ID: <83tu4bey13.fsf@gnu.org> (raw)
In-Reply-To: <87v8ore7tw.fsf@alum.mit.edu> (message from Mark Lillibridge on Mon, 10 Oct 2022 13:34:35 -0700)
> From: Mark Lillibridge <mdl@alum.mit.edu>
> Cc: larsi@gnus.org, 13329@debbugs.gnu.org
> Date: Mon, 10 Oct 2022 13:34:35 -0700
>
> > I just did, and I don't see the bug (in Emacs 28.2). The mbox file I
> > get does include a line that begins with ">From", but in the message
> > buffer presented by Rmail to me I see just "From", with the ">"
> > removed.
> >
> > I see the same in Emacs 28.1, so I'm unsure why you see the problem
> > there. Maybe the reproduction recipe above is too simple, and
> > something else is missing to reproduce the problem?
>
> Hmm. What mailer did you used to send the message? Maybe it wasn't
> sending a MIME message?
Rmail, with sendmail-user-agent as the sending MUA.
> We know that #13328 doesn't show the extra > for non-MIME messages.
That wasn't clear originally, but later I sent "From" in an
attachment, and didn't see any ">From" in the received email. I also
don't think there's a need to do anything with "From" in an
attachment, since attachments are encoded.
> I was using Emacs Rmail, but not the pure emacs 28.1 -q because I
> need to change settings to send email. Let me see if I can try a purer
> reenactment.
>
> Can you check the mbox I sent to see if you see extra >s for the
> last 2 messages there?
I see >From and >>From etc. in the attachments, but I don't understand
how the > part appeared there in the first place: attachments cannot
be possibly taken for the beginning of another email.
prev parent reply other threads:[~2022-10-11 5:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-01 22:24 bug#13329: 24.2 post patch for #9521; Rmail forward does not correctly handle MIME messages containing "From " lines Mark Lillibridge
2022-05-10 12:30 ` Lars Ingebrigtsen
2022-06-09 17:18 ` Lars Ingebrigtsen
2022-06-10 6:19 ` Eli Zaretskii
2022-06-10 9:24 ` Lars Ingebrigtsen
2022-06-10 11:00 ` Eli Zaretskii
2022-06-10 11:02 ` Lars Ingebrigtsen
2022-06-10 11:28 ` Eli Zaretskii
[not found] ` <83czd3l3nq.fsf@gnu.org>
2022-10-10 18:21 ` Mark Lillibridge
2022-10-10 18:25 ` Mark Lillibridge
2022-10-10 19:03 ` Eli Zaretskii
2022-10-10 19:47 ` Eli Zaretskii
2022-10-10 20:37 ` Mark Lillibridge
2022-10-11 5:24 ` Eli Zaretskii
2022-10-10 20:34 ` Mark Lillibridge
2022-10-10 21:04 ` Mark Lillibridge
2022-10-11 11:14 ` Eli Zaretskii
2023-09-03 8:33 ` Stefan Kangas
2024-01-10 11:03 ` Stefan Kangas
2022-10-11 5:20 ` Eli Zaretskii [this message]
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=83tu4bey13.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=13329@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mdl@alum.mit.edu \
/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.