Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-ncis!helios.ee.lbl.gov!pasteur!ucbvax!SRI-NIC.ARPA!TCP-IP-RELAY From: TCP-IP-RELAY@SRI-NIC.ARPA Newsgroups: comp.protocols.tcp-ip Subject: (none) Message-ID: <8901152247.AA15559@ucbvax.Berkeley.EDU> Date: 15 Jan 89 22:47:30 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 32 HELO ADMIN.BYU.EDU TICK 4875 MAIL FROM: RCPT TO: DATA Received: by BYUADMIN (Mailer R2.01A) id 4875; Sun, 15 Jan 89 11:28:47 MST Date: Sat, 14 Jan 89 17:09:22 EST Reply-To: Sender: "(TCP-IP ARPA Discussions)" From: Nick Gimbrone Subject: Re: Re: VERY strange behavior at USENET/BITNET gateway To: "WCC Participate Redistribution (U Iowa)" In-Reply-To: Message of Mon, 09 Jan 89 08:39:30 AST from >> 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 >Perhaps some of you would take a hand in convincing IBM that an >empty line should exist. This is not an IBM problem. The IBM software has no problem treating the line of blanks as a "null line". In this case it sounds more like a UREP problem. UREP is the one who is trying to do cross protocol conversions, thus it is UREP's job to convert between "null lines" and "blank lines". Remember, if it came via UREP from an IBM system then it was talking BSMTP, not SMTP (and thus "null lines" are represented as "blank lines"). In the case of IBM's VM TCP/IP package the translation between these two forms occurs just fine (a true "null line" is send on SMTP when recieved on the BSMTP side, etc). . QUIT