From: Mark Lillibridge <mdl@alum.mit.edu>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: emacs-devel@gnu.org
Subject: Re: Change in rmail-insert-mime-forwarded-message
Date: Tue, 08 Jan 2013 08:32:15 -0800 [thread overview]
Message-ID: <87a9sjtz3k.fsf@foil.strangled.net> (raw)
In-Reply-To: <87vcb89em4.fsf@uwakimon.sk.tsukuba.ac.jp> (stephen@xemacs.org)
"Stephen J. Turnbull" <stephen@xemacs.org> writes:
> Mark Lillibridge writes:
>
> > Messages stored in mbox format have lines starting with >*From\
> > escaped by adding an extra > at the front. This escaping needs to be
> > reversed to get the original message back. See bug #13329 for more
> > details.
>
> It's not particularly relevant to the problem Richard is reporting,
> but that's incorrect. mbox formats vary, but the most common ones
> stuff a ">" if and only if the string "From " occurs at the beginning
> of a line. If ">From" occurs at the beginning of a line, you can't
> know whether it was stuffed by the MDA or by the message author or
> what.
Yes, mbox formats vary; I was describing mboxrd above, which I
believe is the current Rmail default and does not suffer from this
problem. See bug #6574 for why mboxo, which you describe above,
corrupts messages with ">From " lines. Either way, unescaping is
required for forwarding or resending messages (destination system may
not use mbox at all).
> The only portable way I know to handle this involves hiding the
> message text from MDAs by encoding "From" or ">From" as quoted-
> printable.
Agreed. Base64 also works. I don't think either of the message
sending libraries in Emacs does this, however.
- Mark
next prev parent reply other threads:[~2013-01-08 16:32 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 2:18 Change in rmail-insert-mime-forwarded-message Richard Stallman
2013-01-07 3:44 ` Eli Zaretskii
2013-01-08 2:11 ` Richard Stallman
2013-01-09 17:15 ` Eli Zaretskii
2013-01-10 6:19 ` Richard Stallman
2013-01-10 19:03 ` Eli Zaretskii
2013-01-07 4:43 ` Mark Lillibridge
2013-01-08 2:11 ` Richard Stallman
2013-01-08 3:57 ` Mark Lillibridge
2013-01-08 10:02 ` Stephen J. Turnbull
2013-01-08 16:32 ` Mark Lillibridge [this message]
2013-01-08 18:13 ` Stephen J. Turnbull
2013-01-23 0:32 ` Mark Lillibridge
2013-01-23 6:44 ` Stephen J. Turnbull
2013-01-09 16:43 ` Richard Stallman
2013-01-10 16:53 ` Mark Lillibridge
2013-01-11 4:43 ` Richard Stallman
2013-01-11 8:10 ` Eli Zaretskii
2013-01-11 16:48 ` Mark Lillibridge
2013-01-13 22:43 ` Richard Stallman
2013-01-14 22:43 ` Richard Stallman
2013-01-15 2:13 ` Glenn Morris
2013-01-15 4:01 ` Eli Zaretskii
2013-01-15 5:27 ` Richard Stallman
2013-01-15 16:07 ` Eli Zaretskii
2013-01-16 0:04 ` Richard Stallman
2013-01-23 0:40 ` Mark Lillibridge
2013-01-15 17:29 ` Glenn Morris
2013-01-16 0:04 ` Richard Stallman
2013-01-16 1:14 ` Glenn Morris
2013-01-17 6:26 ` Mark Lillibridge
2013-01-17 21:04 ` Richard Stallman
2013-04-01 19:06 ` 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=87a9sjtz3k.fsf@foil.strangled.net \
--to=mdl@alum.mit.edu \
--cc=emacs-devel@gnu.org \
--cc=stephen@xemacs.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).