Subj : Re: Blam BBS List question
To   : The Godfather
From : Avon
Date : Wed May 27 2020 14:32:26

On 26 May 2020 at 09:03p, The Godfather pondered and said...
 
 TG> It's not as much a nodelist issue as it is the specific script manya re
 TG> using on their BBS's for their BBSlist.  The script does not appear to be
 TG> recognizing <hostname>:<port> and defaulting to port 23.  While I could
 TG> likely fix it on my BBS, I can't do so on others who have my BBS listed. 
 TG> This is where the nodelist, I THINK (not sure,) can come into play.  I
 TG> THINK, not sure, the network lead dude has to change my port within the

I think it comes down to what the script code does and if it even looks for
anything about the telnet port from a nodelist or if it just assumes 23

For my part just reading the exchange between yourself and Deon I agree with
Deon that the INA may be the best place to put the telnet port info. I'm not
honestly sure and will need to try and read up on this. I have been (and I
think incorrectly) been using the ITN flag to note this but I think that flag
is really only for use to signal a Telnet based mailer on the port stated.

Hmmm

PS - please accept this as a reply to your email also. I did get that.

--- Mystic BBS v1.12 A46 2020/04/20 (Windows/32)
 * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

.