On 09/24/14, Avon said the following...
The feedback from his end is:
This is what my Radius reports during connects to your Mystic...
: 23-Sep-2014 16:35:55 Mailer : Mystic/1.10 binkp/1.0
Then, when there was trouble...
23-Sep-2014 16:35:55 Aborting due to carrier loss
Which is what the BinkD FAQ states is caused by some shifty encryption attempt by a Radius mailer.
it isn't really "shifty" but simply mis-coded such that radius/argus assumes that the other side can handle it... as the FAQ states, it should check the other side's capabilities first and then not use it OR send an M_ERR block stating why the session is being aborted...
i suspect that they were going to try to get the method added to binkd but never got that far due to problems around those times... i can't help but to wonder if Taurus fixed this problem since it comes from the same code and has many fixes and improvements...
--- Mystic BBS v1.10 A52 (Windows)
* Origin: (46:1/132)
■ Synchronet ■ thePharcyde_ >>
telnet://bbs.pharcyde.org (Wisconsin)