[EMAIL PROTECTED] didn't work with our 
server/transport implementation (jabberd 1.4.2/aimt-t/or pyaim-t).

I also tried username&#64;[EMAIL PROTECTED]<http://transport.company.com>
.

Some sort of escaping does seem to be a reasonable solution though.

Thanks,

-Paul

On 4/28/05, Alexey Nezhdanov <[EMAIL PROTECTED]> wrote:
> 
> В сообщении от Четверг 28 Апрель 2005 20:25 Paul Clegg написал(a):
> > We recently discovered a class of AIM users who have an "@" symbol in 
> their
> > buddy name (e.g. [EMAIL PROTECTED]). Neither aim-t or pyaim-t
> > handle this case (the buddy is translated to the jid
> > [EMAIL PROTECTED]@ transport.server.com<http://transport.server.com>
> > <http://transport.server.com>, which is clearly not a legal jid).
> >
> > Can anyone recommend the correct way to resolve xmpp-illegal characters
> > encountered in external protocols at the transport level, so that the
> > contact can be properly assigned a jid, messaged, stored in the roster,
> > etc.?
> May be do an urlescape over it? I.e. replace "@" with "%40" etc... ?
> >
> > I imagine that the MSN-t folks have dealt with this issue already and 
> may
> > have some suggestions for us.
> >
> > Thanks,
> >
> > Paul
> > _______________________________________________
> > jdev mailing list
> > [email protected]
> > http://mail.jabber.org/mailman/listinfo/jdev
> 
> --
> Respectfully
> Alexey Nezhdanov
> 
>
_______________________________________________
jdev mailing list
[email protected]
http://mail.jabber.org/mailman/listinfo/jdev

Reply via email to