Adium

Ticket #9544 (closed defect: fixed)

Opened 2 years ago

Last modified 2 years ago

set account user info - # char in login name for realm (site separation)

Reported by: lani Owned by: am
Milestone: Adium 1.2.5 Component: Service/Jabber (XMPP)
Version: Severity: normal
Keywords: Cc:
Patch Status:

Description

Hi,

We are owner of msm.muskatli.net, and we host lot of portal site width im service: warcraft.hu, portal.warcraft.hu, space game, modellsport.org, phpwt.net ... and all of the siteadmins use # character in logins for "realm name" separation when site is remote ... because the @ char is used by "jabber/xmpp protocol" for locate server ip.

Formule:

[user]#[site]@[server host]

For example:

John from regional warcraft.hu john#whu@… Rose from central portal.warcraft.hu rose#wnet@… Kate from rcauto-hu site kate#rca@… Mark from rctank-hu site mark#rct@… Mark from rchajo-hu site mark#rch@…

The original client (Gaim) work width # char fine, and the iChat accept this too on Mac computers. But our Mac+Adium users can't setup our account, because the receive error message: invalid char. (But the % char work fine, which is an system char and relay problematic char in jabber-mysql version ;] )

-Configuration-

msm.muskatli.net (Muskatli Smart Messenger) jabber: ejabberd 2.x DB: mysql remote reg: NO

--

Please look after, and allow this char in your client edition.

Thanks your help!

Reagards:

Andras

Change History

Changed 2 years ago by am

Note that the official way to escape @ is \40:  XEP-0106. Following this spec allows clients to display the JID properly (Adium doesn't support this yet).

Changed 2 years ago by evands

  • patch_status changed from Needs Changes by Author to None

Changed 2 years ago by evands

  • status changed from new to closed
  • resolution set to fixed

(In [23071]) Allow # in jabber names. Fixes #9544

Changed 2 years ago by evands

  • milestone set to Adium X 1.2.5

Changed 2 years ago by evands

(In [23072]) Merged [23071]: Allow # in jabber names. Fixes #9544

Note: See TracTickets for help on using tickets.