Jabber: client's messages don't reach the recipients
 

Hi guys.

The next problem I faced is that the Jabber-client sends messages but the recipients do not receive them.

The server is Openfire 3.7.0. And our users use it without any problems.
One user has Kubuntu 10.10. Pidgin 1:2.7.3-1ubuntu3.2. The connection passes well. The contact list loads well. The incoming messages are received well.
But the messages which are sent to others - do not reach them.

His Jabber-client is configured as others'. I tried Pidgin 1:2.7.3-1ubuntu3.2 (which is used in our company) and Gajim 0.13.4-1ubuntu1 .

What can it be? And what should I do?
I compared the openssl version on my computer and on problem computer. I have 0.9.8o-1ubuntu4.4. He had just 4. I upgraded his system. Now he has also 4.4. But the problem is still with us.

Excuse me for my English :) and.. in fact, I have no ideas what to do.
Best regards, Alexey.

This is weird: taking in account you tried multiple clients... You can also give Psi a try, but I'd suggest you inspect network traffic (wireshark, tcpdump).
Who are the recipients? Are they on local or remote server? Are you sure other accounts can communicate with those recipients?

Web31337, thank you for the respond!

Everybody is connected to the same xmpp-server. And only that client seems to be unlucky. Other users communicate well between each other. And only messages from that user don't reach the others.

Can the problem be in SSL ? In some libraries? After setting the connection for the first time, the xmpp-client (of the problem user) receives the certificate of the server, so everything seems to be OK. Only the messages from him don't reach the others.

I'll try to see something with tcpdump when the user will power his PC on (hi's in the other city and other timezone).

Try registering him a test account(in order not to send real password open over internet) and connect without SSL in order to debug this with tcpdump.

The problem was in MTU. The link to the Cisco-router is PPPoE. And everything became OK after setting the MTU on the PC interface to 1400.
:-)