You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by ji...@apache.org on 2004/04/01 12:27:45 UTC

[jira] Updated: (JAMES-241) fail gracefully upon large messages/attachments

The following issue has been updated:

    Updater: Danny Angus (mailto:danny@apache.org)
       Date: Thu, 1 Apr 2004 2:25 AM
    Comment:
Raised the priority and severity of this issue because an OMOException which can be caused by a client during SMTP is a serious DOS vulnerability
    Changes:
             type changed from Improvement to Bug
             priority changed from Major to Critical
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/JAMES-241?page=history

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

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JAMES-241
    Summary: fail gracefully upon large messages/attachments
       Type: Bug

     Status: Unassigned
   Priority: Critical

    Project: James
 Components: 
             POP3Server
   Versions:
             2.1.3

   Assignee: 
   Reporter: Ralf Hauser

    Created: Thu, 1 Apr 2004 12:57 AM
    Updated: Thu, 1 Apr 2004 2:25 AM
Environment: redhat 9

Description:
I am aware of the <maxmessagesize> to prevent too large messages getting into james and the corresponding fast-fail discussions (http://marc.theaimsgroup.com/?l=james-user&m=108040337403426&w=2, http://nagoya.apache.org/jira/browse/JAMES-134).
When uploading via a web-mail interface into my MySQL mailstore, I got messages up to 14MB through the system.

However, I would like to know what is the maximum I can safely handle.
I didn't find anything documented.
I did increase the heap for my JVM in phoenix.sh with PHOENIX_OPTS=-Xmx512m, but on a 45MB attachments, it fails with little useful error output:
<<[root@myhost logs]# less connections-2004-04-01-09-24.log
01/04/04 09:24:35 ERROR connections: Error handling connection
java.lang.OutOfMemoryError>>

Especially, since my adaptation of the MySQL mailstore also explicitly stores attachment sizes, I could stop that message from being pushed through the pop3 server before it is in memory and causes problems and then could issue error message saying (e.g. "message ABC too large - please retrieve via webMail interface" instead of the current <<
Task 'sPop test account - Receiving' reported error (0x800CCC0F) : 'The connection to the server was interrupted.  If this problem continues, contact your server administrator or Internet service provider (ISP).'>> I see in my MUA)


---------------------------------------------------------------------
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