Chemi wrote:

More info about this problem. Reading log file:
...

It seems to me that James doesn't send correctly the end information to the client to end the communication. Or Mozilla and Jakarta Common-Net doesn't know when the communictaion has ended, but.... it is 2 against 1. :-)

Have you seen this behavior before?

Yep. Reader waits till timeout, server never delivers. Workaround: edit the article and press enter at the last line...

Regards...


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



Reply via email to