[Pidgin] #8500: Pidgin ignores Communigate roster answer

[Pidgin]

#8500: Pidgin ignores Communigate roster answer
--------------------------------+-------------------------------------------
 Reporter:  birnenschnitzel     |           Owner:  deryni
     Type:  defect              |          Status:  new   
Component:  XMPP                |         Version:  2.5.4 
 Keywords:  roster communigate  |   Launchpad_bug:        
--------------------------------+-------------------------------------------
 Hello,

 I'm currently testing the connection between Pidgin 2.5.4 and the
 Communigate (www.communigate.com) XMPP module. I noticed that I cannot
 update my presence state and was always wondering why my roster could not
 be retrieved during logon. In the process of debugging I found the reason
 for this:

 The initial Pidgin get roster request results in these two data streams
 between the client and the server:

 (17:39:12) jabber: Sending (ssl): <iq type='get'
 id='purpleae165ca0'><query xmlns='jabber:iq:roster'/></iq>

 (17:39:12) jabber: Recv (ssl)(348): <iq from="acme.com"
 id="purpleae165ca0" to="markus.stockhausen at acme.com/random749594AF"
 type="result"><query xmlns="jabber:iq:roster"><item
 jid="markus.weber at acme.com" name="Markus Weber"
 subscription="both"><group>Kameraden</group></item><item
 jid="mike.hildebrandt at acme.com" name="Mike Hildebrandt"
 subscription="both" /></query></iq>

 The Pidgin log shows no error about this communication but in the ongoing
 process it becomes clear that this request must have been ignored. If I
 try to change my presence state I finally get the error message:

 (17:39:25) jabber: attempt to send presence before roster retrieved

 A complex setup with an intercepting PERL proxy that modifies the servers
 packets I could prove that changing the answer from '<iq from="acme.com"
 ...' to '<iq from="markus.stockhausen at acme.com" ...'
 will bring up the roster in Pidgin.

 If I get the XMPP specification right it should not be required to
 populate the from tag in the servers answer with the requestors email
 address. Other Jabber clients like PSI know how to handle the roster
 answer correctly. I hope you can clarify if this is a defect on client
 side or on server side but as other IM tools have no problems at all I
 think it is related to Pidgins XMPP implementation.

 Attached you will find a complete log of the error.

 Best regards

-- 
Ticket URL: <http://developer.pidgin.im/ticket/8500>
Pidgin <http://pidgin.im>
Pidgin