Subj : possible emsi protocol bug in binkd
To   : Michiel van der Vlist
From : Kees van Eeten
Date : Tue Jan 30 2018 03:40 pm

Hello Michiel!

30 Jan 18 14:46, you wrote to Benny Pedersen:

 BP>> just in case, if qico runs in xinetd with -a auto, then binkp clients
 BP>> stale, this is a bug in binkd

 MvdV> No, it is not a bug. You are trying to make it do it was never designed
 MvdV> for.

 BP>> so binkp protocol clients does not always work with autodetect in
 BP>> qico, so i loose emsi on same port as binkp

 MvdV> Of course it does not work. Binkp was never designed to share a port.
 MvdV> Like most protocols, it was designed to have a port of its own.

 MvdV> The solution is easy: forget about EMSI. Binkp was optimized for use
 MvdV> over IP, EMSI was not. Who needs EMSI when you have binkp?

 I think you are confusing the matter. The way I would implement the auto
 detect, is to look at the fingerprint of waht comes in first. Does it look
 like a binkp or like an EMSI handshake and switch accordingly.

 qico should probably just needs an upgrade in its protocol recognistion.

 I think we have had more or less the same with an other mailer, where the
 calling system had to make shure that a lower version of the binkp protocol
 should be used.

 But the workaround is there, don't use auto but diffrent port instead. ;))

Kees

--- GoldED+/LNX 1.1.5
 * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)

.