Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!wuarchive!kuhub.cc.ukans.edu!anu-news!list From: munnari!csc.anu.oz.au!gih900@UUNET.UU.NET (Geoff Huston) Newsgroups: news.software.anu-news Subject: Re: 822 header lines in MAIL messages Message-ID: <8912072204.AA07973@uunet.uu.net> Date: 8 Dec 89 13:50:33 GMT Sender: ANU-NEWS Discussion Reply-To: Geoff Huston Lines: 32 >>In article <13035.257507d4@ccavax.camb.com>, tinkelman@ccavax.camb.com writes: >> I've just started playing with OPEN/MAIL. (Thanks Geoff.) One of the things >> I had assumed it would do better than VMS mail was to understand RFC822 >> headers for all of the mail I receive over PMDF. Well, at least I wanted it >> to act like it does for news items, not showing the header lines unless I >> do a READ/HEADER. However it doesn't seem to distinguish these lines from >> the body text. Is there a way to make it do this? Do others agree that this >> would be desirable? > >This sounds like a good idea, but it might be a little hard to implement. >Consider a mail message where the first line of the actual body of the message >looks like a header line, for example "Problem:" or something like that. >Currently, NEWS stops processing headers when it finds a null line after a >Newsgroups: header. Since mail messages seldom have Newsgroups: header, how >do you decide where the headers end and the body of the message begins? The way the code works is exactly as you describe... when reading a mail message a flag is set to process two header blocks (i.e. read down to the SECOND line line (null or all blanks because of BITNET doing uncalled for padding!) When processing the expected second header block the scanning will stop if the first line of the second header block is not rfc822 header format. so.. is the body of the mail starts in col 1 with a line of the form: text: string then the second paragraph will be only be visible with READ/HEADER.. Geoff Huston