Subj : Re: binkd and mystic and secure sessions
To   : Allen Prunty
From : Tony Langdon
Date : Thu Dec 15 2016 08:17 am

-=> 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.

I've had no issues.  I used to transfer a lot of mail between my two 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

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

 AP> The domain must match exactly case sensative.

Agree, domains must match.


.... Useless Invention: Umbrella with a skylight.
--- MultiMail/Win32 v0.49
 * Origin: Freeway BBS - freeway.apana.org.au (3:633/410)

.