Date: Thu, 17 Apr 2014 03:28:59 -0400
From: MICHAEL PURDY
To: GREG YOUNGBLOOD
Subject: RE: qwk  DOVE-NET
Newsgroups: win.server.program
Message-ID: 
References:  
X-WcMsg-Attr: Rcvd
X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
Lines: 63

Greg

You should not have any difficulty scripting using virtually any telnet
scripting language.

If you are connecting to a Wildcat! QWK Network using FTPS make sure they
have updated their Wildcat! install to account for the Heartbleed OpenSSL Bug.

Mike


On 4/16/2014 12:25 PM, GREG YOUNGBLOOD wrote to MICHAEL PURDY:

-> Hello Mike
-> 
-> I'll look into it, thanks for the info!
-> 
-> Greg
-> 
-> 
-> 
-> On 4/14/2014 8:37 PM, MICHAEL PURDY wrote to GREG YOUNGBLOOD:
-> 
-> -> If you just want to be a Node connecting to a particular Wildcat! host 
-> to
-> -> Upload REP and Download QWK Packets then you can use Telnet scripting 
-> which
-> -> is made easier if you use the Wildcat! fast login option [!] and 
-> enhanced
-> -> scripting prompts.
-> -> 
-> -> The problem is that Telnet scripting works on the basis of
-> -> 
-> ->   Read Data
-> ->     Write Data
-> ->   Read Data
-> ->     Write Data
-> ->   ...
-> ->  
-> -> So if a Wildcat host has modified their screens/prompts you need to 
-> match
-> -> your script to work with the site specific customization.
-> -> 
-> -> In the real world the Read Write Data equates to scripting in the form 
-> of:
-> -> 
-> ->   expect [wait x]
-> ->     output
-> ->     
-> -> Within established private Wildcat! QWK Networks FTP is used to overcome
-> -> the Telnet scripting limitations.
-> -> 
-> -> You can use any Telnet scripting language you want.  Netterm is probably
-> -> the most popular.
-> -> 
-> -> http://www.securenetterm.com/
-> -> 
-> -> Again just keep in mind that FTP and Telnet scripting is a non-compliant
-> -> basic method suited to simple Node to Hub requirements, its not 
-> suitable as
-> -> a model for running a QWK Network.
->  
 
--- Platinum Xpress/Win/WINServer v3.1