Indeed, it works now, although there was no update of gajim. There is also no difference in the server replies.
gajim just initiates starttls now instead of throwing an error:
<!-- Out --> <?xml version='1.0'?> <stream:stream xmlns="jabber:client" to="gmail.com" version="1.0" xmlns:stream="http://etherx.jabber.org/streams" xml:lang="en" >
<!-- In --> <stream:stream from="gmail.com" id="99A425FE4FF99C8B" version="1.0" xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client"> <stream:features> <starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"> <required/> </starttls> <mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl"> <mechanism>X-GOOGLE-TOKEN</mechanism> <mechanism>X-OAUTH2</mechanism> </mechanisms> </stream:features>
<!-- Out --> <starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>
Indeed, it works now, although there was no update of gajim. There is also no difference in the server replies.
gajim just initiates starttls now instead of throwing an error:
<!-- Out --> client" to="gmail.com" version="1.0" xmlns:stream="http:// etherx. jabber. org/streams" xml:lang="en" >
<?xml version='1.0'?>
<stream:stream xmlns="jabber:
<!-- In --> 99C8B" version="1.0" xmlns:stream="http:// etherx. jabber. org/streams" xmlns="jabber: client"> urn:ietf: params: xml:ns: xmpp-tls" > urn:ietf: params: xml:ns: xmpp-sasl" > X-GOOGLE- TOKEN</ mechanism> X-OAUTH2< /mechanism>
<stream:stream from="gmail.com" id="99A425FE4FF
<stream:features>
<starttls xmlns="
<required/>
</starttls>
<mechanisms xmlns="
<mechanism>
<mechanism>
</mechanisms>
</stream:features>
<!-- Out --> urn:ietf: params: xml:ns: xmpp-tls" />
<starttls xmlns="