cc:Mail Link to SMTP Undeliverable Message

penc000.administrator@smtp.cnet.navy.mil
Mon, 13 Apr 98 15:23:41 -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 15:23:28 -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 AA26929; Mon, 13 Apr 1998 15:15:44 -0500
Received: from ch4.viperlink.net by twister.emerald.iea.com (NTList 3.02.13) id xa257371; Mon, 13 Apr 1998 13:09:30 -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 PAA04641 for <ntisp@emerald.iea.com> Mon, 13 Apr 1998 15:54:52 -0400
Message-Id: <199804131954.PAA04641@ch4.viperlink.net>
X-Sender: ric@mail.viperlink.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0
Date: Mon, 13 Apr 1998 16:09:28 -0400
To: ntisp@emerald.iea.com
From: Ric Castagna <ric@viperlink.net>
Subject: Re: IIS 4.0 Newsfeeds
In-Reply-To: <000e01bd6706$db592880$fac7c3d0@tripoli.AISNETWORK>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Reply-To: ntisp@emerald.iea.com
X-Listmember: cnet.t221c@smtp.cnet.navy.mil [ntisp@emerald.iea.com]

Stupid Question of the Day for you, Matt: Why isn't the customer running a
news
server an pulling their own feed? Granted, it's still going to suck down=
your
bandwidth, but at least you wouldn't have to waste your time configuring=
your
software to accomodate their needs. Unless, of course, you're billing them=
for
your time.

When we set up a co-lo, the customer has to be running and administering it
all...that's the purpose of a co-lo. All you should have to give them is an
RJ-45 port, an IP address or two, bandwidth and a power outlet.

/ric

At 01:06 PM 4/13/98 -0500, you wrote:=20
>
> Hello,
> =A0
> Here is my question -- I have a customer who is switching ISP's from=
another
> provider to us. The are currently running newsgroups, and want to "import"
> their existing groups onto their co-located server here with us.
> =A0
> How do I set up the NNTP service in IIS 4.0 to "pull" from another feed?=
The
> other news server is configured to allow pulls, but I cannot figure out=
how
> to configure the "new" server to pull the feed down.
> =A0
> Any ideas?
> =A0
>
> ----------
> Matt Stratton, MCP
> Systems Integrator
> AIS Network
> A Microsoft Solution Provider
> <mailto:matts@aisnetwork.net>matts@aisnetwork.net
> <http://www.aisnetwork.net/>http://www.aisnetwork.net
> 847.882.0493 x124 (Vox)
> 847.882.0201 (Fax)
>
> ----------
> =A0

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

--simple boundary--