james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Updated: (JAMES-241) fail gracefully upon large messages/attachments
Date Thu, 01 Apr 2004 10:29:45 GMT
The following issue has been updated:

    Updater: Danny Angus (mailto:danny@apache.org)
       Date: Thu, 1 Apr 2004 2:29 AM
I see that it is only during a POP get, which is less serious than I had thought, but still
a vulnerability
             priority changed from Critical to Major
For a full history of the issue, see:


View the issue:

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

     Status: Unassigned
   Priority: Major

    Project: James

   Reporter: Ralf Hauser

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

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

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)

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

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

View raw message