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
Hi Sergei,
5) googlemail.com sends a key over the same TCP connection (!):
That's called piggybacking.
=INFO REPORT 2007-09-19 20:35:32 ===
I(0.5062.0:ejabberd_s2s_in:317): GET KEY: {nes.ru,
googlemail.com,
On 9/19/07, Philipp Hancke [EMAIL PROTECTED] wrote:
Hi Sergei,
5) googlemail.com sends a key over the same TCP connection (!):
That's called piggybacking.
Then things become more complicated, and I don't know where the bug is.
Ejabberd verifies both keys, sends dialback answers, and after
On 9/19/07, Sergei Golovan [EMAIL PROTECTED] wrote:
On 9/19/07, Philipp Hancke [EMAIL PROTECTED] wrote:
Hi Sergei,
5) googlemail.com sends a key over the same TCP connection (!):
That's called piggybacking.
Then things become more complicated, and I don't know where the bug is.
Hello, Sergei!
Wed, 19 Sep 2007 23:19:58 +0400 you wrote:
SG It's very strange given that other ejabberd deployment don't have
SG problems with Google Talk S2S.
You aren't the only one who has problems with Google :) my ejabberd 1.1.4
also fails when Google tries to add someone from my
2007/9/19, Sergei Golovan [EMAIL PROTECTED]:
On 9/19/07, Sergei Golovan [EMAIL PROTECTED] wrote:
On 9/19/07, Philipp Hancke [EMAIL PROTECTED] wrote:
Hi Sergei,
5) googlemail.com sends a key over the same TCP connection (!):
That's called piggybacking.
Then things become more
On Sep 19, 2007, at 21:41, George Hazan wrote:
Hello, Sergei!
Wed, 19 Sep 2007 23:19:58 +0400 you wrote:
SG It's very strange given that other ejabberd deployment don't have
SG problems with Google Talk S2S.
You aren't the only one who has problems with Google :) my ejabberd
1.1.4 also
