Noel, I've been up on 2.2.0 RC3 for a few days now as you suggested. I'm still having a problem with timeouts(?). To refresh your memory:
This is coming from a list. The message in question apparently has nulls at the end. I think four, but I don't get to see them because of the problem. I believe that James is hanging up when it encounters the nulls (you can see a couple minutes go by below right after the 354 response). What I do know is that the list puts a footer on the message that I don't see (because I think James is hung up at that point). The list owner says that he is timing out on his side. It appears that the sender breaking connection is what gets James going again. 20/05/04 10:44:30 DEBUG smtpserver: Getting SMTPHandler from pool. 20/05/04 10:44:30 INFO smtpserver: Connection from nt.phred.org (216.254.27.122) 20/05/04 10:44:30 DEBUG smtpserver: Sent: 220 leela SMTP Server (JAMES SMTP Server 2.2.0RC3) ready Thu, 20 May 2004 10:44:30 -0400 (EDT) 20/05/04 10:44:30 DEBUG smtpserver: Calling start() 20/05/04 10:44:30 DEBUG smtpserver: Watchdog default Worker #14 has time to sleep 360000 20/05/04 10:44:30 DEBUG smtpserver: Command received: EHLO catfood.nt.phred.org 20/05/04 10:44:30 DEBUG smtpserver: Sent: 250 leela Hello catfood.nt.phred.org (nt.phred.org [216.254.27.122]) 20/05/04 10:44:30 DEBUG smtpserver: Calling reset() default Worker #14 20/05/04 10:44:30 DEBUG smtpserver: Command received: MAIL FROM:<[EMAIL PROTECTED]> 20/05/04 10:44:30 DEBUG smtpserver: Sent: 250 Sender <[EMAIL PROTECTED]> OK 20/05/04 10:44:30 DEBUG smtpserver: Calling reset() default Worker #14 20/05/04 10:44:30 DEBUG smtpserver: Command received: RCPT TO:<[EMAIL PROTECTED]> 20/05/04 10:44:30 DEBUG smtpserver: Sent: 250 Recipient <[EMAIL PROTECTED]> OK 20/05/04 10:44:30 DEBUG smtpserver: Calling reset() default Worker #14 20/05/04 10:44:30 DEBUG smtpserver: Command received: DATA 20/05/04 10:44:30 DEBUG smtpserver: Sent: 354 Ok Send data ending with <CRLF>.<CRLF> 20/05/04 10:46:59 INFO smtpserver: Successfully spooled mail Mail1085064270933-1002 from [EMAIL PROTECTED] for [EMAIL PROTECTED] 20/05/04 10:46:59 DEBUG smtpserver: Sent: 250 Message received 20/05/04 10:47:00 DEBUG smtpserver: Calling reset() default Worker #14 20/05/04 10:47:00 DEBUG smtpserver: Calling stop() default Worker #14 20/05/04 10:47:00 DEBUG smtpserver: Closing socket. 20/05/04 10:47:00 DEBUG smtpserver: Calling disposeWatchdog() default Worker #14 20/05/04 10:47:00 DEBUG smtpserver: Watchdog default Worker #14 is exiting run(). 20/05/04 10:47:00 DEBUG smtpserver: Returning SMTPHandler to pool. 20/05/04 10:47:00 DEBUG smtpserver: Returning a org.apache.james.smtpserver.SMTPHandler to the pool > -----Original Message----- > From: Noel J. Bergman [mailto:[EMAIL PROTECTED] > Sent: Friday, May 14, 2004 1:19 PM > To: James Users List; [EMAIL PROTECTED] > Subject: RE: Nulls hanging up James? > > > > > The smtp log shows over 2 minutes from the 354 response. Talking to > > the list owner, it looks like his server is timing out and then > > james is sending the 250. > > That's odd. James should catch an error if there is a > timeout. It should > need to see the <CRLF>.<CRLF>. I just did a test where I > started a message, > and then left it hanging in the middle of the DATA command. > Please test > with 2.2.0RC3. If necessary, we can do a special build with > some extra > debugging code. > > --- Noel > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
