Hello Dan,

 DE> I only have client side experience with BinkD but I've had nothing but 
 DE> problem after problem with it. Janis runs BinkD on her 
 DE> standard BinkP port 24554, as well as BBBS's native 
 DE> BinkD driver on 24555. I can connect to her BBBS no 
 DE> sweat. If I ever try to connect to her BinkP it 
 DE> immediately disconnects me. In the logs it says I 
 DE> presented an "invalid address: 1:3005/3 115:1502/110". 
 DE> i.e. It's seeing both my address as a single item and 
 DE> complaining. But the exact same setup has me connecting 
 DE> to both Irex and to BBBS with 0 hickups. That is how I 
 DE> deem unreliable.

Binkd requires 5D adressing AFAIK (can be a pita). In BinkleyTerm 5D
addressing was optional but in binkd it works that way. Your domains
need to be configured first in binkd.cfg, mine are like this.. 

domain fidonet /max/spool/outbound 1
domain fido alias-for fidonet
domain fidonet.org alias-for fidonet
domain acnet alias-for fidonet

Like that may outbound looks like it always did with BinkleyTerm. And
then your addresses are configured with 5D addressing.

Address 1:132/500.19{at}fidonet 63:63/103{at}acnet

That works for me problem free.

 Ttyl :-),
         Al

--- Maximus/UNIX 3.03b