cc:Mail Link to SMTP Undeliverable Message

penc000.administrator@smtp.cnet.navy.mil
Mon, 13 Apr 98 16:41:26 -0600

--simple boundary
Content-Type: text/plain; charset=US-ACSII
Content-Transfer-Encoding: 7bit

Message is undeliverable.
Reason: User "cnet.t221c@smtp.cnet.navy.mil" is not found in the cc:Mail Directory.
Original text follows:
---------------------

--simple boundary
Content-Type: text/plain; charset=US-ACSII
Content-Transfer-Encoding: 7bit

Received: from netpmsa.cnet.navy.mil by pens3646.cnet.navy.mil (ccMail Link to SMTP R8.00.01)
; Mon, 13 Apr 98 16:41:08 -0600
Return-Path: <null@emerald.iea.com>
Received: from twistersec.iea.com by netpmsa.cnet.navy.mil with SMTP
(1.38.193.4/16.2) id AA28812; Mon, 13 Apr 1998 16:33:26 -0500
Received: from ch4.viperlink.net by twister.emerald.iea.com (NTList 3.02.13) id aa257400; Mon, 13 Apr 1998 14:25:35 -0700
Received: from galactus.viperlink.net (galactus.viperlink.net [208.134.73.21])
by ch4.viperlink.net (2.5 Build 2639 (Berkeley 8.8.6)/8.8.4) with SMTP
id RAA00122 for <ntisp@emerald.iea.com> Mon, 13 Apr 1998 17:10:59 -0400
Message-Id: <199804132110.RAA00122@ch4.viperlink.net>
X-Sender: ric@mail.viperlink.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0
Date: Mon, 13 Apr 1998 17:25:33 -0400
To: ntisp@emerald.iea.com
From: Ric Castagna <ric@viperlink.net>
Subject: RE: IIS 4.0 Newsfeeds
In-Reply-To: <003101bd671e$360d4100$fac7c3d0@tripoli.AISNETWORK>
References: <199804131954.PAA04641@ch4.viperlink.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Reply-To: ntisp@emerald.iea.com
X-Listmember: cnet.t221c@smtp.cnet.navy.mil [ntisp@emerald.iea.com]

>Well, I guess you could call us a VAISP (Value Added ISP)
Service? Oh, you're supposed to provide service, too?

>The point is, this server only has customer info on it...we are just trying
>to figure out how suck down their old news groups from the old server and
>put them on the new one.
If they've been using Microsoft's News Server (part of MCIS), you might be
able to import and configure the "active.txt" file they should already
have. This would work, in theory, if you have all of the groups in your
current feed they used to have with their other provider.

My guess, though, is their old ISP or ISP's upstream wouldn't let the new
IP address (your class c's address) pull that feed that is current with
their existing groups.

/ric

----------------------------------------------------------
NTISP Mailing List listserver@emerald.iea.com

--simple boundary--