I ran into a problem similar to this early on with SquirrelMail. A friend
of mine had about 1500 mail messages in his inbox and it would break when
he would try to list the index. The large memory consumption happens as a
result of the session data file on the server. SquirrelMail is sped up by
us
Hello Paul,
> I installed squirrelmail 1.4.3a from the ports under FreeBSD 5.2.1. I
> also installed Apache 2.0.50, php 4.3.8 and cyrus-mail from the ports -
> so far so good. I configured squirrelmail before so that was no problem
> either, but as soon as I opened my inbox I saw the first problem
> Anyway; I tried SquirrelMail 1.5.1 from CVS and it seems to do its job a
> lot better! Even with 8M as memory_limit I get my inbox as I expect it to
> do. Even faster then I expected! :-) Is it advisable to use the CVS
> version already? In our case it's maybe even the only option... I checked
>
Hi,
Marc Powell wrote:
I can't help with the problem but I can provide a data point. I've
successfully used 1.4.3a with mailboxes with over 50,000 messages in
them. It's slow, relatively speaking, but it works.
Php memory_limit = 50M
That strange. You where also on apache 2?
Anyway; I tried S
> -Original Message-
> From: Paul Dekkers [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 20, 2004 8:26 AM
> To: [EMAIL PROTECTED]
> Subject: [SM-USERS] malloc-error (recursive call) with large inbox
> I assume this error is caused by two reasons: of course my in
Hi,
I installed squirrelmail 1.4.3a from the ports under FreeBSD 5.2.1. I
also installed Apache 2.0.50, php 4.3.8 and cyrus-mail from the ports -
so far so good. I configured squirrelmail before so that was no problem
either, but as soon as I opened my inbox I saw the first problems arise:
it c
