Newsgroups: comp.archives
Path: utzoo!utgpu!news-server.csri.toronto.edu!math.lsa.umich.edu!math.lsa.umich.edu!emv
From: ned@hmcvax.claremont.edu (Ned Freed, Postmaster)
Subject: [vmsnet.mail.pmdf] RE: CMU TCP Channel not working...
Message-ID: <1990Aug25.043420.29441@math.lsa.umich.edu>
Followup-To: vmsnet.mail.pmdf
Sender: emv@math.lsa.umich.edu (Edward Vielmetti)
Reply-To: ned@hmcvax.claremont.edu (Ned Freed, Postmaster)
Organization: University of Michigan, Department of Mathematics
Date: Sat, 25 Aug 90 04:34:20 GMT
Approved: emv@math.lsa.umich.edu (Edward Vielmetti)
X-Original-Newsgroups: vmsnet.mail.pmdf
Lines: 22

Archive-name: pmdf-patches/25-Aug-90
Original-posting-by: ned@hmcvax.claremont.edu (Ned Freed, Postmaster)
Original-subject: RE: CMU TCP Channel not working...
Archive-site: ymir.claremont.edu [134.173.4.23]
Reposted-by: emv@math.lsa.umich.edu (Edward Vielmetti)

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