Message: A new issue has been created in JIRA.
--------------------------------------------------------------------- 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: Improvement Status: Unassigned Priority: Major 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 12:57 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: <<[EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
