Did google finally kill off s2s federation?

Since around 6pm EDT last night, I've been receiving "invalid dialback key" errors from gmail.com. Yeah, I know I'm not supposed to federate with them, but it's easiest to explain to my mother and others.

Nothing had changed on my side - the server had been running for 4 days uptime and had successfully federated with them many many times before (since around 2007 or so).

I'm wondering if google has finally terminated it's vestigial ties to XMPP, and if anyone might know anything about this.

Thanks

Yes, I read https://www.ejabberd.im/invalid-dialback-key. Even though I had never set this prior to today, it had not affected anything in 9 years since the domain was the server as well. I set it today, and 8.8.8.8 is showing it, but it has made no difference.

2016-09-01 09:53:49.285 [info] <0.564.0>@ejabberd_s2s_out:log_s2s_out:1253 Trying to open s2s connection: myrealdomain.xxx -> gmail.com with TLS=true
2016-09-01 09:53:49.285 [debug] <0.564.0>@ejabberd_s2s_out:open_socket:214 open_socket: {<<"myrealdomain.xxx">>,<<"gmail.com">>,true,false}
2016-09-01 09:53:49.286 [debug] <0.564.0>@ejabberd_s2s_out:get_addr_port:1099 srv lookup of 'gmail.com': [{20,0,5269,"alt2.xmpp-server.l.google.com"},{20,0,5269,"alt4.xmpp-server.l.google.com"},{20,0,5269,"alt3.xmpp-server.l.google.com"},{5,0,5269,"xmpp-server.l.google.com"},{20,0,5269,"alt1.xmpp-server.l.google.com"}]
2016-09-01 09:53:49.286 [debug] <0.564.0>@ejabberd_s2s_out:get_addr_port:1119 srv lookup of 'gmail.com': [{<<"xmpp-server.l.google.com">>,5269},{<<"alt2.xmpp-server.l.google.com">>,5269},{<<"alt4.xmpp-server.l.google.com">>,5269},{<<"alt3.xmpp-server.l.google.com">>,5269},{<<"alt1.xmpp-server.l.google.com">>,5269}]
2016-09-01 09:53:49.287 [debug] <0.564.0>@ejabberd_s2s_out:get_addrs:1184 inet of xmpp-server.l.google.com resolved to: [{64,233,183,125}]
2016-09-01 09:53:49.287 [debug] <0.564.0>@ejabberd_s2s_out:open_socket2:293 s2s_out: connecting to {64,233,183,125}:5269
2016-09-01 09:53:49.424 [debug] <0.564.0>@ejabberd_s2s_out:wait_for_validation:395 recv result: {<<"gmail.com">>,<<"myrealdomain.xxx">>,<<>>,<<"invalid">>}
2016-09-01 09:53:49.424 [info] <0.564.0>@ejabberd_s2s_out:wait_for_validation:418 Closing s2s connection: myrealdomain.xxx -> gmail.com (invalid dialback key)
2016-09-01 09:53:49.424 [debug] <0.564.0>@ejabberd_s2s_out:terminate:961 terminated: {normal,wait_for_validation}

In the ejabberd, jabber-oper

In the ejabberd, jabber-oper and jabber-dev mailing lists there is no mention to this problem. And there aren't relevant results searching in google.com for: gmail.com jabber s2s, in last week.

Syndicate content