Package: imcom Version: doesn't support DNS SRV records (as required by XMPP) Severity: important
imcom doesn't support DNS SRV records, as is required by the XMPP RFCs, and doesn't have any other way of handling a Jabber server that runs on a different host than the primary domain host. For example, I want to run Jabber for example.com so that my users' JIDs are [EMAIL PROTECTED], but the A record of example.com is not the host that the Jabber server is running on. No problem, I add in a few DNS SRV records: _xmpp-server._tcp.example.com. IN SRV 5 0 5269 jabber.example.com. _xmpp-client._tcp.example.com. IN SRV 5 0 5222 jabber.example.com. According to the XMPP RFCs, clients must handle this, as this is a common, and in most cases, preferred setup (most sites don't want JIDs like [EMAIL PROTECTED]) Unfortunately, there is not even a workaround with imcom, as if you change the server name, it will also use that hostname as the Jabber domain when talking to the server, which of course then doesn't match and fails. This bug is important because in this common configuration, imcom does not work at all, coupled with the fact that there isn't even a good workaround. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-amd64-k8-sk98lin Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
