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

 BF> Suddenly (without any known changes having been made on my system) I
 BF> get a "bad password" error to two of the circa 20 systems I connect
 BF> 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
 BF> Argus crash the mail (the same password since decades ago) it works
 BF> perfectly well, but not from binkd.

i don't think i've seen this with my taurus system...

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

this one i've seen and it was due to a misunderstanding of the spec or what was
being seen in RL testing... some actually place a '-' in the field and transmit
that encoded as needed... what should actually be being done is not sending a
password at all or sending an encoded blank/nul message...

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

the only thing i know of is for the developer of the software to get their
binkp implementation fixed or relaxed or such... one or two of the RAT
(Radius/Argus/Taurus) mailers has a problem like this and i remember reading
something about bugs in similar areas...

 BF>    Any help or suggestions would be muchly appreciated!

you got the code? ;)

)\/(ark

Always Mount a Scratch Monkey

... It must be Thursday. I never could get the hang of Thursdays.
---