No - Horde caching is generally dealing with setup/data caching.  Most 
PHP caching solutions deal with the compliation of PHP code to 
bytecode.  So they are not the same.



Using PHP caching solutions with Horde is fine - you just have to make 
sure that any cache temp files are flushed.  Turck-mmcache is 
notoriously bad for having very screwy behavior after a PHP 
crash/restart unless all temp files are removed first.

It's a very good point!  Of course, I'm using a caching program 
(mmcache), it's significantly increasing perfomance of Horde.  I've 
turned it off, messages are readable now!  Is Horde's file system 
cache the same effective as mmcache?  For now, the total perfomance 
seems to be a bit slower.



Thanks a lot,

Ilya.

You need to turn off any PHP caching program you may have active (i.e. 
turck mmcache).  See if this fixes this.

Hi,



I've tried three versions of c-client:

1. The one which comes with Debian Woody

2. 2002a (backport from unstable)

3.The latest one, 2004a, was compiled by myself,and php was rebuilt with

'--with-imap=/usr/local/src/php/c-client/imap-2004a'

option

None worked for IMP 4.0.  IMP 3.2.6 works just fine, BTW



(I'm running both versions of Horde on the same box, they have 
different virtual sites and use different mysql databases).



Thanks,

Ilya.

This sounds like a very broken c-client version, try updating your 
c-client and recompile PHP.

All messages are shown as sources with all headers and base64 (or 
whatever) bodies.  Restarting browser, clearing cache, relogin doesn't 
help.