Opened 11 years ago

Last modified 10 years ago

#6077 new defect

SIMPLE: username containing '@' causes problems

Reported by: achraf Owned by: seanegan
Milestone: Patches welcome Component: SIMPLE
Version: 2.4.2 Keywords:
Cc:

Description (last modified by darkrain42)

The Contact name consedered by our sip server is our email address. When I specify my mail address as "Username" on pidging account we cann't have connection with our sip server, because mail address contain "@" and pidgin will consider "@" as a separator for contac name and server name ===> wrong contact name and wrong server. Below trace issued from debugger utility:

(11:53:03) account: Connecting to account achraf.ben-hammouda@alcatel-lucent.fr@sip.alcatel.com
(11:53:03) util: Writing file accounts.xml to directory /root/.purple
(11:53:03) util: Writing file /root/.purple/accounts.xml
(11:53:03) util: Writing file blist.xml to directory /root/.purple
(11:53:03) util: Writing file /root/.purple/blist.xml
(11:53:24) autorecon: do_signon called
(11:53:24) autorecon: calling purple_account_connect
(11:53:24) account: Connecting to account achraf.ben-hammouda@alcatel-lucent.fr@sip.alcatel.com
(11:53:24) autorecon: done calling purple_account_connect
(11:53:25) util: Writing file accounts.xml to directory /root/.purple
(11:53:25) util: Writing file /root/.purple/accounts.xml
(11:53:55) connection: Connecting. gc = 0x8a53e40
(11:53:55) dnssrv: querying SRV record for _sip._tcp.alcatel-lucent.fr@sip.alcatel.com
(11:53:55) dnssrv: found 0 SRV entries
(11:53:55) network: Listening on port: 5063
(11:53:55) network: Couldn't create UPnP mapping
(11:53:55) network: Couldn't create UPnP mapping
(11:53:55) simple: listenfd: 29
(11:53:55) simple: connecting to alcatel-lucent.fr@sip.alcatel.com port 5060
(11:53:55) dns: DNS query for 'alcatel-lucent.fr@sip.alcatel.com' queued
(11:53:55) dns: Created new DNS child 27902, there are now 1 children.
(11:53:55) dns: Successfully sent DNS request to child 27902
(11:54:00) util: Writing file accounts.xml to directory /root/.purple
(11:54:00) util: Writing file /root/.purple/accounts.xml
(11:54:06) dns: Got response for 'alcatel-lucent.fr@sip.alcatel.com'
(11:54:06) dnsquery: Error resolving alcatel-lucent.fr@sip.alcatel.com:
Name or service not known
(11:54:06) proxy: Connection attempt failed: Error resolving alcatel-lucent.fr@sip.alcatel.com:
Name or service not known
(11:54:06) account: Disconnecting account 0x8a03750
(11:54:06) connection: Disconnecting connection 0x8a53e40
(11:54:06) Gtk: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed
(11:54:06) connection: Destroying connection 0x8a53e40

Best Regards

Change History (9)

comment:1 Changed 11 years ago by datallah

  • Description modified (diff)

comment:2 Changed 11 years ago by datallah

  • Summary changed from Use address mail as contac mail to username containing '@' causes problems

comment:3 Changed 11 years ago by chemistrydioxide

This is the same as #2500 although it is about another protocol.

comment:4 Changed 11 years ago by chemistrydioxide

copied this from the mailing list:

From: Mark Doliner <*> To: Achraf Ben Hammouda <*>, *, * Subject: Re: User name as am email address Date: Thu, 12 Jun 2008 11:24:04 -0500 (18:24 CEST) Mailer: Open WebMail? 2.51 20050228

Hmm, RFC 2543 (the older SIP RFC) states in section 2 that @ is not allowed in the username. I think RFC 3261 states the same thing in in section 25.1, but it's more difficult to read.

Is it common to have an "@" in the username portion of the SIP address??

-Mark

_ Support mailing list Support@… http://pidgin.im/cgi-bin/mailman/listinfo/support

comment:5 follow-up: Changed 11 years ago by refried

I received an authorization request on my Yahoo account from someone with username with the format:

name@…

I approved, and tried to add her as well, but got an error. I forget what it was. I know it looks like a MSN account, but it was truly received via my Yahoo account.

When I try to add her through the IM window, I get the error:

(8/10/2008 12:00:26 AM) Could not add buddy name@… to group <Group> to the server list on account <MyYahooAccount?>.

I am able to receive IMs from her, but haven't seen any evidence that I am able to return them.

The Pidgin Debug Window with error level "All" doesn't seem to indicate any problems.

I dunno if I should've submitted a new ticket for this or not, but seems like a fairly major bug if a valid class of usernames is actually being misparsed.

Thanks!

comment:6 in reply to: ↑ 5 Changed 11 years ago by chemistrydioxide

You are talking about MSN and Yahoo. This ticket is about a problem with the SIP/SIMPLE protocol. You should open a new ticket for this issue.

Replying to refried:

I received an authorization request on my Yahoo account from someone with username with the format:

name@…

I approved, and tried to add her as well, but got an error. I forget what it was. I know it looks like a MSN account, but it was truly received via my Yahoo account.

When I try to add her through the IM window, I get the error:

(8/10/2008 12:00:26 AM) Could not add buddy name@… to group <Group> to the server list on account <MyYahooAccount?>.

I am able to receive IMs from her, but haven't seen any evidence that I am able to return them.

The Pidgin Debug Window with error level "All" doesn't seem to indicate any problems.

I dunno if I should've submitted a new ticket for this or not, but seems like a fairly major bug if a valid class of usernames is actually being misparsed.

Thanks!

comment:7 Changed 10 years ago by bernmeister

Does this still occur in Pidgin 2.5.8?

comment:8 Changed 10 years ago by darkrain42

  • Description modified (diff)
  • Milestone set to Patches welcome
  • Summary changed from username containing '@' causes problems to SIMPLE: username containing '@' causes problems

comment:9 Changed 10 years ago by darkrain42

Ticket #8466 has been marked as a duplicate of this ticket.

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!