• Article for your preferred language does not exist. Below is international version of the article.

Article ID: 112650, created on Oct 27, 2011, last review on Mar 30, 2016

  • Applies to:
  • Operations Automation 5.x
  • Operations Automation 2.9


Horde webmail shows errors or a blank screen while uploading large attachments or downloading large messages. The web server error log on the webmail host contains the following errors:# tail -fn0 /var/log/httpd_error_log
Allowed memory size of 104715200 bytes exhausted (tried to allocate 67643695 bytes)
Allowed memory size of 104715200 bytes exhausted (tried to allocate 67643695 bytes)


By default, the Horde webmail configuration does not allow you to use more than 100M of memory while processing one request:# grep memory_limit /usr/local/pem/etc/apache/webmail.conf
php_admin_value memory_limit 100M
php_admin_value memory_limit 100M


Consider raising this and other related limits as shown in the following example:

/etc/php.ini:# egrep "upload_max_filesize|post_max_size" /etc/php.ini
post_max_size = 128M
upload_max_filesize = 128M

/usr/local/pem/etc/apache/webmail.conf:# grep memory_limit /usr/local/pem/etc/apache/webmail.conf
php_admin_value memory_limit 400M
php_admin_value memory_limit 400M

Note that the memory_limit parameter should be four times more than the upload_max_filesize parameter.

if LimitRequestBody is specified in the /etc/httpd/conf.d/php.conf, consider increasing it as well:# grep LimitRequestBody /etc/httpd/conf.d/php.conf
LimitRequestBody 126214400

The above configuration will allow you to upload attachments of up to 400M. If even larger files need to be processed, consider raising all the above mentioned parameters proportionally.

Once the configuration is performed, restart the web server:# /usr/local/pem/etc/apache/pemhttpd.init restart

The changes made to the configuration files might be overwritten during POA upgrades. Be ready to re-apply these changes after POA upgrades.

2554725ed606193dd9bbce21365bed4e 5356b422f65bdad1c3e9edca5d74a1ae 37e602325b9e080e0d137546b764143c 80fcf07a72a3fc2739554dff85ce8fe7 caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF