[ejabberd] about fallback
mk-ejabberd at spline.de
Tue Dec 6 14:15:10 MSK 2011
On 27.04.2011 03:51, sergio wrote:
> On 04/27/2011 05:41 AM, Evgeniy Khramtsov wrote:
>> Probably, there is a problem with gmail server software, no?
> Yes! But how to verify this?
> For example there was a similar problem with jabberd14. The solution was
> to add _jabber srv record. (As I understand jabberd14 doesn't look at
> _xmpp-server, but on _jabber)
> Looks like google even doesn't try to communicate with slave.
Are there any updates on the topic?
We are currently observing the same problem over here.
I(<0.475.0>:ejabberd_s2s_out:353) : Closing s2s connection: our-domain
-> gmail.com (invalid dialback key)
I(<0.1469.0>:ejabberd_s2s_out:417) : wait for validation: our-domain ->
This is our dns setup (master is down)
_xmpp-client._tcp.jabber IN SRV 11 0 5222 slave
_xmpp-client._tcp.jabber IN SRV 5 0 5222 master
_xmpp-server._tcp.jabber IN SRV 11 0 5269 slave
_xmpp-server._tcp.jabber IN SRV 5 0 5269 master
; legacy support
_jabber._tcp.jabber IN SRV 11 0 5269 slave
_jabber._tcp.jabber IN SRV 5 0 5269 master
Is there anything wrong? Anything weird that google might choke on?
More information about the ejabberd