RN> That would explain this then, but you did connect:

 RN> =====================================================================
 RN> ===== 20120318 09:29:23 [2840] incoming from 75.1.38.203
 RN> (75.1.38.203) 20120318 09:29:23 [9412] session with 75.1.38.203
 RN> (75.1.38.203) 20120318 09:29:23 [9412] OPT MB CRC MD5 20120318
 RN> 09:29:23 [9412] SYS SATX Alamo Area Net 20120318 09:29:23 [9412] ZYZ
 RN> Roy Witt 20120318 09:29:23 [9412] LOC San Antonio, Texas, USA
 RN> 20120318 09:29:23 [9412] NDL CM,MO,INA,IBN 20120318 09:29:23 [9412]
 RN> TIME 2012/03/18 02:30:00 -5:00 20120318 09:29:23 [9412] VER Internet
 RN> Rex 2.29 Win32 (binkp/1.1) 20120318 09:29:23 [9412] addr:
 RN> 1:387/22{at}fidonet 20120318 09:29:23 [9412] addr: 1:387/0{at}fidonet
 RN> 20120318 09:29:23 [9412] addr: 1:387/1{at}fidonet 20120318 09:29:23
 RN> [9412] addr: 1:387/6{at}fidonet 20120318 09:29:23 [9412] pwd protected
 RN> session (MD5) 20120318 09:29:24 [9412] done (from 1:387/22{at}fidonet,
 RN> OK, S/R: 0/0 (0/0 bytes)) 20120318 09:29:24 [9412] session closed,
 RN> quitting...
 RN> =====================================================================
 RN> =====

 RW> So I don't have to turn off the CRAM-MD5 session protocol in your
 RW> configuration here.

you should not have to turn off CRAM-MD5 at all... for anyone unless
there's a config problem... or possibily a version incompatibility...

)\/(ark