From: CRDGW2::CRDGW2::MRGATE::"SMTP::YMIR.CLAREMONT.EDU::POSTMAST" 24-AUG-1990 21:47:50.92 To: MRGATE::"ARISIA::EVERHART" CC: Subj: RE: CMU TCP Channel not working... Received: by crdgw1.ge.com (5.57/GE 1.70) id AA15930; Fri, 24 Aug 90 21:34:08 EDT Resent-From: postmast@YMIR.CLAREMONT.EDU Resent-Message-Id: <9008250134.AA15930@crdgw1.ge.com> Received: from HMCVAX.CLAREMONT.EDU by YMIR.CLAREMONT.EDU with PMDF-822; Fri, 24 Aug 1990 18:11 PDT Resent-Date: Fri, 24 Aug 1990 18:15 PDT Date: Fri, 24 Aug 1990 18:10 PDT From: "Ned Freed, Postmaster" Subject: RE: CMU TCP Channel not working... To: MCGUFFEY@MARSHALL.BITNET, INFO-PMDF@YMIR.CLAREMONT.EDU Errors-To: postmast@YMIR.CLAREMONT.EDU Message-Id: X-Vms-To: IN%"MCGUFFEY@MARSHALL.BITNET" X-Vms-Cc: IPMDF If the CMU TCP/IP slave program is saying "cannot find channel in table", this means that you do not have a ctcp_local channel in your configuration. You must have one for it to work right. No other channel name is acceptable; you can have additional ctcp_ channels but you have to have the ctcp_local channel in any case. I do not think this is related to any PMDF bugs. It sounds like a configuration problem, plain and simple. However, the bug fixes are available via anonymous FTP from ymir.claremont.edu in the directory [anonymous.mailserv.files.pmdf_patches]. They are also available from the mailserv system on ymir.claremont.edu. All the bug fixes are out there, but you cannot upgrade 3.0 into 3.1 with them; the changes were far too extensive to allow such an upgrade via patching. Ned