Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!europa.asd.contel.com!wlbr!lonex.radc.af.mil!blackbird.afit.af.mil!kahuna.asd-yf.wpafb.af.mil!nieland_t
From: nieland_t@kahuna.asd-yf.wpafb.af.mil
Newsgroups: comp.org.decus
Subject: Re: DECUS and E-Mail (Was Re: DECUS Board of Dire
Message-ID: <1991Mar13.075425.64@kahuna.asd-yf.wpafb.af.mil>
Date: 13 Mar 91 12:54:25 GMT
References: <4496@dftsrv.gsfc.nasa.gov> <009451A5.83C422A0@KING.ENG.UMD.EDU>  <943@hadron.COM>
Distribution: na
Organization: USAF ASD/YF, WPAFB, Dayton, OH
Lines: 22

In article <943@hadron.COM>, klr@hadron.COM (Kurt L. Reisler) writes:
> In article <353.27d533c4@dragon.uucp> cts@dragon.uucp (Charles T. Smith, Jr.) writes:
> 
>>One of the biggest problems in dealing with Decus is finding the responsible
>>party.  For example, who is responsible for the policy of keeping DCS off the
>>net.  I for one would be happy to place a few phone calls.
> 
> At a DECUS meeting held this weekend, I was told that DCS "should have
> two-way Email access via the InterNet by March 15th".  The person who
> was responsible is no longer "with us", and the person who has taken
> over just found out what the blockage was, and is removing it.  Of
> course, 3/15 is a VMS-timeframe date (:-), which means "real soon now".
> 
> I will keep those who lurk in the aether informed.
> 

The Message on DCS in VAX NOTES from the DCS system Manager is putting the 
connection date as in May.

Ted Nieland				nieland_t@kahuna.asd-yf.wpafb.af.mil
Control Data Corporation		nieland@dayfac.cdc.com
(513) 427-6355				ted@nieland.dayton.oh.us