Blank page when folder contains too many emails

When a folder contains too many message (not sure what the t

Mon, 14 Mar 2011 04:31:54 +0000

When a folder contains too many message (not sure what the threshold is), I get a blank page (no error message, nothing) when trying to view the content of the folder. When #of messages <1500, by navigating to another folder and coming back to the desired folder normally solves the issue. In this particular case, I hadn't clean my Trash folder in several days and 4400 emails had accumulated. I was not able to access my Trash folder from Horde but only from a shell.

Please follow the hints at http://wiki.horde.org/FAQ/Admin/T

Mon, 14 Mar 2011 05:53:05 +0000

Please follow the hints at http://wiki.horde.org/FAQ/Admin/Troubleshoot#wsod to generate and find a useful error message.

I have finally been able to reproduce the blank page error c

Wed, 08 Jun 2011 22:26:52 +0000

I have finally been able to reproduce the blank page error consistently. I recently received one email with a 8+MB attachment. Every time I try to open this email in horde, I get a blank page. Looking at the logs, there is nothing in either /var/log/apache2/error.log or in /tmp/horde.log /tmp/horde.log contains only login success and logout lines. This is totally useless! From this behavior it is clear that there is a memory limit that stops the execution to a blank page. Shouldn't the error be catched and an error message returned to the user instead of a blank page? In my conf.php file, I have: $conf['debug_level'] = E_ALL; $conf['log']['name'] = '/tmp/horde.log'; $conf['log']['type'] = 'file'; $conf['log']['enabled'] = true; $conf['fetchmail']['size_limit'] = '10000000'; $conf['compose']['attach_size_limit'] = '0'; So my questions are: 1) How can I disable the NO error_reporting() in horde? Where is the switch that would put back horde in testing mode? 2) Why the error(s) is(are) not reported in the logs (horde or apache)!

> From this behavior it is clear that there is a memory limi

Wed, 08 Jun 2011 22:39:35 +0000

> From this behavior it is clear that there is a memory limit that > stops the execution to a > blank page. > Shouldn't the error be catched and an error message returned to the > user instead of a blank page? It will if error_reporting in PHP is set to output errors to the page. > 2) Why the error(s) is(are) not reported in the logs (horde or apache)! It will be reported to wherever *PHP* is configured to log to.