Subj : binkd and mystic and secure sessions
To   : mark lewis
From : Nicholas Boel
Date : Thu Dec 15 2016 07:09 am

Hello mark,

On 15 Dec 16 05:04, mark lewis wrote to Allen Prunty:

 ml> that option helps in some cases... i requested it be added because
 ml> stats were wrong... i was polling a system in an othernet supposedly
 ml> with my othernet address but that other system's stats were logging
 ml> everything with my main address which was not in that othernet...
 ml> there was no connection or link between us with that main address so
 ml> their stats were technically wrong... by hiding the other addresses,
 ml> there was only one presented to them and their stats were now
 ml> technically correct... i think it would have been easier for mystic to
 ml> present the common address first in the list of addresses and avoid
 ml> the problem in the first place but someone didn't see that or they
 ml> didn't understand the problem... there is a reason for having AKA
 ml> matching ;)

Fairly certain this was coded per spec (or proposal even). Most mailers do not 
match the common AKA. They usually work in a top-down list and match the first 
one that matches. So if you and I both have a Fidonet address, it will try to 
use that first. If it fails, it will go to the next matching AKA in the list. 
This is how binkd, Argus/Taurus/Radius, Irex, and any other mailers I've used 
in the past currently operate.

I don't know of any mailers that do not do it this way (while I don't agree 
with the method, but whatever). This was why the "Hide AKAs" was added to 
Mystic in the first place.. to get past that issue if it were to come up.

Regards,
Nick

.... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20160827
 * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

.