Leonid Evdokimov escribió:
Peter Saint-Andre wrote:
  
We had this problem at jabber.org but now s2s seems to work again (even
before I signed up for Google Apps, verified domain ownership, and then
disabled Google Apps services). Perhaps Google fixed some bugs?
    

As far as I know, Google fixed this issue. An acquaintance of mine
(Google employee) told me that.

  
looks like our server is having the issue again, it was fine for a whole year and today just stop working..
looks like more servers are having the problem:
http://www.google.com/support/forum/p/Talk/thread?tid=12547027e1d0db93&hl=en

 fgrep \'binaryfreedom.info/gmail.com\' /var/log/jabber/s2s.log |tail -4
Sat Feb 21 19:46:00 2009 [notice] [24] [209.85.162.129, port=55426]
received dialback authrequest for route 'binaryfreedom.info/gmail.com'
Sat Feb 21 19:48:57 2009 [notice] [24] [209.85.162.129, port=55426]
dialback for incoming route 'binaryfreedom.info/gmail.com' timed out
Sat Feb 21 19:48:59 2009 [notice] [24] [209.85.162.129, port=56412]
received dialback authrequest for route 'binaryfreedom.info/gmail.com'
Sat Feb 21 19:49:26 2009 [notice] [68] [209.85.162.129, port=56551]
received dialback authrequest for route 'binaryfreedom.info/gmail.com'


Any idea? anyone else experiencing this issues?

Thanks





Reply via email to