Subj : Re: binkd and mystic and secure sessions
To   : Tony Langdon
From : Allen Prunty
Date : Wed Dec 14 2016 06:12 pm

Bink-D assumes 0... but mystic auto fills out the .0

:-)

I've seen someone somehow put a space in that field and it messed things up.

Allen

On Dec 15, 2016 08:07am, Tony Langdon wrote to Allen Prunty:

-=>> Allen Prunty wrote to Lindsay Zellner <=-

 AP>> I don't know if you ever got this resolved.  Mystic can be very
 AP>> literal... have the node you are connected with set NOT to send you
 AP>> their AKAs.  That seemed to fix a similar issue I had with a mystic
 AP>> node.

 TL> I've had no issues.  I used to transfer a lot of mail between my two
 TL> BBSs - one Mystic, one binkd.

 AP>> Also you need to make sure you have the same domain programmed in your
 AP>> binkd.cfg as they do.

 AP>> Mystic is very literal and binkd needs to have in it's node entry the
 AP>> full 5d domain

 AP>> 1:111/111.0@fidonet

 TL> I haven't found the need to put the point into my node entries (unless
 TL> it's a point, of course ;) ).

 AP>> The domain must match exactly case sensative.

 TL> Agree, domains must match.


 TL> ... Useless Invention: Umbrella with a skylight.
 TL> --- MultiMail/Win32 v0.49
 TL>  * Origin: Freeway BBS - freeway.apana.org.au (3:633/410)
--- Platinum Xpress/Win/WINServer v3.0pr5
 * Origin: LiveWireBBS.com -=* Happy Holidays *=- Deus Te Amat (1:2320/100)

.