I am playing with my local Zimbra installation (ZD 1.0.4 over Linux) by sending it some test SOAP messages from a custom Java application and I can convince the service to authenticate.
More specifically, I post the following SOAP message through a Java OutputStremWriter (variable w):
w.write(" <AuthRequest xmlns=\"urn:zimbraAccount\">\r\n");
w.write(" <account by=\"name">MyAccName@gmail.com</account>\r\n");
where MyAccName@gmail.com is an existing GMail address, the inbox of which I access via ZD (or via any browser), using MyPassword. ZD synchronizes with MyAccName flawlessly.
However, whenever I post the above SOAP message, I get the following response:
<soap:Text>invalid password: MyPassword</soap:Text>
<Error xmlns="urn:zimbra"> .......
As I said above, MyPassword works fine with both GMail and ZD. The documentation (soap.txt) says that account.INVALID_PASSWORD means "new password doesn't meet the system's rules", but how can this be possible, since it works already and I am not trying to create a new password anyway?