Uploaded image for project: 'James Server'
  1. James Server
  2. JAMES-320

Some messages cause POP3 output stream to freeze on RETR.

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Fixed
    • 2.2.0
    • 2.3.0
    • POP3Server
    • None
    • 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.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            bago Stefano Bagnara
            gduffy Greg Duffy
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment