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:24:06 +0300 [thread overview]
Message-ID: <83sfjvexvt.fsf@gnu.org> (raw)
In-Reply-To: <87sfjve7ps.fsf@alum.mit.edu> (message from Mark Lillibridge on Mon, 10 Oct 2022 13:37:03 -0700)
> From: Mark Lillibridge <mdl@alum.mit.edu>
> Cc: larsi@gnus.org, 13329@debbugs.gnu.org
> Date: Mon, 10 Oct 2022 13:37:03 -0700
>
> > And now I've also sent to myself a message with a MIME attachment,
> > where the attachment was a text that included a line that began with a
> > "From". In the message I received, if I tell Rmail to show the
> > attachment, I see that line without any leading ">" before "From". So
> > again, I'm unable to reproduce the problem you are describing.
>
> How did your mailer encode the attachment? If it used base64, then
> I don't expect you'll see the bug.
It was base64, but that's the default used by Rmail, because I didn''t
change anything, just used the mail-add-attachment command, and the
file I attached was plain-ASCII file.
> > Are you sure you are using rmail.el which came with Emacs 28?
>
> For the test with the existing mbox, yes. I downloaded and built
> from source Emacs 28.1 and invoked it with -q, which should mean it
> looks at none of my elisp.
Then I have no idea what is going on, but from my testing the problem
doesn't exist. Perhaps your configuration of email happens to trigger
some rare situation, but I'd need a clear recipe starting from "emacs -Q"
to reproduce it. Or maybe your MTA has something to do with that?
next prev parent reply other threads:[~2022-10-11 5:24 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 [this message]
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
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=83sfjvexvt.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 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).