Version: 0.80.2 (using 4.3.5 (KDE 4.3.5), Gentoo) Compiler: x86_64-pc-linux-gnu-gcc OS: Linux (x86_64) release 2.6.31-gentoo-r6 When connecting to a jabber account, Kopete chooses the non-SSL port 5222 in the default settings, even though SSL is explicitely enabled in the account settings. This can easily be seen by invoking "netstat -tnp": tcp 0 0 192.168.1.10:53707 217.10.10.196:5222 ESTABLISHED 8698/kopete To force a connection over SSL, it is seems to be sufficient to check the "Override default server" checkbox and then leave the suggested default settings untouched, i.e., the server's DNS name and port 5223. With this options set, Kopete warns about self-signed certificates, and the netstat output confirmes the connection to the SSL port: tcp 0 0 192.168.1.10:45233 217.10.10.196:5223 ESTABLISHED 8698/kopete
Kopete has support for STARTTLS and use it if server has support for it. For jabber is now used only port 5222. Old port 5223 is used only for legacy SSL support. So checking port number is not enough for detecting if TLS is used or not. Dump packets (e.g. by wireshark) to check for it. Closing as invalid.