Host details lost if manually disconnect.

majhalhouse / exodus

Automatically exported from code.google.com/p/exodus

0 stars 0 forks source link

Host details lost if manually disconnect. #3

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago

Using version 0.10.0.0 host details are overwritten with domain of jabber ID.

To replicate;

1. Create a profile, under Connection tab uncheck "Automatically discover
host and port" and enter a host that is different from the domain of jabber ID.
2. Connect successfully.
3. Disconnect manually.
4. Can no longer connect. Check profile details. Host had been overwritten
with the domain of the jabber ID.

Under 0.9.1.0 the problem did not occur.

Original issue reported on code.google.com by jason.sa...@gmail.com on 27 Nov 2007 at 1:45

GoogleCodeExporter commented 8 years ago

I'm having the same problem.  I use Exodus for work and my company has a domain 
with
Google Apps and we're using Gtalk as our jabber server.  I'm using Exodus 
0.10.0.0.
Profile settings are:
ID = myname@COMPANY.net  (where COMPANY.net is our own Google App domain)
Host = talk.google.com on port 5222
Resource = Exodus

I can connect to Gtalk just fine.  But if I disconnect, I cannot reconnect.
Looking at my profile after disconnecting I see some settings have been changed:
Host is now COMPANY.net
Resource is now ExodusB940E033 (or something like that)

I have to manually change the host before I can reconnect.

Original comment by doug%dwv...@gtempaccount.com on 10 Mar 2008 at 3:12

GoogleCodeExporter commented 8 years ago

It happens on my computer too! Please fix this. Otherwise a nice product. 
THakns.

Original comment by youngber...@gmail.com on 17 Mar 2008 at 10:02

GoogleCodeExporter commented 8 years ago

This occurs all the time, please increase priority, annoyance for users.

Original comment by kevincha...@gmail.com on 26 Mar 2008 at 1:29

GoogleCodeExporter commented 8 years ago

I also suffer from this although you don't need to manually disconect, 
hibernating
your PC is enough for the host to be overwritten.
This didn't happen in the prior version, I upgraded and now I have this bug.
Version 0.10.0.0
Thanks.

Original comment by matias.g...@gmail.com on 16 Sep 2008 at 1:34

GoogleCodeExporter commented 8 years ago

Nothing has changed since Nov 27, 2007?!
Fix it after all!
Version 0.10.0.0

Original comment by dime...@gmail.com on 23 Dec 2008 at 7:14

GoogleCodeExporter commented 8 years ago

I had this same issue and fixed it by adding SRV DNS records for the XMPP 
server.
Apparently the client is looking for the SRV record response and rewrites the 
server
based upon the response.

_xmpp-client._tcp 3600 IN SRV 10 0 5222 xmpp.example.com.
_xmpp-client._udp 3600 IN SRV 10 0 5222 xmpp.example.com.
_jabber-client._tcp 3600 IN SRV 10 0 5222 xmpp.example.com.
_jabber-client._udp 3600 IN SRV 10 0 5222 xmpp.example.com.

If you do a Google search for SRV record XMPP, you will find multiple responses
because this is a common problem with SIP also.

Original comment by grypho...@gmail.com on 13 Jan 2009 at 1:34

GoogleCodeExporter commented 8 years ago

Same problem here.. connecting, disconnecting...

Original comment by ng4rrjan...@rediffmail.com on 6 Feb 2009 at 5:59

GoogleCodeExporter commented 8 years ago

Same problem. Seems like the project developers are dead, they are all dead...

No change since 2007 - almost 3 years. The project is discontinued, but still
pretends to be alive... Exodus was a good messenger, one of the best in my 
opinion. 

Rest in peace!

Original comment by DKomarov...@gmail.com on 27 Jan 2010 at 9:23