mm so you have a different error message: it seems to me that at least you get to reach the server: what have you done to get to that point?
a) which are your settings on the phone
b) are my listed server side settings enough?
Do you have any idea at least how to check where is it hanging: is it a server side config problem? Is it a connection problem (wrong ports/ports not reachable?)? Is it a client (telephone) setup problem?
I did not open any extra port too.
our port schemes are conceptually different but in practice similar:
1) requests on port 80 of webmail.domain.example are automatically connected by apache via mod_jk to the port where http zimbra is running and the following RewriteRule is active
RewriteRule ^/$
http://webmail.domain.example/zimbra
2) requests on port 443 of webmail.domain.example are automatically connected by apache via mod_jk to the port where https zimbra is running and the following RewriteRule is active
RewriteRule ^/$
https://webmail.domain.example/zimbra
At the beginning I was using the self generated certificate of zimbra but since the name with which we access the mail server is different from the private_name of the zimbra server (name under which the zimbra generated certificate was created) I was getting a sync error due to a certificate server name mismatch (error 0x80072f17). So I have generated with openssl a new certificate for the correct name. I have let zimbra, apache and the treo use it and I got back to the "original" error message:
0x85030022: "The server is not an exchange server or is not running a compatible software ........."
the same one that I got without SSL.
Sure I let you know if I get forward, but I am pretty much out of ideas now.