From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: mdl@alum.mit.edu, 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: Fri, 10 Jun 2022 14:00:36 +0300 [thread overview]
Message-ID: <83tu8szstn.fsf@gnu.org> (raw)
In-Reply-To: <87r4m4tucm.fsf@foil.strangled.net>
[-- Attachment #1: Type: text/plain, Size: 139 bytes --]
Here is your message, forwarded as MIME by Rmail (I just edited the
Subject, to avoid creating a new bug report). Did you receive it
OK?
[-- Attachment #2: Type: message/rfc822, Size: 799 bytes --]
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: mdl@alum.mit.edu, 13329@debbugs.gnu.org
Subject: Re: bug#13329: 24.2 post patch for #9521; Rmail forward does not correctly handle MIME messages containing "From " lines
Date: Fri, 10 Jun 2022 11:24:27 +0200
Eli Zaretskii <eliz@gnu.org> writes:
> At this point I can only say that I'm forwarding email with MIME
> attachments quite a lot, and didn't spot any problems, although I
> admit there's not a lot of ">>...>From" in them.
Here's a message with a From line:
>From thing lala yes
If you can forward this as MIME in rmail, then I think the bug has been
fixed?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-06-10 11:00 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 [this message]
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
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=83tu8szstn.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).