🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: comp.mail.headers
7 messages
7 total messages Started by Govind N. Kamat Wed, 28 Jun 1989 01:54
"Status" header
#43
Author: Govind N. Kamat
Date: Wed, 28 Jun 1989 01:54
10 lines
685 bytes
I keep noticing a header called "Status" in certain mail, with field
values like "R" and "OR".

What is this header supposed to represent?  It doesn't seem to be part
of RFC822.

-- 
Govind N. Kamat 			College of Engineering
kamat@uceng.UC.EDU			University of Cincinnati
					Cincinnati, OH 45221, USA
Re: "Status" header
#44
Author: Karl Kleinpaste
Date: Wed, 28 Jun 1989 13:52
2 lines
632 bytes
That's being done by Berkeley Mail.  If you have source, see
ucb/Mail/send.c.  Gross.  Pick another MUA.
Re: "Status" header
#45
Author: Dan Heller
Date: Thu, 29 Jun 1989 04:26
28 lines
1958 bytes
In reponse to someone's question about what the Status: header is for,
karl@giza.cis.ohio-state.edu (Karl Kleinpaste) writes:

> That's being done by Berkeley Mail.  If you have source, see
> ucb/Mail/send.c.  Gross.  Pick another MUA.

This header is modified by Mail (or sokme UA) to remember that the
message has been Read, Unread-but-old, or other information about
the message.

Karl feels that this is "gross".  I'd love to hear suggestions about
how to retain the "status" of a message without losing "state" and
not storing the information in the actual message.  The status header
is common among most Mail-based UA's (I don't know about MH).

The "state" I was referring to is the state of integrity that the
information about the message remains accurate even tho there may
be different users/processes accessing the same file.  The state
isn't completely conserved, but it is much more efficient than
using a separate state file.  I don't know how MH manages to remember
the status of messages if it doesn't store such information in the
message (file) itself.

I am guessing that Karl is using MH or something other than Mail, Elm
or Mush.  So, Karl, I ask how one would save the fact that a message
has been saved, printed, forwarded, read/unread, replied-to... Mush
uses the status: header to save all this information about each message.
Dan Heller	<island!argv@sun.com>
Re: "Status" header
#46
Author: Bill Wisner
Date: Thu, 29 Jun 1989 05:19
17 lines
1248 bytes
MH can be instructed to keep track of messages that have not been seen by
putting them into an "unseen" sequence. It never touches the actual messages
to do this.

MH can also be instructed to keep track of when a message is replied,
forwarded, or whatever. It does not use the utterly bogus and highly ugly
Status: header. It inserts two header lines at the very top of the message
(thus making them very easy to edit out) along the lines of:

Replied: Tue, 27 Jun 89 12:59:17 PDT
Replied: Martin Hanley <praxis!mph@uunet.UU.NET>

(Look, Martin! Your name in lights!)

Note that MH does none of these things unless explicitly told to.

w
Re: "Status" header
#56
Author: Curt Stevens
Date: Mon, 03 Jul 1989 22:13
21 lines
1497 bytes
In article <1322@uceng.UC.EDU> kamat@uceng.UC.EDU (Govind N. Kamat) writes:
>I keep noticing a header called "Status" in certain mail, with field
>values like "R" and "OR".
>
>What is this header supposed to represent?  It doesn't seem to be part
>of RFC822.

I assume that RFC822 describes the vanilla email header??? Could someone
please tell me where I can get this via anonymous ftp? Thanks a bunch...

===============================================================================
|Curt Stevens        (303)492-1218 |   /   |arpa: stevens@boulder.colorado.edu|
|University of Colorado at Boulder |  o o  |uucp:{ncar|nbires}!boulder!stevens|
|Computer Science Department       |   |   |----------------------------------|
|Campus Box 430                    |  \_/  |Its a dog eat dog world & Im wear-|
|Boulder, Colorado 80309           |       |ing milkbone underwear.Norm@Cheers|
===============================================================================

========
| Curt |
========
Re: "Status" header
#59
Author: Brandon S. Allbery
Date: Mon, 03 Jul 1989 22:35
32 lines
1971 bytes
As quoted from <15051@pasteur.Berkeley.EDU> by dheller@cory.Berkeley.EDU (Dan Heller):
+---------------
| In reponse to someone's question about what the Status: header is for,
| karl@giza.cis.ohio-state.edu (Karl Kleinpaste) writes:
| 
| > That's being done by Berkeley Mail.  If you have source, see
| > ucb/Mail/send.c.  Gross.  Pick another MUA.
| 
| This header is modified by Mail (or sokme UA) to remember that the
| message has been Read, Unread-but-old, or other information about
| the message.
| 
| Karl feels that this is "gross".  I'd love to hear suggestions about
| how to retain the "status" of a message without losing "state" and
| not storing the information in the actual message.  The status header
| is common among most Mail-based UA's (I don't know about MH).
+---------------

MH *does* use such headers.  However, the format is quite different:

	Replied: Sat, 01 Jul 89 10:43:08 -0400

However, you can give MH commands a flag (-noannotate) to turn this off.
Presumably, Karl does this (assuming that he uses MH); I, personally, prefer
to know about it.

++Brandon
-- 
Brandon S. Allbery, moderator of comp.sources.misc	     allbery@ncoast.org
uunet!hal.cwru.edu!ncoast!allbery		    ncoast!allbery@hal.cwru.edu
      Send comp.sources.misc submissions to comp-sources-misc@<backbone>
NCoast Public Access UN*X - (216) 781-6201, 300/1200/2400 baud, login: makeuser
Re: "Status" header
#58
Author: Bill Wisner
Date: Mon, 03 Jul 1989 22:47
6 lines
789 bytes
RFC822 describes the standard format for messages on the Internet. The
UNIX mail format is not quite RFC822, although it does make an effort
to conform.

Bill Wisner		wisner@mica.berkeley.edu	     ucbvax!mica!wisner
I'm not the NRA either.
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads