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 13:33:42 -0400	[thread overview]
Message-ID: <m2ive9iu4p.fsf@galaxy.atlissc.ibm.com> (raw)
In-Reply-To: Per Abrahamsen's message of 06 May 1996 17:18:38 +0200

Per Abrahamsen <abraham@dina.kvl.dk> writes:
> How does it From: header looks?
>
> If it looks right, the example is irrelevant.

The example simply points out that your notion of "real world" is
incorrect.

> SJ> I'll detect the
> SJ> lack of a From: line when I try to reply to any such errant message,
>
> Have you ever received such a message?  I have been unable to generate
> one with sendmail or /bin/mail here.  As I noted in another message,
> sendmail insist on putting the envelope address in the From: line if
> there isn't one in the first place.

Precisely why I would prefer to have that one glaring exception be
handled manually, instead of having GNUS decide for me.

> SJ> At least make this an option that defaults to nil.
>
> Why should the default be something that is wrong in all examples you
> and me can think of?

Uh, why is it "wrong"?  Would you rather that the default was to set
up a situation where a user can reply to a mail only to have it be
delivered to some auto-scanner that sinks it unread?

We agree that the lack of "From:" is an extremely rare incident.  Then
why do you wish that the user forgo the pleasure of handling this
once-in-a-lifetime incident herself?  Besides, like you've shown by
your sendmail example, the message would have to arrive by a really
weird route to not have a From: line in the first place.  Given this,
the envelope sender information is unlikely to be pointing to the
originating host; definitely not an address that should be
auto-selected for replies.

-Sudish


  reply	other threads:[~1996-05-06 17:33 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
1996-05-06 15:18             ` Per Abrahamsen
1996-05-06 17:33               ` Sudish Joseph [this message]
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=m2ive9iu4p.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).