Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!pasteur!cory.Berkeley.EDU!dheller From: dheller@cory.Berkeley.EDU (Dan Heller) Newsgroups: comp.mail.headers Subject: Re: "Status" header Message-ID: <15051@pasteur.Berkeley.EDU> Date: 29 Jun 89 04:26:02 GMT References: <1322@uceng.UC.EDU> Sender: news@pasteur.Berkeley.EDU Reply-To: dheller@cory.Berkeley.EDU.UUCP (Dan Heller) Distribution: na Organization: University of California, Berkeley Lines: 28 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