Even starting Kopete from the command line, and observing the messages reported didn't help me at all, but I was sure that the account was working, since I was able to log-in with another Jabber client (e.g. PSI).
At last I found an hint in the OpenFire server logs, in particular in the Warn section of the logs: the Kopete client was sending to the server a wrong/bad server name, and thus the server was refusing the connection. For example, if the server is called myserver.mydomain.com and the Kopete client is configured to connect to myserver, it will not work. It does not matter if you manually specify the server ip address, either overriding the name of the server in the Jabber ID or placing it directly in such ID, the server will refuse the connection. In my case, for instance, I was trying to log-in with the Jabber ID:
luca.ferrari@myserverand my computer could resolv myserver (i.e., it is not a DNS problem). Once I substituted the Jabber ID with the following:
firstname.lastname@example.orgI was able again to connect to the server. In conclusion, Kopete requires you to specify the same server string that you put in the OpenFire server configuration, or the server will refuse the client to connect to the server.