Subj : BinkD
To   : Russell Tiedt
From : Bob Jones
Date : Wed Oct 08 2003 02:36 pm

 BJ> Should be relatively simple.  BinkD allows for the 
 BJ> inbound port number
 BJ> to be chanaged (from the default port number) in its control file.
 BJ> The other catch is integrating what comes in via 
 BJ> the BinkD mailer with
 BJ> your other processes.  I run BinkD using a Binkley Style Outbound
 BJ> setup and integrate it with the rest of my fidonet traffic
 BJ> accordingly.  [Ok, So I'm using Binkley for my front end mailer on
 BJ> POTS, telnet and vmodem connections.]

 RT> Yeah, setting it to run on a different port appears to 
 RT> be simply a matter of 
 RT> setting iport and oport, I presume as follows,

 RT> iport binkp 24555
 RT> oport binkp 24556

I believe the port number is supposed to be the only option after the iport or 
oport key word.  If the port number is a name (such as binkp), then I believe 
the code is looking it up in the standard table (/etc/services on most linux or 
unix systems.  Under OS/2, I believe the services file is burried where some of 
the other TCP/IP configuration files are located.)  So, if I am correct, you 
really want:

iport 24555
oport 24556

 RT> But my problem is that BinkP on MBSE is run from 
 RT> inetd.conf, and it appears 
 RT> that if there is a binkp line in inetd.conf then BinkD 
 RT> will not run in daemon 
 RT> mode on my Binkley system, which is how I want to run it. :-((

If you were using your stated lines ('iport binkp 24555' and 'oport binkp 
24556') then I think Binkd was still trying to use the standard ports (binkp), 
and ignoring the 24555 and 24556 port numbers.

Take care.....

Bob Jones, 1:343/41


--- Maximus/2 3.01
 * Origin: Top Hat 2 BBS (1:343/41)

.