[jira] Commented: (JAMES-320) Some messages cause POP3 output stream to freeze on RETR.

[se...@james.apache.org]

The following comment has been added to this issue:

     Author: jason diprinzio
    Created: Thu, 23 Sep 2004 7:34 PM
       Body:
I've tracked down what I believe to be the issue.  In the server logs, the stack trace leads to org/apache/james/pop3server/POP3Handler.readCommandLine.
In this file line 221, which instantiated a new BufferedReader, was commented out in favor of instantiating a CRLFTerminatedReader.  The stacktrace points to line 98 of this class as the last apache class responsible for the exception.  I commented out the new line and uncommented out line 221 which temporarily fixed the same problem I was having.
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/JAMES-320?page=comments#action_53371

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/JAMES-320

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JAMES-320
    Summary: Some messages cause POP3 output stream to freeze on RETR.
       Type: Bug

     Status: Unassigned
   Priority: Critical

    Project: James
 Components: 
             POP3Server
   Versions:
             2.2.0

   Assignee: 
   Reporter: Greg Duffy

    Created: Thu, 2 Sep 2004 12:21 PM
    Updated: Thu, 23 Sep 2004 7:34 PM
Environment: Server:
Fedora Core 2 Linux (x86)
Sun J2SDK 1.4.2_04

Clients:
FreeBSD/Thunderbird
FreeBSD/Telnet
Windows XP/Outlook
Windows XP/Telnet

Description:
I've been using James on my personal server since about 2.1.3. My domains receive a good deal of spam (on the order of ~1000 per day, spread over the e-mail accounts I host and the postmaster address).

Some of these messages contain attachments (usually virii) that seem to contain characters that will stop the POP3 transmission in the middle of a RETR.

Basically, this means that when you RETR an offending message, GUI mail clients time out and telnet sessions just hang until you escape to console and quit. 

If the message is first in the list, this means most clients will not be able to retrieve the rest of the messages in the inbox.

The only end-user solution is to telnet in, DELE the offending message(s), and then RETR the good ones. 

I'm going to try to attach a sample of an offending message (I haven't used JIRA much). Maybe this is a more general problem with some kind of control characters in the POP3 implementation?

I haven't had a chance to dig in to James's architecture, but I'd love some pointers.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org