Xref: utzoo news.misc:2513 comp.protocols.tcp-ip:5880 Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-lcc!ames!mailrus!ukma!david From: david@ms.uky.edu (David Herron -- One of the vertebrae) Newsgroups: news.misc,comp.protocols.tcp-ip Subject: Re: VERY strange behavior at USENET/BITNET gateway Keywords: bug BITNET USENET news Message-ID: <10836@s.ms.uky.edu> Date: 6 Jan 89 22:30:39 GMT References: <17978@glacier.STANFORD.EDU> Reply-To: david@ms.uky.edu (David Herron -- One of the vertebrae) Organization: U of Kentucky, Mathematical Sciences Lines: 17 I've seen things like this happen if the blank line(s) between the header and the body weren't truly blank but had spaces in it. Something which happens (at least with UREP) is that files coming in from BITNET-land have lines which are supposed to be truly empty instead contain some number of blanks. You would think this would be non-destructive, but the header parser in the news software gets confused and thinks that the first part of the body is actually part of the header. On a related note, sending out files with truly empty lines cause those "records" to disappear. -- <-- David Herron; an MMDF guy <-- ska: David le casse\*' {rutgers,uunet}!ukma!david, david@UKMA.BITNET <-- Now I know how Zonker felt when he graduated ... <-- Stop! Wait! I didn't mean to!