unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: mdl@alum.mit.edu
Cc: emacs-devel@gnu.org
Subject: Re: Change in rmail-insert-mime-forwarded-message
Date: Wed, 23 Jan 2013 15:44:42 +0900	[thread overview]
Message-ID: <87mww04cv9.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <878v7k20xy.fsf@foil.strangled.net>

Mark Lillibridge writes:

 >     Yes, Rmail cannot prevent/fix damage that has already been incurred
 > due to broken mail distribution agents.  Hopefully, in the future we can
 > get those broken mail distribution agents fixed so they use mboxrd and
 > do not cause damage.

That's not good enough.  You also have to fix all of the ancient mbox
files that people have lying around.  Not going to happen.

 >     You would like Rmail to additionally damage the message again in the
 > hopes that the two damages cancel out?  You asked Rmail to send the
 > message:

No, I would like an MUA to ignore From-stuffing entirely (ie, treat
">" as just a character when it appears in the message body, no matter
what the context) when copying to and from mbox files.

It might be nice if the MUA would beautify the *display* of mail being
read (but not composed!) by suppressing one ">" when followed by
"From" in a context where it seems that there is an extra ">".  I've
got better things to do that try to write such code, though.

In composition, the user can "fix" it if they think those are the
appropriate semantics.  Why not let them?

 > Note that the ">" before the From is not part of the message per
 > the mbox format rules; sending it would be corrupting the message.

There is no standard for "mbox formatting rules", just a wide variety
of practices that are very similar but not identical.[1]  If the MDA does
From-stuffing, the ">" might be part of the format, or it might be
part of the message -- it depends on what came in over the wire, and
you don't have normally access to that.  If the MDA doesn't do From-
stuffing, it's part of the message.  Both are correct, according to
their own designs.  You don't have to like those designs, but the MDAs
are conforming to the specs they were written to.

"When faced with ambiguity, refuse to guess."

Why-yes-I'm-unambiguously-a-Tim-Peters-fan-ly y'rs,

Footnotes: 
[1]  http://www.jwz.org/doc/content-length.html.  Sadly enough,
nothing has much changed since then, except the proliferation of sites
that don't use the mbox format.  Nevertheless, there are still plenty
of sites that do, especially those based on free OSes where Emacs is
likely to be the platform of choice for at least some users.  And they
have some *very* old mbox files....



  reply	other threads:[~2013-01-23  6:44 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
2013-01-08 18:13           ` Stephen J. Turnbull
2013-01-23  0:32             ` Mark Lillibridge
2013-01-23  6:44               ` Stephen J. Turnbull [this message]
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=87mww04cv9.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --cc=emacs-devel@gnu.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).