Subj : bad password
To   : Bj”rn Felten
From : Tommi Koivula
Date : Thu Apr 28 2016 08:27 pm

Hi Bj”rn.

29 Apr 16 03:15, you wrote to All:

 BF> Suddenly (without any known changes having been made on my system) I get a
 BF> "bad password" error to two of the circa 20 systems I connect to.

 BF>    They both have one thing in common -- "VER Argus/3.208/ binkp/1.0"

 BF>    I cannot for the life of me figure out what's wrong. When I let my 
Argus
 BF> crash the mail (the same password since decades ago) it works perfectly
 BF> well, but not from binkd.

 BF>    But I also encountered the old 'expected password "-"' error when no
 BF> password was entered recently. Did anyone discover what this was caused 
by?

 BF>    Is there some setting in binkd that can cause/fix this?

 BF>    Any help or suggestions would be muchly appreciated!

I remember seeing something like this a long time ago and it was related to the 
aka order.

Your binkd has akas:

VER binkd/1.1a-65/Win32 binkp/1.1
addr: 2:203/2@fidonet
addr: 2:203/0@fidonet
addr: 2:20/0@fidonet
addr: 2:2/2@fidonet

And your 'Argus':

VER Tedious/3.211/ binkp/1.0
addr: 2:203/0@fidonet
addr: 2:203/2@fidonet
addr: 2:20/0@fidonet
addr: 2:2/2@fidonet
addr: 2:203/1@fidonet

So, I'd try to adjust the order in binkd...

'Tommi

---
 * Origin: ====================================== (2:221/6)

.