kamat@uceng.UC.EDU (Govind N. Kamat) (06/28/89)
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
karl@giza.cis.ohio-state.edu (Karl Kleinpaste) (06/28/89)
That's being done by Berkeley Mail. If you have source, see ucb/Mail/send.c. Gross. Pick another MUA.
dheller@cory.Berkeley.EDU (Dan Heller) (06/29/89)
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>
wisner@mica.Berkeley.EDU (Bill Wisner) (06/29/89)
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
stevens@boulder.Colorado.EDU (Curt Stevens) (07/04/89)
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 | ========
allbery@ncoast.ORG (Brandon S. Allbery) (07/04/89)
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
wisner@mica.Berkeley.EDU (Bill Wisner) (07/04/89)
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.