Where did you come across this? There's a right way to do it. Other
clients don't seem to have a problem with it. It's defined by JEP-0077.
http://www.jabber.org/jeps/jep-0077.html If a client wants to know
how to register it should send this:
<iq type='get' id='reg1'>
<query xmlns='jabber:iq:register'/>
</iq>
If supported, the server will respond with precisely what fields are
required to register. If there's an old method, it's no longer in the
standards. If it comes down to it, the old method should be ignored if
that's what it takes to support the new method.
Joel
William Schulz wrote:
On Tue, Jun 07, 2005 at 10:21:39PM -0400, Joel Ebel wrote:
I'm looking into this. GAIM appears to be doing something wrong when
registering a jabber account. I'm investigating exactly what that is,
but for now, the best I can suggest is to try a different client.
From the help folks:
"yes. we can't handle xmpp registration because we don't know
how to tell if a server supports that or the older
registration"
Once registered (via another client), Gaim does allow you to log in, etc.
SWS
[EMAIL PROTECTED]
--
TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug
TriLUG Organizational FAQ : http://trilug.org/faq/
TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
TriLUG PGP Keyring : http://trilug.org/~chrish/trilug.asc
