I think the PHP5 fix for #459020 has fixed this squirrelmail-decode problem as well.

I've confirmed this with a mail which uses big5 encoding and which would trigger the problem with the previous version of PHP5 in Etch. With the latest php5 security update for Etch (version 5.2.0-8+etch11) the mail opens fine, whereas previously the memory usage for the php- cgi process would grow until the OOM killer kicked in.

--
        Bart



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to