Subj : Re: Blam BBS List question To : The Godfather From : alterego Date : Wed May 27 2020 11:19:12 Re: Re: Blam BBS List question By: The Godfather to alterego on Tue May 26 2020 09:03 pm al>> Ahh, I have an idea. al>> If you edit your nodelist and change the INA: to an al>> INA:: does it fix your problem? 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 TG> nodelist or when others look me up, they'll be dialing into the wrong TG> port. Well .. telnetting into the wrong port. In addition, the Right, that's why I'm suggesting you edit your nodelist to validate that if the network admin did update the nodelist that it would work. (IE: No point sending out an updated nodelist, if it doesnt help this cause :) The only field that I think could be updated, that *may* not affect other BBS mailer operations is the INA field. (I may be wrong though...) If updating the INA field enables your script/mod to connect to other BBSes on a non-standard telnet port, then we just need to validate that binkp still works (does it use the INA field - not sure - if the node is not defined in the node manager). If still does work, then network admins could record "telnet access details" to BBSes in the INA field. ....лоеп .... Federal Employment Principle: Confusion creates jobs. --- SBBSecho 3.11-Linux * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116) .