Communigate XMPP

[birnenschnitzel at volloeko.de]

Hello,

I'm testing connectivity between Pidgin and Communigate XMPP server and I came around a very confusing problem when adding buddies. The steps are:

1. Add a buddie in Pidgin and send authorization request.
2. In the Communigate Pronto web interface (more or less a Flash based XMPP web client) of the buddy the request appears and he can confirm authorization. 
3. This triggers a request back to Pidgin and there I have the possibility to authenticate the user in my buddy list. But this will try to add the same user to the buddy list once again. Finally I have two users with the same name. One is online and the other ist waiting for authentication. 

Last but not least, the other user will never see me online, when I'm connected with pidgin.

Here are the XMPP logs (R = traffic from server to client, S = traffic from client to server):

Pidgin subscribe request

S [<presence to='postmaster at acme.com' type='subscribe'/>]
R [<iq type="set"><query xmlns="jabber:iq:roster"><item ask="subscribe" jid="postmaster at acme.com" subscription="none" /></query></iq>]
S [<iq xmlns='jabber:client' type='error' id='purple689c6041'><query xmlns='jabber:iq:roster'><item ask='subscribe' jid='postmaster at acme.com' subscription='none'/></query><error type='modify'><bad-request xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error></iq>]
R [<iq from="acme.com" id="purple689c6041" to="markus.stockhausen at acme.com/randomFC93AA47" type="error"><query xmlns="jabber:iq:roster"><item ask="subscribe" jid="postmaster at acme.com" subscription="none" /></query><error type="cancel"><not-allowed xmlns="urn:ietf:params:xml:ns:xmpp-stanzas" /></error></iq>]

Communigate Authenticate message

R [<presence from="postmaster at acme.com" type="subscribe" />]
R [<iq type="set"><query xmlns="jabber:iq:roster"><item jid="postmaster at acme.com" name="postmaster" subscription="to" /></query></iq>]
R [<presence from="postmaster at acme.com" type="subscribed" />]
R [<presence from="postmaster at acme.com" />]
S [<iq xmlns='jabber:client' type='error' id='purple689c6042'><query xmlns='jabber:iq:roster'><item jid='postmaster at acme.com' name='postmaster' subscription='to'/></query><error type='modify'><bad-request xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error></iq>]
R [<iq from="acme.com" id="purple689c6042" to="markus.stockhausen at acme.com/randomFC93AA47" type="error"><query xmlns="jabber:iq:roster"><item jid="postmaster at acme.com" name="postmaster" subscription="to" /></query><error type="cancel"><not-allowed xmlns="urn:ietf:params:xml:ns:xmpp-stanzas" /></error></iq>]

Any ideas, what is going wrong there. Everything works like a charm, when using PSI as Jabber client. But it lacks multi-protocol features.

Best regards.
-- 
Jetzt 1 Monat kostenlos! GMX FreeDSL - Telefonanschluss + DSL 
für nur 17,95 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a