Hi, I use OpenFire (currently verion 3.4.5) and the problems started at a point when nothing had changed for a while. I in fact upgraded the version after this occurred in an attempt to fix it. Our DNS has always been setup with srv records (its the same as our institutional domain) so I doubt thats it. TLS is also available as a s2s connection option.
I'm still mistified how a roster synchronization problem could nerf federation to an entire domain without there being a serious bug in google's implementation D Chris Johnston wrote: > Unfortunatly I don't have an answer although I have some input. > > I have not noticed an issue with the Google Service since I have > configured it properly with SSL and SRV DNS entries, although I use > ejabberD which has proven to be especially stable with s2s > connection. The most common issues seem to be related to jabbber2 and > the lower versions of that server. At least that is where I hear most > of the issues originating from. > > > Things to note in my configuration which has been awesome and stable. > > * ejabberD 2.xx SVN- updated at least once a week > > * Using PSI is the best way to interface with presence subscriptions > and authorization. > PSI is the best application, #2 is Coccinella > > * I have been denied by a Google user and then "re-send authorization" > with success to be added to their roster, honestly I have not had a > presence issue with Google, it always seems very responsive to the > logons at Gmail. > > * My server has a very low amount of connections to gmail.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "google-talk-open" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-talk-open?hl=en -~----------~----~----~----~------~----~------~--~---
