Gnus development mailing list
 help / color / mirror / Atom feed
From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: Mail without `From:' lines
Date: 05 May 1996 09:59:44 +0200	[thread overview]
Message-ID: <rjbuk3ble7.fsf@babbage.dina.kvl.dk> (raw)
In-Reply-To: "Sudish Joseph"'s message of 04 May 1996 20:10:46 -0400


>>>>> "SJ" == Sudish Joseph <sudish@VNET.IBM.COM> writes:

SJ> Just like it's Pine's intent to transform a random piece of junk into
SJ> a format that's suitable for following up to as a USENET message.  We
SJ> all know how that went, never mind that Pine's usage of Newsgroup
SJ> makes more sense in theory.

Pine wasn't dealing with random junk and it wasn't doing any
transformations, and it went against an established tradition for how
to use a particular header.  None of these are relevant for the issue
at hand, quite the contrary Gnus would be following an established
tradition, which mailers like VM has shown works well in practice.

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
worse than not converting it in hypothetical examples.

SJ> To put it simply:
SJ> Anything that can be achieved by munging together a From: header by
SJ> inspecting From_ can be done by inspecting From_ whenever you do not
SJ> see a From:.  If that doesn't please you, put the information in an
SJ> X-Bogosity: header.  Don't mess up a message that might later be
SJ> processed by an agent other than GNUS.

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.


  reply	other threads:[~1996-05-05  7:59 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 [this message]
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=rjbuk3ble7.fsf@babbage.dina.kvl.dk \
    --to=abraham@dina.kvl.dk \
    /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).