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 10:59:46 UTC
[jira] Created: (JAMES-241) fail gracefully upon large messages/attachments
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:
<<[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
[jira] Updated: (JAMES-241) fail gracefully upon large messages/attachments
Posted by ji...@apache.org.
The following issue has been updated:
Updater: Danny Angus (mailto:danny@apache.org)
Date: Thu, 1 Apr 2004 2:29 AM
Comment:
I see that it is only during a POP get, which is less serious than I had thought, but still a vulnerability
Changes:
priority changed from Critical to Major
---------------------------------------------------------------------
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: 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 2:29 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
[jira] Commented: (JAMES-241) fail gracefully upon large messages/attachments
Posted by se...@james.apache.org.
The following comment has been added to this issue:
Author: Ralf Hauser
Created: Sat, 19 Jun 2004 11:37 PM
Body:
got a little bit further: PHOENIX_OPTS as described in the phoenix.sh is never used while really
PHOENIX_JVM_OPTS=-Xmx512m works.
==> this way, I could retrieve 44 MB !!!
although, I first tried to sign it (openssl) that process wouldn't finish before the MUA timed out ...
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/JAMES-241?page=comments#action_36246
---------------------------------------------------------------------
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: Major
Project: James
Components:
POP3Server
Versions:
2.1.3
Assignee:
Reporter: Ralf Hauser
Created: Thu, 1 Apr 2004 12:57 AM
Updated: Sat, 19 Jun 2004 11:37 PM
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
[jira] Resolved: (JAMES-241) fail gracefully upon large
messages/attachments
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Norman Maurer resolved JAMES-241.
---------------------------------
Resolution: Fixed
Fix Version/s: (was: Trunk)
3.0-M2
Assignee: Norman Maurer
The POP3Server now use the new Mailbox api which can handle such emails without problems.
> fail gracefully upon large messages/attachments
> -----------------------------------------------
>
> Key: JAMES-241
> URL: https://issues.apache.org/jira/browse/JAMES-241
> Project: JAMES Server
> Issue Type: Bug
> Components: POP3Server
> Affects Versions: 2.1.3
> Environment: redhat 9
> Reporter: Ralf Hauser
> Assignee: Norman Maurer
> Fix For: 3.0-M2
>
>
> 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)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Updated: (JAMES-241) fail gracefully upon large
messages/attachments
Posted by "Stefano Bagnara (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefano Bagnara updated JAMES-241:
----------------------------------
Assignee: (was: Stefano Bagnara)
Removed myself as assignee as I'm not willing to work on this in the near future. In the past 2 years I've applied some patches to increase the probability to be able to stream only the message without loading, but this still does not happen on every case.
> fail gracefully upon large messages/attachments
> -----------------------------------------------
>
> Key: JAMES-241
> URL: https://issues.apache.org/jira/browse/JAMES-241
> Project: James
> Issue Type: Bug
> Components: POP3Server
> Affects Versions: 2.1.3
> Environment: redhat 9
> Reporter: Ralf Hauser
> Fix For: Trunk
>
>
> 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)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Assigned: (JAMES-241) fail gracefully upon large
messages/attachments
Posted by "Stefano Bagnara (JIRA)" <se...@james.apache.org>.
[ http://issues.apache.org/jira/browse/JAMES-241?page=all ]
Stefano Bagnara reassigned JAMES-241:
-------------------------------------
Assign To: Stefano Bagnara
> fail gracefully upon large messages/attachments
> -----------------------------------------------
>
> Key: JAMES-241
> URL: http://issues.apache.org/jira/browse/JAMES-241
> Project: James
> Type: Bug
> Components: POP3Server
> Versions: 2.1.3
> Environment: redhat 9
> Reporter: Ralf Hauser
> Assignee: Stefano Bagnara
>
> 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)
--
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
-
For more information on JIRA, 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
[jira] Updated: (JAMES-241) fail gracefully upon large messages/attachments
Posted by ji...@apache.org.
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