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: 06 May 1996 10:53:15 -0400	[thread overview]
Message-ID: <m2k9ypj1k4.fsf@galaxy.atlissc.ibm.com> (raw)
In-Reply-To: Per Abrahamsen's message of 05 May 1996 09:59:44 +0200

Per Abrahamsen <abraham@dina.kvl.dk> writes:
> It seems to me that converting the 'From ' line in the absence of a
> `From:' header will be the right thing in all real examples, and no

Here's a real example: *Every* message I receive from the internet has
envelope sender set to a fixed address of this form:
<@smtp.relay,relay.id@vm.node.that.doesn't.speak.tcp.ip>
(also a nice real world example of a valid use of source routes)

> worse than not converting it in hypothetical examples.

Not necessarily.  Using the envelope sender makes sense for local mail
and mail sent to directly connected hosts.  True, this accounts for
the vast majority of mail messages (and ~ 10% of my mail).

Then again, the percentages of messages w/o From: lines is vanishingly
small.  I'd prefer that GNUS did not tear, damage or spindle the
headers (other than X-blah) of any message I receive.  I'll detect the
lack of a From: line when I try to reply to any such errant message,
and I'll be able to make a far better estimate of the actual return
address than GNUS.

Unless, of course, someone wants to write that cool routine to parse
Received: headers to see where the mail originated, and then figure
out how to reply to it.  This is far more likely to be correct than
using envelope sender.

> The `From ' line is an artifact of the mbox format, so leaving it
> alone is not an option with other backends.  Converting is to an `X-'
> header will break if the message is later read by another mail agent
> (like VM), who will then not be able to access the information.  The
> only way to preserve the information is to convert the broken message
> into standard (RFC 822) format.

GNUS current X-From-Line preserves that information.  Putting it in
From: destroys information (namely, the far more important information
that the original message did not have a From: line).  I do not want
to reply to From_ blindly.  I'd prefer that my MUA choked and died on
such messages.

Oh, yes. Please note that replies send to envelope sender can
disappear w/o any fuss.  You won't even have the benefit of a bounce
to know that you must resend.

At least make this an option that defaults to nil.
-Sudish


  reply	other threads:[~1996-05-06 14:53 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
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 [this message]
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=m2k9ypj1k4.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).