Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!cwjcc!hal!ncoast!allbery From: allbery@ncoast.ORG (Brandon S. Allbery) Newsgroups: comp.mail.headers Subject: Re: "Status" header Message-ID: <13784@ncoast.ORG> Date: 3 Jul 89 22:35:26 GMT References: <1322@uceng.UC.EDU> <15051@pasteur.Berkeley.EDU> Reply-To: allbery@ncoast.ORG (Brandon S. Allbery) Followup-To: comp.mail.headers Distribution: na Organization: Cleveland Public Access UN*X, Cleveland, Oh Lines: 32 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@ NCoast Public Access UN*X - (216) 781-6201, 300/1200/2400 baud, login: makeuser