I ran the telnet test and everything worked as expected (I couldn't delete the same message twice). I'm still having problems popping messages from James but don't have any new ideas as to what might be causing it.
-J
Its true that James doesn't hang, rather it seems to prematurely abort, possibly because Netscape closes the connection. You can see that there are 594 messages in the queue, but after 'RETR 3' there is a reset and a stop.
There are messages, but Netscape isn't asking for them. The "reset()" message is just a debugging notice in James that it is resetting the watchdog timer for that connection.
What I don't understand is why Netscape was able to pop the same messages from my ISP successfully, but gets stuck popping from James.
Well, the fact that DELE x works multiple times in a row is bothersome.
I'm using James 2.1.2. It may be worth noting that I'm using the filesystem to store messages not the database.
I did my test with James v2.2.0a8 using JDBC, but the file system shouldn't be the issue. The DELETE operation is handled internally. I just checked the diff between the code I'm running, and v2.1.2, and I don't see anything that would make a difference.
http://cvs.apache.org/viewcvs/james-server/src/java/org/apache/james/pop3ser ver/POP3Handler.java.diff?r1=1.18.4.3&r2=1.18&diff_format=h&only_with_tag=br anch_2_1_fcs
Can you run the same telnet test I did and check the results?
--- Noel
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
