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: 04 May 1996 20:10:46 -0400	[thread overview]
Message-ID: <m2ybn8yo6x.fsf@galaxy.atlissc.ibm.com> (raw)
In-Reply-To: Per Abrahamsen's message of 04 May 1996 03:37:19 +0200

Per Abrahamsen <abraham@dina.kvl.dk> writes:
> RFC 822 is irrelevant since a message without a "From: " is not an RFC
> 822 message in the first place.

Hardly.  Not when your goal is to generate an 822 format message.  The
issue isn't what format the original crud is in, the issue is what
format it will be transformed into.

> The question is how to transform a piece of random junk in unix mbox
> format into something resembling an RFC 822 message.  Using the

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

> information in the `From ' message separator to generate a missing
> `From:' and `Date:' header has worked fine for me when converting old
> mbox.out files, and works fine for VM and many other mail agents.

Hitting "r" on such a message is going to cause problems for anything
other than personal mail (yes, that's 822 behaviour, but then your
stated goal is to transform to 822 format).

I have yet to see an MDA-generated UNIX From_ line contain anything
other than the envelope sender (+ctime date), I'd be grateful if you
showed me such an example.

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

-Sudish


  reply	other threads:[~1996-05-05  0:10 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 [this message]
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=m2ybn8yo6x.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).