Adium

Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#6505 closed defect (fixed)

Adding New Google Talk Account Does Not Populate Server Field with talk.google.com

Reported by: tgage Owned by: nobody
Milestone: Adium X 1.0.2 Component: Service/Google Talk
Version: Severity: normal
Keywords: Cc:
Patch Status:

Description

When creating a new Google Talk account Adium does not populate the Chat server field with any value. In my opinion the default behavior should be to populate this field with talk.google.com since this is almost certainly the server Google Talk users need to communicate with.

To further aggravate this problem, Adium does not report that no server has been configured in the account dialog. Rather, Adium simply appears to be connecting and reports that the user is not connected. After examining the Google Talk instruction for configuring iChat/Jabber, I was able to determine that Adium should likely have talk.google.com configured as the server. This resolved the connectivity issue after I disabled and then re-enabled the account. Simply changing the value did not immediatelly resolve the connectivity issue.

Change History (9)

comment:1 Changed 13 years ago by Tim Gage

Mac OS X 10.4.8 1.5GHz PowerBook G4 1GB RAM

comment:2 Changed 13 years ago by Evan Schoenberg

Worksforme, but not closing since it obviously doesn't work for you.

Populating the Connect Server field is not (should not) be necessary. A newly added Talk account works perfectly for me, with no connect server field specified; specifically, connect server *should not* be specified so that automatic DNS SRV lookup can occur.

What is the domain part of your Talk name?

comment:3 Changed 13 years ago by Tim Gage

fellowman.org

As this domain is not production and is being used to test the features of the new Google Apps Enterprise, I can provide to a temporary account for troubleshooting if this would be helpful.

Regards, Tim

comment:4 Changed 13 years ago by Evan Schoenberg

Oh.

Well that explains that. I guess we *do* need to include the connect server, after all; I had thought that all Talk accounts had to end in gmail.com or googlemail.com, both of which SRV-resolve to talk.google.com. Looking up "Google Apps Enterprise," I guess that's not to be the case moving forward?

comment:5 Changed 13 years ago by Tim Gage

With Google Apps Enterprise the DNS records are maintained by the Google Apps subscriber. That being said, it is possible for the subscriber to add the SRV records, but none of the Google docs say to do this so I think that most admins will not bother. Also without digging, Google makes no significant effort to let folks know that they are just another Jabber service.

FYI, Google Apps has partnered with Enom so maybe Enom could automagically add the SRV record as part of any Quick Google Apps Enterprise Setup.

That being said, I still think that adding talk.google.com would be the safe bet since I makes things work in more cases and doesn't break anything.

comment:6 Changed 13 years ago by Chris Forsythe

Hrmm, we could do this 3 ways

  • Keep things how they are. Get some documentation going on how to setup a google for domains account/google apps account
  • Make a new account type. Google Enterprise or some other name. It's still jabber/xmpp, but we're visually separating gtalk and google for domains/google apps.
  • Have this setup in the google talk account type.

comment:7 Changed 13 years ago by Evan Schoenberg

Milestone: Adium X 1.0.2

There's no harm in restoring the connect server. I don't think there's any reason to clutter the services list with "Google Enterprise".

comment:8 Changed 13 years ago by Evan Schoenberg

Resolution: fixed
Status: newclosed

(In [19082]) Revert [18731]; we now specify the Google Talk connect server and port again by default. Fixes #6505

comment:9 Changed 13 years ago by Evan Schoenberg

(In [19083]) Merged [19082], reverting [18732]: we now specify the Google Talk connect server and port again by default. Fixes #6505

Note: See TracTickets for help on using tickets.