[SOLVED] Zimbra to Yahoo IM Connection Broken after 5.0.4

[Chewie71]

We upgraded to 5.0.4 this past weekend. Now IM won't connect to the Yahoo service for some reason. Was there a change made to IM that wasn't listed in the release notes?

I found that when I try to make a connection and it fails, the zmmailboxd.out log gets an entry that looks like this.

Response is: 0
ymsgr=AE1RzEdgiH6sX3atHtpjP_...............
partnerid=B9ZW0S_..........

Not much help there. The UI window just tells me "Connection FAILED: Incorrect username or password", but I can login from my desktop using another IM client just fine with the same username/password.

Anyone know?

Matt

[tim brennan]

Have you tried disabling and then re-enabling the Yahoo registration for the account? (Go to the IM app, click the Yahoo icon, choose logout -- then re-register)?

Have you tried to log into the affected account with one of the standard yahoo messenger clients?

[Chewie71]

Tried all that...

I think I see what's wrong. Looks like it is trying to connect to the yahoo service at yahoo.mydomain.edu....instead of trying to contact Yahoo's servers.

We didn't change anything when we upgraded, and I don't remember anyplace where this was configured. How do I tell this IM service to connect to Yahoo's servers and not try to connect to Yahoo IM service on my local domain?

Matt

[tim brennan]

the yahoo.mydomain.ext connection is correct -- that's the internal XMPP service trying to connect to the yahoo gateway (which should be hosted on your internal server).

Sounds like your server is missing the yahoo interop extension. You're using network edition? Look in /opt/zimbra/lib/ext/ and see if you have the zimbraiminterop extension (again, Network Edition only) installed.

[Chewie71]

An 'ls -l' on that directory returns this...

[root@zcs8 zimbraiminterop]# ls -l
total 1580
-r--r--r-- 1 root root 86015 Mar 21 15:21 cindy.jar
-r--r--r-- 1 root root 204536 Mar 21 15:21 jml-1.0b1.jar
-r--r--r-- 1 root root 682375 Mar 21 15:21 joscar-client.jar
-r--r--r-- 1 root root 22375 Mar 21 15:21 joscar-common.jar
-r--r--r-- 1 root root 531917 Mar 21 15:21 joscar-protocol.jar
-r--r--r-- 1 root root 64866 Mar 21 15:21 zimbraiminterop.jar
[root@zcs8 zimbraiminterop]#

Matt

[tim brennan]

Hmm. That looks correct. What are the exact error messages you're seeing in the logs?

[Chewie71]

Which logs have the info I'm looking for? The one I mentioned up in my first post didn't give me much info.

Matt

[tim brennan]

Actually I managed to track this one down. Looks like things get into a bad state if you enter an invalid password once. The client isn't unregistering the existing session (in a 'bad_auth' state) before it tries to reconnect -- and the server doesn't do the right thing at all (it should just drop the existing session and reconnect).

I've added bug 26634 to track this. The fix is checked in and will come out in 5.0.5.

Unfortunately for you, it looks like the account is going to remain stuck until you restart the server - I don't see any way to work around this from the Web Client.

If you're comfortable doing a little bit of scripting, you can manually unregister the account from interop by sending the proper SOAP request

<IMGatewayRegisterRequest service="yahoo" op="unreg" xmlns:ns0="urn:zimbraIM"/>

to the server. There's a perl script you can run, if you have the source installed somewhere:

cd <SOURCE_ROOT>/ZimbraServer/src/perl/soap
perl imGatewayRegister.pl -u USERNAME -op unreg -gw yahoo -h http(s)://YOUR_HOST -pw PASSWORD

[Chewie71]

Thanks Tim for figuring that out. We're restarting later this week, so I'll see if I can get it working after that.

Matt

[chelea]

did restarting help?