Hi!
Last few weeks I'm experiencing a loss of connectivity with gmail.com
and googlemail.com. It's interesting that my messages (from nes.ru to
gmail.com) rich recipients just fine, but messages from gmail.com
can't be delivered (users get error messages).
After switching off STARTTLS over S2S (which hides the problem) I got
the following ejabberd log (it's a typical scenario):
1) Google server connects to nes.ru:
=INFO REPORT==== 2007-09-19 20:35:31 ===
I(<0.241.0>:ejabberd_listener:90): (#Port<0.6781>) Accepted connection
{{72,14,252,129},30195} -> {{212,119,199,80},5269}
(Note #Port<0.6781>. It's an Erlang port, which processes the TCP connection.)
2) ejabberd opens an incoming S2S stream:
=INFO REPORT==== 2007-09-19 20:35:31 ===
I(<0.5062.0>:ejabberd_s2s_in:105): started: {gen_tcp,#Port<0.6781>}
Now the stream is controlled by Erlang process <0.5062.0>.
3) gmail.com sends a key
=INFO REPORT==== 2007-09-19 20:35:32 ===
I(<0.5062.0>:ejabberd_s2s_in:317): GET KEY: {"nes.ru",
"gmail.com",
[],
"CAESBxC07cjz0SIaEEWGpREmNkivSJRYciOVI70="}
Note port number <0.5062.0>.
4) nes.ru opens outgoing S2S stream to verify the key (it's irrelevant here)
5) googlemail.com sends a key over the same TCP connection (!):
=INFO REPORT==== 2007-09-19 20:35:32 ===
I(<0.5062.0>:ejabberd_s2s_in:317): GET KEY: {"nes.ru",
"googlemail.com",
[],
"CAESBxC17cjz0SIaEBnkylXoIZMlEI4Y4qYXHDQ="}
The port is the same <0.5062.0>. After that the connection is stalled.
ejabberd never receives anything in this stream.
For me it looks like a severe bug in Google Talk server.
Did someone experienced similar problems with gmail.com and
googlemail.com? May be Google Talk admins read this list and can help?
Cheers!
--
Sergei Golovan
