Squirrelmail issues since Security Update 2006-001

[maticks]

Has anyone else been having issues using Squirrelmail since they updated to 2006-001 security fix.
I noticed they “added security” to php4 ever since i rebooted all users are unable to use webmail.

The user can login to Squirrelmail see thier messages but if you click on a message to read it.
The Apache process hits 100% CPU time and it timesout.
Fatal error: Maximum execution time of 30 seconds exceeded in /usr/share/squirrelmail/src/read_body.php on line 98

I’ve turned all the logging on and i cant actually see Squirrelmail call the message from imap, but it seems to be able to talk to imap to fetch the mailbox index.
I’ve tried repairing the mailbox but it seems to be some fix thats has broken it.

anyway else having the same issue ?

[Paul]

Had the same issue. Found the answer in another forum. You can fix this from the command line. login as su. cd /etc/squirrelmail/config.
run to conf.pl script: ./conf.pl When the options appear choose option 4 General Options then choose 11 allow server-side sorting.
Enter yes to set the value to true. Choose Q to quit and save changes. Very simple but works.

[maticks]

have to do S before Q to save the changes, but thanks it has fixed the issue

[Anonymous]

I had the same problem since installing the Security Update 2006-001. Setting server-side sorting to true worked for my server too. Thanks

[Bill]

Had the exact same issue on my end. the fix in this thread worked for me as well. Thanks for posting the solution to this problem.

[Anonymous]

I’m an add’l admin that can confirm that this does, indeed, fix the time-out issue that my users were experiencing. Another forum suggested that a update to PHP4.2 would fix it, but more-than-likely that install would have resulted in the single parameter change necessary. This alternate solution does the trick.

[Author]

Posts