In a default installation, the IPC provider is “embeded” but I got this error … how can I manage it ? I tried to use memcached provider but there is an issue, on CentOS 7, with the memcached-pecl extension … The RPM is unable to validate dependancies and your code is unable to use the extension from the system.

Also, have you followed the advice in the INSTALL guide for whitelisting the Z-Push server in the zimbra DosFilter?

To be sure, set the z-push logging level to WBXML, and in the zimbra config.php, set ZIMBRA_DEBUG to true. This will output all the SOAP requests/responses to the log file. Look for any HTML errors in the zimbra respoonses.

It is also possible that your CAS integration is resulting in a HTML redirect instruction that the zimbra backend does not know how to handle.

In a default installation, the IPC provider is “embeded” but I got this error … how can I manage it ? I tried to use memcached provider but there is an issue, on CentOS 7, with the memcached-pecl extension … The RPM is unable to validate dependancies and your code is unable to use the extension from the system.

If you set up the Z-Push repository, you could just install z-push-ipc-sharedmemory package which will get the necessary dependencies for the default installation.

if you show your proxy acl, i might be able to see whats wrong.
If i look at the 2 lines manfred posted, about the IPC, the i would say, you that you whitelisted your mail server, but your user auth is before the whitelist entry.

My issue was coming from the IPC share memory. I re installed it and the IPC error has disappear but the proxy error was also present.
I push from production the z-push version 2.1.3 and it “seems” work but in reality any account false ou true is working via z-push but the synchronisation is not working with a mobile phone. The data synchro is not available.

A thing you could try also, is to disable gzip on the webserver running the z-push vhost.
That might fix the SOAP content truncated 0!=687 part
I’ve found some other things you can read, maybe it helps.

after wide troubleshooting it’s should be an issue with Transfer-Encoding: chunked . The response size doesn’t match the attended size … We have tried all way rproxy, proxy, zimbra no luck :(
Maybe a curl issue … troubleshooting again …