Path: utzoo!attcan!telly!problem!compus!lethe!torsqnt!news-server.csri.toronto.edu!rutgers!dimacs.rutgers.edu!mips!decwrl!pa.dec.com!decuac!hadron!klr
From: klr@hadron.COM (Kurt L. Reisler)
Newsgroups: comp.org.decus
Subject: Re: DECUS and E-Mail (Was Re: DECUS Board of Dire
Message-ID: <947@hadron.COM>
Date: 15 Mar 91 04:51:46 GMT
References: <4496@dftsrv.gsfc.nasa.gov> <009451A5.83C422A0@KING.ENG.UMD.EDU> <943@hadron.COM> <1991Mar13.075425.64@kahuna.asd-yf.wpafb.af.mil>
Reply-To: klr@hadron.UUCP (Kurt L. Reisler)
Distribution: na
Organization: Hadron, Inc., Fairfax, VA
Lines: 26

In article <1991Mar13.075425.64@kahuna.asd-yf.wpafb.af.mil> nieland_t@kahuna.asd-yf.wpafb.af.mil writes:
>In article <943@hadron.COM>, klr@hadron.COM (Kurt L. Reisler) writes:
>> 
>> 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".
>
>The Message on DCS in VAX NOTES from the DCS system Manager is putting the 
>connection date as in May.
>

That is the "official" connection.  I was told that a "backdoor" through
DECUServe might be available on 15 March.  However, there has been no
follow up, so I guess nothing happened.  I know I would rather be able
to read my DECUS leadership mail and respond to it from my Unix system,
than having to fight my way through VMS and ALL-IN-ONE (BLETCH!).



Kurt Reisler (703) 359-6100
============================================================================
UNISIG Chairman, DECUS US Chapter                       | Hadron, Inc.
..!{uunet|sundc|rlgvax|netxcom|decuac}!hadron!klr       | 9990 Lee Highway
Sysop, Fido 109/101 The Bear's Den   (703) 671-0598     | Fairfax, VA 22030