They're working on it. From my (private) bug posting on bugzilla (#62722), Zimbra staff wrote:
This currently occurs for some accounts and not others. Probably Yahoo is in
the process of rolling out changes which make this stop working.
It looks like we have always included Zimbra context header in our SOAP
requests to Yahoo, but recently started it failing at the Yahoo server.
Removing context header in SoapTransport.java allows Yahoo SOAP requests to
work on all accounts. We'll have to expose header creation so it can be
overridden in a subclass.
fails:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header>
<context xmlns="urn:zimbra">
<nosession/>
<userAgent name="Zimbra Desktop" version="7.1.2_10930_Mac"/>
</context>
</soap:Header>
<soap:Body>
<GetUserData xmlns="urn:yahoo:ymws"/>
</soap:Body>
</soap:Envelope>
works:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<GetUserData xmlns="urn:yahoo:ymws"/>
</soap:Body>
</soap:Envelope> |