From: "Edward J. Sabol" <sabol@alderaan.gsfc.nasa.gov>
Subject: Re: resending & empty subjects
Date: Fri, 13 Nov 1998 16:26:14 -0500 [thread overview]
Message-ID: <199811132126.QAA19055@alderaan.gsfc.nasa.gov> (raw)
In-Reply-To: <m3ww4zphxg.fsf@sparky.gnus.org> (message from Lars Magne Ingebrigtsen on 13 Nov 1998 19:27:07 +0100)
Excerpts from mail: (13-Nov-98) Re: resending & empty subjects by Lars Magne Ingebrigtsen
>> X-From-Line too,
> I think that one should stay to preserve the chain of events.
It's no big deal, but I think that might be in bad form. I would prefer it if
"X-From-Line:" were removed. To quote RFC822:
Some systems permit mail recipients to forward a message,
retaining the original headers, by adding some new fields. This
standard supports such a service, through the "Resent-" prefix to
field names.
[...]
Note: In general, the "Resent-" fields should be treated as con-
taining a set of information that is independent of the
set of original fields. Information for one set should
not automatically be taken from the other.
My interpretation of these passages is that the MUA should not alter the
original headers in any fashion when resending and that it should only add a
set of standard fields all of which start with the "Resent-" prefix. The
"X-From-Line:" should only be in the resent e-mail if it was in the original
e-mail as well. If Gnus is adding "X-From-Line:" as part of some internal
meta-information tracking mechanism, then it should remove it before
resending. IMHO, of course.
next prev parent reply other threads:[~1998-11-13 21:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-10 18:33 Vladimir Volovich
1998-11-13 18:27 ` Lars Magne Ingebrigtsen
1998-11-13 20:22 ` Vladimir Volovich
1998-11-13 21:31 ` Lars Magne Ingebrigtsen
1998-11-13 21:26 ` Edward J. Sabol [this message]
1998-11-13 22:06 ` Lars Magne Ingebrigtsen
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=199811132126.QAA19055@alderaan.gsfc.nasa.gov \
--to=sabol@alderaan.gsfc.nasa.gov \
/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.
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 NNTP newsgroup(s).