Noel, Yes, I can turn on debug. After sending the previous message i did notice that the correct file size is displayed in outlook express. i think the issue is in forte free agent....maybe....
i have also noticed james is throwing errors in nntpserver.log constantly 10/01/03 09:17:35 ERROR nntpserver: NNTP Connection has idled out. 10/01/03 09:17:35 ERROR nntpserver: Exception during connection:socket closed java.net.SocketException: socket closed at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(Unknown Source) at sun.nio.cs.StreamDecoder$CharsetSD.readBytes(Unknown Source) at sun.nio.cs.StreamDecoder$CharsetSD.implRead(Unknown Source) at sun.nio.cs.StreamDecoder.read(Unknown Source) at java.io.InputStreamReader.read(Unknown Source) at java.io.BufferedReader.fill(Unknown Source) at java.io.BufferedReader.readLine(Unknown Source) at java.io.BufferedReader.readLine(Unknown Source) at org.apache.james.nntpserver.NNTPHandler.handleConnection(NNTPHandler.java:35 7) at org.apache.james.util.connection.ServerConnection$ClientConnectionRunner.run (ServerConnection.java:404) at org.apache.avalon.excalibur.thread.impl.ExecutableRunnable.execute(Executabl eRunnable.java:47) at org.apache.avalon.excalibur.thread.impl.WorkerThread.run(WorkerThread.java:8 0) ----- Original Message ----- From: "Noel J. Bergman" <[EMAIL PROTECTED]> To: "James Users List" <[EMAIL PROTECTED]> Sent: Friday, January 10, 2003 9:20 AM Subject: RE: NNTP: Nightly Build available for testing > > i just tested the new nntp james.sar. outlook express was able to see and > > retrieve yesterdays test post. i did another test post with a binary > > attachment (.jpg) and that worked well. i just did a second test post with > a > > multi-part binary attachment (.mp3) and it posted and decoded perfectly. > > Well those are good things to hear. :-) > > > the only issue i see is the reported file size of 65535 for every post. > > don't know if this is james or free agent...... > > Randy, there is a known bug were James reports -1 for the line count. But > it should report the correct byte count. Can you turn on debugging, and see > if we spot the source of the faulty size in the log file? > > --- Noel > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
