W
winddancer
Guest
Hi all,
I think this issue has been discussed here and on several of the other forums in one form or the other.
However I still want to point out that this is a serious problem for people using horde webmail as a working environment.
I raised the PHP upload and post limit to 20 MB to allow emails with attachments of this size via horde.
However as soon as I try to send 6MB or more, PHP tries to allocate enormous ammounts of memory. I even set the memory limit of php to 128 MB (which I have to reduce later on anyway).
I only get this error msg in the apache error log.
I had a look at the stated line. And there's some form of search & replace with new lines. I didn't investigate it further ('cause it's part of the pear package), but it may very well be that this search is also done on the attachments. However I still don't get why search and replace on a 12 MB Attachement would require more then 128 MB memory limit!!!
@SWSOFT I really would like to see this fixed or at least get some kind of hotfix for this!!!
btw. I only have this problem on all of my new plesk 8.1 hosts. 2 7.5 Plesk servers run pretty fine with 64 MB Limit and up to 20 MB attachment size!
Kind regards
Sven
I think this issue has been discussed here and on several of the other forums in one form or the other.
However I still want to point out that this is a serious problem for people using horde webmail as a working environment.
I raised the PHP upload and post limit to 20 MB to allow emails with attachments of this size via horde.
However as soon as I try to send 6MB or more, PHP tries to allocate enormous ammounts of memory. I even set the memory limit of php to 128 MB (which I have to reduce later on anyway).
I only get this error msg in the apache error log.
PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 35944245 bytes) in /usr/share/psa-horde/pear/Net/SMTP.php on line 759,
I had a look at the stated line. And there's some form of search & replace with new lines. I didn't investigate it further ('cause it's part of the pear package), but it may very well be that this search is also done on the attachments. However I still don't get why search and replace on a 12 MB Attachement would require more then 128 MB memory limit!!!
@SWSOFT I really would like to see this fixed or at least get some kind of hotfix for this!!!
btw. I only have this problem on all of my new plesk 8.1 hosts. 2 7.5 Plesk servers run pretty fine with 64 MB Limit and up to 20 MB attachment size!
Kind regards
Sven