Subj : 21:1/100 "Warning: remote set UNSECURE session"
To   : Oli
From : Oli
Date : Sat May 22 2021 08:33 am

Did someone suggest to use the -r parameter with binkd? That would explain it:

usage: binkd [-CcDipqrsvmh] [-P node] config
  -D       run as daemon
  -C       reload on config change
[...]
  -r       disable crypt traffic


Oli wrote (2021-05-21):

 O> + 12:06 [1936] call to 21:1/100@fsxnet
 O> + 12:06 [1936] outgoing session with net1.fsxnet.nz:24556 [...]
 O> [...]
 O> - 12:06 [1936] SYS Agency + Risa HUB
 O> [...]
 O> + 12:06 [1936] Remote has 0b of mail and 0b of files for us
 O> - 12:06 [1936] OPT EXTCMD GZ BZ2
 O> + 12:06 [1936] Remote supports EXTCMD mode
 O> + 12:06 [1936] Remote supports GZ mode
 O> + 12:06 [1936] Remote supports BZ2 mode
 O> ? 12:06 [1936] Warning: remote set UNSECURE session
 O>                                     ^^^^^^^^
 O> + 12:06 [1936] pwd protected session (MD5)
 O> + 12:06 [1936] done (to 21:1/100@fsxnet, OK, S/R: 0/0 (0/0 bytes))

 O> Why doesn't 21:1/100 offer an CRYPT OPT?

 O> ---
 O>   * Origin: . (21:3/102)

---
 * Origin: . (21:3/102)

.