Path: utzoo!utgpu!water!watmath!clyde!att!rutgers!ucsd!ames!lll-tis!GARNET.BERKELEY.EDU!netinfo
From: netinfo@GARNET.BERKELEY.EDU (Postmaster & BITINFO)
Newsgroups: comp.protocols.iso.x400.gateway
Subject: Re:  forbidden characters in body of message
Message-ID: <8809090353.AA23660@garnet.berkeley.edu>
Date: 9 Sep 88 03:53:08 GMT
Sender: root@tis.llnl.gov
Distribution: inet
Organization: The Internet
Lines: 63
Approved: post-x400-gateway@tis.llnl.gov

In reply to:

	Return-Path: <ifip-gtwy-request@tis.llnl.gov>
	From: Hans-Georg Kerkhoff BESSY-Berlin phone +49 (30)82004-153
		<kerkhoff%exp.bessy.dbp.de@relay.cs.net>
	To: ifip-gtwy@tis.llnl.gov
	Cc: reichenbach%exp.bessy.dbp.de@relay.cs.net
	Message-Id: <897:kerkhoff@exp.bessy.dbp.de>
	Subject: forbidden characters in body of message
	
	Excuse me if this is a silly question.
	
	When a message from BITnet is received by DFN-EAN-V2 (German
	X.400 approach) a (|) in the body of a message is replaced by
	an (!). ...

The problem is most likely a CDC node on the BITNET/EARN. See message
from SBSWKAC@CSUGOLD.BITNET below.

Bill Wells

------------------------------------------------------------------------
| William Wells      Telephone: COML: +1 415-642-9801, ATSS: 582-9801  |
| Data Communication & Network Services  postmaster@jade.berkeley.edu  |
| University of California at Berkeley   netinfo@garnet.berkeley.edu   |
| 269 Evans Hall         NETINFO at UCBGARNE (BITNET NJE/RSCS PUN/PRT) |
| Berkeley, CA 94720    NETINFO%GARNET.BERKELEY.EDU@EARN-RELAY (Janet) |
------------------------------------------------------------------------


From: SBSWKAC@CSUGOLD.BITNET
Message-Id: <8512231635.AA14839@ucbjade.Berkeley.Edu>
To: bitinfo@ucbjade
Date: Mon Dec 23 08:34:46 1985
Subject: SEND OUTPUT

To: Bill Wells BITINFO @ UCBJADE
From: Richard A. Jones
      University of Colorado at Boulder
      SBSWKAC @ CSUGOLD

     Thanks for the copy of the reply to Mark Walker at Wyoming
I will tell him what I am telling you:

     The CDC NJEF product has the following translations (which I
consider to be wrong):

     Outgoing, an exclamation point is mapped into an EBCDID 4F, a
vertical bar.  A vertical bar is mapped into a FA (long thin vertical
bar), and is lost at most ASCII sites.

     Incoming, an EBCDIC 4F (vertical bar) is mapped into an exclamation,
a 5A (exclamation point) and BD (right bracket) are both mapped into
a right bracket.

     Thus, there is no way to get an exclamation point into BITNET from
the Cyber.

     I have reported all this to the CDC fellow at CSU who handles NJEF,
and he "is looking into it."

     Thanks for your help in assisting me collecting enough information to
pin down what was happeding and where--and pin it on CDC.