From: "Sudish Joseph" <sudish@VNET.IBM.COM>
Cc: ding@ifi.uio.no
Subject: Re: Mail without `From:' lines
Date: 03 May 1996 19:11:57 -0400 [thread overview]
Message-ID: <m2n33pl5c2.fsf@galaxy.atlissc.ibm.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 03 May 1996 20:31:06 +0200
[ Argh, I thought the Supercite keymap was hanging off C-c C-s, with
unfortunate results. Hmm, SC's keymap isn't to be found, a side
effect of the change of hook names in message.el? ]
Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
> Kai Grossjohann <grossjoh@ls6.informatik.uni-dortmund.de> writes:
> > WIBNI Gnus were to use the information from X-From-Line in lieu of the
> > missing `From ' line?
>
> This is on the Red Gnus todo list. Or rather, the mail backends will
> fudge a missing From: header from the "From " separator.
I wrote:
mishap> This isn't a good idea, as you're effectively setting the reply
mishap> address for the message to the envelope sender--and that's only
mishap> allowed for bounces, I think (or it might not be, I don't have the
mishap> time to dig into 821/822 to check this (*). In fact, I'm pretty
mishap> certain that you're not supposed to reply to the conents of Sender:,
mishap> and that's a
Anyways, the above paragraph was going to be changed to end on the
lines of: "you're not supposed to reply to the contents of Sender,
and Sender's a whole lot better for this purpose than the envelope
recipient (as mailing list expanders are required to rewrite
env. rec.); so I'd assume that replying _manually_ to env. recip. is
strictly taboo."
Here's 822 on replying to Sender.
822> 4.4.4. AUTOMATIC USE OF FROM / SENDER / REPLY-TO
822>
822> For systems which automatically generate address lists for
822> replies to messages, the following recommendations are made:
822>
822> o The "Sender" field mailbox should be sent notices of
822> any problems in transport or delivery of the original
822> messages. If there is no "Sender" field, then the
822> "From" field mailbox should be used.
822>
822> o The "Sender" field mailbox should NEVER be used
822> automatically, in a recipient's reply message.
Kai's original idea is better as it only effects what gets displayed
in the summary, no (illegal in this instance?) munging of headers.
Basically, this kind of thing gives me the shivers, since it could
well backfire in the manner that Pine's use of Newsgroup has. No, I
haven't thought it through, but it still gives me the creeps. :-)
-Sudish "
(*) And I should have stuck to that, instead of losing more time now,
greeping 822 and then rewriting this :-)
next prev parent reply other threads:[~1996-05-03 23:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-03 11:45 Kai Grossjohann
1996-05-03 18:31 ` Lars Magne Ingebrigtsen
1996-05-03 22:58 ` Sudish Joseph
1996-05-06 8:44 ` Kai Grossjohann
1996-05-06 11:12 ` Per Persson
1996-05-06 12:00 ` Per Abrahamsen
1996-05-06 12:12 ` Per Abrahamsen
1996-05-06 15:59 ` Per Persson
1996-05-06 16:01 ` Per Abrahamsen
1996-05-06 17:30 ` Per Persson
1996-05-06 17:45 ` Per Abrahamsen
1996-05-06 20:12 ` Per Persson
1996-05-07 5:38 ` Per Abrahamsen
1996-05-06 17:46 ` Stainless Steel Rat
1996-05-06 16:42 ` Stainless Steel Rat
1996-05-03 23:11 ` Sudish Joseph [this message]
1996-05-04 0:39 ` Sudish Joseph
1996-05-04 1:37 ` Per Abrahamsen
1996-05-05 0:10 ` Sudish Joseph
1996-05-05 7:59 ` Per Abrahamsen
1996-05-06 14:53 ` Sudish Joseph
1996-05-06 15:18 ` Per Abrahamsen
1996-05-06 17:33 ` Sudish Joseph
1996-05-06 17:53 ` Per Abrahamsen
1996-05-05 12:33 ` Per Abrahamsen
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=m2n33pl5c2.fsf@galaxy.atlissc.ibm.com \
--to=sudish@vnet.ibm.com \
--cc=ding@ifi.uio.no \
/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).