Folks, Something seems to have gone wonky with the code in James CVS. It builds and runs, OK but it is throwing up errors I haven't seen before. 1) Connecting with Netscape Messenger on Win ME or Linux to James on Linux, the client reports an error and the server log shows excption null e.g. Mon Mar 12 17:08:21 GMT+00:00 2001 [INFO ] <<james.connections>> (default Worker #0): Command received: STAT Mon Mar 12 17:08:21 GMT+00:00 2001 [INFO ] <<james.connections>> (default Worker #0): Command received: LIST Mon Mar 12 17:08:21 GMT+00:00 2001 [INFO ] <<james.connections>> (default Worker #0): Command received: UIDL Mon Mar 12 17:08:22 GMT+00:00 2001 [INFO ] <<james.connections>> (default Worker #0): Command received: RETR 1 Mon Mar 12 17:08:22 GMT+00:00 2001 [INFO ] <<james.connections>> (default Worker #0): Command received: DELE 1 Mon Mar 12 17:08:22 GMT+00:00 2001 [INFO ] <<james.connections>> (default Worker #0): Command received: RETR 2 Mon Mar 12 17:08:22 GMT+00:00 2001 [INFO ] <<james.connections>> (default Worker #0): Command received: DELE 2 Mon Mar 12 17:08:22 GMT+00:00 2001 [ERROR ] <<james.connections>> (default Worker #0): Exception during connection from kestrel (192.168.1.3) : null Mon Mar 12 17:08:22 GMT+00:00 2001 [DEBUG ] <<james.connections>> (default Worker #0): Ending connection on Socket[addr=kestrel/192.168.1.3,port=1720,localport=110] 2) Sending mail from WinME to James on Linux, client reports error opening connectin, as does server: Mon Mar 12 17:15:42 GMT+00:00 2001 [DEBUG ] <<james.connections>> (default Worker #1): Starting connection on Socket[addr=kestrel/192.168.1.3,port=1725,localport=25] Mon Mar 12 17:15:42 GMT+00:00 2001 [INFO ] <<james.connections>> (default Worker #1): Connection from kestrel (192.168.1.3) Mon Mar 12 17:15:42 GMT+00:00 2001 [DEBUG ] <<james.connections>> (default Worker #1): Exception opening socket: null Mon Mar 12 17:15:42 GMT+00:00 2001 [DEBUG ] <<james.connections>> (default Worker #1): Ending connection on Socket[addr=kestrel/192.168.1.3,port=1725,localport=25] Neither of these were happening before and the pre-connections code still works fine, so I guess this is from the new connections code. But I thought the rationale for replacing the (cornerstone) sockets code with the (cornerstone) connections code was that connections was better?? Has anyone else seen similar errors? Charles --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
