Just an update for anybody that reads this thread... The pop problem has been fixed in 2.2 (possibly in 2.1.3 also but I didn't try it), although I'm still not sure exactly what caused it.

-J

Jay Kraly wrote:

Yes. Will it be a build of 2.2 or 2.1?

-J

Noel J. Bergman wrote:

Nothing shows up in the logs in terms of exceptions. The only thing I
do see is a stop() from james when the disconnect happens, but I
haven't been able to figure out what is generating it.


There is only one way to get a stop() in the log. POP3Handler.parseCommand
has to return false. There are two ways for that to happen:


 1. in.readLine() == QUIT
 2. in.readline() == null

An exception will not cause that to happen.

I don't like something that I see in the code. It appears to have the same
bug that we fixed earlier in SMTPHandler. It is relying upon a
BufferedReader, which can lead to problems due to CRLF handling.
BufferedReader should be replaced by CRLFTerminatedReader. I don't know if
that would fix your problem, but it might.


If I do a private build, do I have your permission to e-mail a SAR to you
for testing?


--- Noel


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]








--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to