GitLab

Current xmpp.transports does two possible SRV queries, one of which is meant for s2s connections (legacy s2s connections at that). My work server answered _jabber._tcp. with the3 correct s2s port 5269, which gajim was obviously not expecting to connect with. A simple patch, for now, is to remove this query (see attachment). Another is bug is that this SRV lookup prevents custom ports from being used if one of the queries returns a result. The patch does not address this.