Hey Alan,

-=> Alan Ianson wrote to Dan Egli <=-

 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.

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

As you write in your example Binkd can handle 4D too. :) But the Domain 
is required, but it's not for a normal EMSI session, so Binkleyterm 
doesn't work with domains.

 AI> That works for me problem free.

Me too. :)

Bo


... What is mind? No matter! What is matter? Never mind! - Homer S.
___ MultiMail/Linux v0.46

--- Maximus/UNIX 3.03b