Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!wuarchive!kuhub.cc.ukans.edu!sloane
From: sloane@kuhub.cc.ukans.edu
Newsgroups: news.software.anu-news
Subject: Re: 822 header lines in MAIL messages
Message-ID: <19470.257f9a8a@kuhub.cc.ukans.edu>
Date: 8 Dec 89 17:27:06 GMT
References: <8912072204.AA07973@uunet.uu.net>
Organization: University of Kansas Academic Computing Services
Lines: 30

In article <8912072204.AA07973@uunet.uu.net>,
 Geoff Huston <munnari!csc.anu.oz.au!gih900@UUNET.UU.NET> writes:
> 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..

I hope you can handle something like:

Problem: I actually saw an article that was posted like this. I started out
         with something that looked like an RFC822 mail header, but was
         actually several thousand characters of text that were the body of
         the message.  An older version of news die horribly when processing
         this message because it thought the line was a (continued) header and
         tried to read it all in. The fix you put in news was to stop reading
         headers when you found a Newsgroups: header line. How will you handle
         something like this in mail?
-- 
USmail: Bob Sloane, University of Kansas Computer Center, Lawrence, KS, 66045
E-mail: sloane@kuhub.cc.ukans.edu, sloane@ukanvax.bitnet, AT&T: (913)864-0444