🚀 go-pugleaf

Apparently there are some CDC nodes on BITNET that are running old
CDC NJEF code.  The following is forwarded from an ARPA Internet
mailing list for the information of all CDC nodes on BITNET.

Bill Wells
NETINFO at UCBGARNE

----------------------------------------------------------------------------

>From ifip-gtwy-request@tis.llnl.gov Mon Sep 12 08:56:58 1988
Message-Id: <880912101213.000045DB.AASQ.01@CDCCentr> (UMass-Mailer 4.03)
Date:     Mon, 12 Sep 88  10:12:13 CDT
Sender: "IFIP 6.5 Gateway Group" <ifip-gtwy-request@tis.llnl.gov>
Return-Path: <ifip-gtwy-request@tis.llnl.gov>
>From: njfnhp%CDCCENTR.BITNET@cunyvm.cuny.edu (NJEF Support)
Subject:  CDC NJEF Character Translation Correction
To: ifip-gtwy@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 as reported by
Richard A. Jones (SBSWKAC@CSUGOLD.BITNET).

Control Data PSR number NJ20075 reports this problem against the NJEF
product.  Corrective code has been available since July, 1986.  This
corrective code was included in the NJEF product with the Level 664
release.  Any sites running NJEF prior to Level 664 should install the
corrective code available on SOLVER.

Dave Seidenstricker (njfnhp@cdccentr.bitnet)
NJEF Support
Control Data