1. Bug 711 deals with an entirely different issue.  And I still 
believe that PHP is partially responsible for the strange behavior in 
that bug (i.e. PHP would randomly segfault given the same input) - 
although, admittedly, there were some issues with our code.



2. Most likely, there is a message in the INBOX with some kind of 
quirky header that is crashing c-client.  This has come up numerous 
times in the past and, as Chuck correctly points out, the solution is 
to upgrade c-client and recompile.  If this doesn't work, you should 
track down what specific message is causing the problem and then 
inform the c-client people (or possibly the PHP c-client people) so 
that they can fix it.

Well, two comments on that:



- bug 711 seems to suggest that Horde sometimes isn't that innocent.



- I've used the CVS IMP code for months without any problems. Then I 
did a cvs update and "bang". I didn't change *anything* else. Neither 
Apache nor PHP. Or anything else on the system but the Horde PHP code 
itself.



Of course, it's not directly PHP code that segfaults since that's 
technically impossible but it seems some changed Horde code is 
*triggering* something in PHP. You can say "Not my (seg)fault." but I 
can imagine more constructive approaches...

segfaults are never horde bugs. recompile php and c-client.

Using the latest code, PHP segfaults when an IMP inbox gets opened.



Interestingly, the number of mails in the inbox and its sub-folders 
are displayed correctly. The segfault only happens when trying to open 
it.