Gnus development mailing list
 help / color / mirror / Atom feed
From: "Sudish Joseph" <sudish@VNET.IBM.COM>
Cc: ding@ifi.uio.no
Subject: Re: Mail without `From:' lines
Date: 03 May 1996 18:58:25 -0400	[thread overview]
Message-ID: <m2oho5l5ym.fsf@galaxy.atlissc.ibm.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 03 May 1996 20:31:06 +0200

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.

This isn't a good idea, as you're effectively setting the reply
address for the message to the envelope sender--and that's only
allowed for bounces, I think (or it might not be, I don't have the
time to dig into 821/822 to check this :).  In fact, I'm pretty
certain that you're not supposed to reply to the conents of Sender:,
and that's a


4.4.4.  AUTOMATIC USE OF FROM / SENDER / REPLY-TO

    For systems which automatically  generate  address  lists  for
    replies to messages, the following recommendations are made:

        o   The "Sender" field mailbox should be sent  notices  of
            any  problems in transport or delivery of the original
            messages.  If there is no  "Sender"  field,  then  the
            "From" field mailbox should be used.

        o   The  "Sender"  field  mailbox  should  NEVER  be  used
            automatically, in a recipient's reply message.

        o   If the "Reply-To" field exists, then the reply  should
            go to the addresses indicated in that field and not to
            the address(es) indicated in the "From" field.



Kai's original idea is better as it only effects what gets displayed
in the summary, no (illegal in this instance?) munging of headers.

-Sudish


  reply	other threads:[~1996-05-03 22:58 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 [this message]
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
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=m2oho5l5ym.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).