[imp] Big attachment problem

[Tim Meader]

Not evangelizing, but fyi for a lot of these people that are having users 
trying to upload gigantic files... you might do well to investigate the 
usage of mod_perl with the libapreq module. It provides a very simple, perl 
based obviously, api for uploading files (among other things). The big plus 
is that it DOES spool uploads to disk and does not keep them in RAM as PHP 
tends to. I've noticed several front ends on various code repositories  on 
the net that could be paired with mod_perl, and have a system I wrote 
myself that I would be glad to give to others (as is) if they are 
interested (only condition being that if they improve it at all they let me 
know <wink> ).

Love IMP and Horde though, unrivaled for quality as far as IMAP based web 
front-ends go. Anxiously awaiting IMP 3.2 so I can finally move to PHP 4.3, 
and Horde 2.2.1 hopefully without incident.

Later.

At 04:56 PM 2/6/2003 -0600, Eric Rostetter wrote:
>Quoting Myke Place <mp at xmission.com>:
>
> > Fatal error: Allowed memory size of 20971520 bytes exhausted (tried to
> > allocate 7006319 bytes) in
> > /var/www/horde/lib/MIME/Part.php on line 195
> >
> > Fatal error: Allowed memory size of 20971520 bytes exhausted (tried to
> > allocate 140 bytes) in
> > Unknown on line 0
>
>I've seen issues like this when I was using PHP 4.1.2 installations.
>I believe, but can not prove, it is a bug in some 4.1.2 installations.
>I can not remember if the problem was in RedHat's RPMS, or the RPMS from
>rpms.arvin.dk, or both.
>
>Basically, I had a machine which people upload files to (not Horde related).
>They often upload up to about 100 MB files.  I had set the limit to be
>about 100MB, and it worked fine with php 4.0.6.  Well, when the security
>notes about 4.0.6 came out, I upgraded to 4.1.2, and I ran into a problem
>like above.  So I ended up having to set memory to about 250 MB to get a
>100MB file to upload.  Not sure why, etc.  But I do note that the machine
>only had 128 MB of memory, and I had no issues with setting the php memory
>limit higher than physical memory, and I didn't notice any obvious swapping.
>Well, when I upgraded to another php (probably 4.2, but not sure) I was able
>to lower the memory setting back down to 100MB and still upload files.
>
>So the moral is: There *may* be a bug in some php 4.1.2 versions out there.
>Then again, my case could have been isolated.
>
>--
>Eric Rostetter
>The Department of Physics
>The University of Texas at Austin
>
>Why get even? Get odd!
>
>--
>IMP mailing list
>Frequently Asked Questions: http://horde.org/faq/
>To unsubscribe, mail: imp-unsubscribe at lists.horde.org

---
Tim Meader
ODIN Unix Group
ACS Government Services, Inc. - (301) 286-8013
tmeader at cne-odin.gsfc.nasa.gov