G

DNS SRV entries are not checked

On 0.2.0, core/xmpp.py does not respect DNS SRV entries due to the way we use client.XMPPClient from wokkel. A quick hack consisting in changing __init__ method this way: def __init__(self, host_app, profile, user_jid, password, host=None, port=5222): # client.XMPPClient.__init__(self, user_jid, password, host, port) client.XMPPClient.__init__(self, user_jid, password) self.factory.clientConnectionLost = self.connectionLost self.__connected=False self.profile = profile self.host_app = host_app self.client_initialized = defer.Deferred() self.conn_deferred = defer.Deferred() does travers DNS SRV. Maybe there is something wrong with host since in wokkel/twisted, if host is not set, then it should try DNS SRV entries.
G

Thomas Preud'homme 26/03/2013, 14:16

I also have this problem. My domain (celest.fr) doesn't have any A, AAAA, or CNAME record for itself (only for subdomains) but has a SRV record for XMPP. It works fine with gajim, psi and mcabber but SàT is unable to connect to it. However, in Primitivus, if I set the correct jid (with @celest.fr) but use the IP instead for the server parameter, it manages to connect. Best regards and long life to SàT :) Tom

G

hg source bot 25/06/2014, 14:38

Changeset b29452cab50b in sat. http://repos.goffi.org/sat/rev/b29452cab50b core, memory, plugins, stdui, frontends: look for DNS SRV records when server is not specified: - fix bug 3 - modify "Connection" params: - rename "Server" to "Force server" and "Port" to "Force port" - set the default value to empty string for both

id

3

author

Xavier Maillard

created

04/08/2011, 19:54

updated

25/06/2014, 14:41

labels
Backend
type
bug
status
closed
priority
normal
milestone
0.7
severity
normal