I have found the same problem in ZCS GA 6.0.10. I have some ideas but I am not sure if they will be smart enough:
Originally Posted by switch007
2) Use </session> somewhere in the zmsoap command as it suggest me from reading the documentation at /opt/zimbra/docs/soap.txt. Unfortunately it is not evident on how to force zmsoap to associate a session to itself.
3) Try to hack the internal openfire? that has zimbra inside?
The server's default is disabling sessions for every SOAP request.
Clients that desire notification must explicitly request that the server
maintain a session for them. This is done by specifying a <session/>
element in the request
4) Try to commit custom database queries to whatever Zimbra internal database uses.
So if you could give any hint on any of these I will appreciate. Thank you for your attention.