Tue, 08 Jul 2008 22:50:53 -0400 http://bugs.horde.org/ticket/6676 Large attachments Occasionally my users get send large attachments which don't download because the php process exceeds the php max memory. Is there a chance that the file could be saved locally so the user can download the file via normal http i.e. not via a php program. I could increase the php max memory, but that option is there for my "general" protection and shouldn't really be used for these types of things. Fri, 02 May 2008 07:11:32 -0400 http://bugs.horde.org/ticket/6676#t45099 Can you be more specific about where memory is exhausted? We could save the data to a file, but without stream support in the imap module, we're just as likely to run out of memory fetching the data to put in that file as we are serving it back to the user. Fri, 02 May 2008 11:27:57 -0400 http://bugs.horde.org/ticket/6676#t45108 It is exploding at: $Horde: imp/lib/MIME/Contents.php,v 1.153.4.45 2007/08/07 19:53:40 slusarz Exp $ /usr/share/psa-horde/imp/lib/MIME/Contents.php 173 The error is: [client xxx.xxx.xxx.xxx] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 9962983 bytes) in /usr/share/psa-horde/imp/lib/MIME/Contents.php on line 173 Allowed memory size of 33554432 bytes exhausted (tried to allocate 0 bytes) I think you (the royal you) are reading all the mime attachments into memory. The attachment was 9MB so given: $this->_bodypart[$id] = str_replace("\r\n", "\n", $this->_bodypart[$id]); You need 18MB of storage not including any other copies which may be in scope, or other attachments. Fri, 02 May 2008 12:48:26 -0400 http://bugs.horde.org/ticket/6676#t45113 K, well, that won't be helped by saving the data to a file. Michael S., wasn't this improved recently? Fri, 02 May 2008 13:01:55 -0400 http://bugs.horde.org/ticket/6676#t45116 Duplicate of Ticket 4753. Fri, 02 May 2008 13:07:20 -0400 http://bugs.horde.org/ticket/6676#t45117