Subj : Nothing in Outbound Area
To   : Peter Knapper
From : Mvan Le
Date : Fri Sep 15 2034 05:48 am

[...]
 
 PK> The entire process is designed to demonstrate that you 
 PK> know HOW to use your Software and follow instructions.
 
 ML> I'm at the stage where I have everything configured, 
 ML> but BinkleyTerm refuses 
 ML> to work with an unlisted address and there isn't a 
 ML> configuration option to   
 ML> turn this restriction off, which seems counter 
 ML> productive to me.             

 PK> See further on on how to solve that.

Your reply has led me to notice that bt-ref.txt mentions 
that if BossPwd and BossPhone are used together, a nodelist 
is not required:

  BossPwd <password>

  Used for Point installations, this statement designates 
  the password to be used for session-level passwording 

  [...]

  When this statement AND 'BossPhone' are BOTH 
  implemented, a nodelist is NOT required for a Point 
  system.

[...]

 PK> No he shouldn't, but the important part is that as the 
 PK> Nodelist is almost NEVER used raw, it is always complied, 
 PK> and the compilation process allows you to ADD specific 
 PK> Details concerning -
 PK> 1. Phone numbers for existing nodes,
 PK> 2. Session passwords for existing nodes,
 PK> 3. Details concerning NEW nodes not listed in the standrd Nodelist,
 PK> 4. Special operating instructions (EG special Modem 
 PK> configuration parameters, etc).

What nodelist editor do I use for this ?

I heard people were using Makenl. 

 PK> A node never EXPORTS a RAW Nodelist so no-one else sees your COMPILED
 PK> version  of the nodelist, and as long as it contains your OWN 
 PK> specific temporary details that you are using, BinkelyTerm is happy.

 PK> The reason for this is that if you set up Session Level 
 PK> passwords for any of your Links, the passwords HAVE to be 
 PK> entered into your COMPILED Nodelist, and its the Compiling 
 PK> process that does this.

The simplest way is to enable BossPwd and BossPhone in Binkley.cfg.

You'd only need to get involved with nodelist if connected to
multiple networks.

Even then it doesn't feel right. Session passwords should be
configured in the mailer imo. 

[...]

 PK> For example, here in Net 3:772 our specific instructions 
 PK> advise you to -  1. Configure your Mailer at address 
 PK> 3:772/99. 
 PK> 2. Then Poll the NC (3:772/0 using the Nodelist entry) for the next
 PK> step.  3. The NC's system is configured to then send a Netmail 
 PK> to 3:772/99 with further instructions 
 PK> 4. Those instructions advise you perform certain 
 PK> functions and REPLY to the NC with YOUR system set as 
 PK> 3:772/999. You then wait for a reply. 
 PK> 5. If those steps worked then you will receive a reply from the NC
 PK> with  either a request for more info or details regarding your 
 PK> assigned Fidonet node number. 

Geeze that seems pretty long winded. 

When I had FidoNet all we had to do was pack the password with each
message using Squish.

 PK> I am not the NC, however if anyone calls here as 3:772/99, 
 PK> my system will resond advising they have contacted the 
 PK> WRONG Node, and what steps they need to take to contact the 
 PK> correct node.

What mailer are you using ?


.... DOS never says "EXCELLENT command or filename"...
___ Blue Wave/386 v2.30

--- Maximus 3.01
 * Origin: The Dog House * Orillia ON Canada * bbs.doghousebbs.com (1:229/1394)

.