sendxmpp error

[buliwyf]

Binary package hint: sendxmpp

Description: Ubuntu 8.04.1
Release: 8.04

sendxmpp:
  Installed: 1.13-1
  Candidate: 1.13-1

After upgrading vom gutsy to hardy
sendxmpp quits with the following error message.

Could not connect to server 'jabber.ccc.de': IO::Socket::INET: Cannot determine remote port

Error could be verified on another ubuntu hardy server.

With gutsy the setup worked for month flawlessly

[buliwyf (dominik-sennfelder)]

btw, the problem also occurs with diffrent servers. e.g. swissjabber.ch

[Brock Colby (levsky)]

Hi!

I had the same error and solved it.
Try adding the port number of your jabber server to your '.sendxmpprc', for example:

<email address hidden>:5222 secret

[Iain Lane (laney)]

Hi,

Can you test this with the new version in Intrepid when it's released and see if the problem is still there?

Thanks.

[Brock Colby (levsky)]

Hello again!

The Problem seems to be solved in Intrepid.
I am able to send a message via sendxmpp without having added a port in my configuration file.

Brock

[Arnold Daniels (info-adaniels)]

A second bug with this version of sendxmpp.

Using "<email address hidden>;foo.com secret" or "<email address hidden>;foo.com:5222 secret" in .sendxmpprc results in:
   syntax error in line 1 of /root/.sendxmpprc

Both issues are solved by using sendxmpp version 1.14-1 (backported from intriped). May I suggest updating the hardy to version 1.14.

[Arnold Daniels (info-adaniels)]

Backported sendxmpp 1.14-1 from intriped to see if this would solve the problem and is not caused by libnet-xmpp-perl (or another package). With version 1.14 both issues are solved.

[Iain Lane (laney)]

Thanks for checking. I'll see if we can get this patched in hardy-updates.

[Arnold Daniels (info-adaniels)]

There is actually a second bug. When you specify a host which is different than the server part of the JID (using a ;), the username is set to user@server. The server (ejabberd 2.0.1-2~hardy1) does not accept this as it tried to authenticate user@server@host. Instead 'to' should be used which can be set using the 'component' key when connecting. Using the component option is still different though, since that's also added to each recipient when sending a message.

[Benjamin E. Zeller (bez)]

Seems not to be solved yet... Any ETA?