Well, the transports and the clients need to support iq:gateway, which will properly generate the appropriate jabberid for that transport.
So temas, does aim-t do iq:gateway yet? :) On Mon, 2002-04-15 at 12:22, Thomas Muldowney wrote: > Generally this should be encoded as [EMAIL PROTECTED] Just like > it's done to use msn-t with passport accounts. > > --temas > > > On Mon, 2002-04-15 at 06:24, Ashvil wrote: > > Is there a reason why some clients like JabberIM 1.10 and WinJab 1.1 do not allow >you to use an email address as a user name like '[EMAIL PROTECTED]'. They don't seem to >like the '@'. > > > > IMHO, if the user enters > > UserName : [EMAIL PROTECTED] > > Server : im.xyz.com > > > > Then it should connect to the server at im.xyz.com and send the JID as [EMAIL PROTECTED] > > And if the username does not contain a '@' character, then append the server name >to generate the JID. > > > > This way, I can run the server on a sub domain (maybe outsourced to a different >ISP) and still have my JID with my main domain name. > > > > Can someone enlighten me on this issue. > > > > Regards, > > Ashvil > > > > PS - WinJab 0.9.5.7 used to do this the way, I suggested > > > > _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
