Subject: Re: PyMSNt sends error without namespace - msg#00227

Previous Message by Date: click to view message preview

Re: Anybody seen this on pyMSNt?

On 24/03/2006, at 12:07 AM, Pedro Melo wrote: Hi, I just noticed today this stanzas: <presence to='some_jid@xxxxxxx' from='tel:+15559191@xxxxxxxxxxxxxx' type='subscribe'><x xmlns='http://jabber.org/protocol/roster-subsync'><item subscription='from'/></x></presence> (jid and phone number changed to protect the innocent). This tel: jid is invalid AFAIK, but seems to be related to the SMS gateway of MSN, right? Or is this something different that I don't know about (most likely)? Thanks, -- HIId: Pedro Melo SMTP: melo@xxxxxxxxxx XMPP: pedro.melo@xxxxxxx Never seen it before :) I will have to look into that. Thanks. --- James

Next Message by Date: click to view message preview

Re: webreg 0.5 preview

On 3/30/06, James Bunton <james@xxxxxxxxxxxx> wrote: > Does the Python Yahoo transport publish itself in service discovery? yep > Do a disco#info with Psi, and look at the XML console. What differences > are there between the MSN & Yahoo transports? > <iq from="yahoo.jabber.server" type="result" id="ad40a" to="me@xxxxxxxxxxxxx/Work" > <query xmlns="http://jabber.org/protocol/disco#info"> <identity category="gateway" type="yahoo" name="XMPPPY Yahoo! Transport (Dev)" /> <feature var="jabber:iq:register" /> <feature var="jabber:iq:version" /> </query> </iq> <iq from="msn.jabber.server" type="result" to="me@xxxxxxxxxxxxx/Work" id="ad3fa" > <query xmlns="http://jabber.org/protocol/disco#info"> <identity category="gateway" type="msn" name="MSN Transport" /> <identity category="conference" type="text" name="MSN Transport Chatrooms" /> <feature var="http://jabber.org/protocol/disco" /> <feature var="jabber:x:conference" /> <feature var="jabber:iq:conference" /> <feature var="jabber:iq:register" /> <feature var="jabber:iq:gateway" /> <feature var="jabber:iq:version" /> <feature var="http://jabber.org/protocol/commands" /> <feature var="vcard-temp" /> </query> </iq> Looks like jabber:iq:gateway is missing on the yahoo transport, but that is used to indicate implemenetation of the send "legacy username to the gateway and receive a properly-formatted JID in return" process, which is not supposed atm. What's required to make the webreg work? -- - Norman Rasmussen - Email: norman@xxxxxxxxxxxxxxx - Home page: http://norman.rasmussen.co.za/

Previous Message by Thread: click to view message preview

PyMSNt sends error without namespace

I tried to get the vCard of an MSN user not in my contact list. PyMSNt (trunk) returned an error message, <recipient-unavailable/>, but didn't include a namespace declaration on the error element. I think this patch would fix it: Index: disco.py =================================================================== --- disco.py (revision 131) +++ disco.py (working copy) @@ -232,6 +232,7 @@ error.attributes["type"] = etype error.attributes["code"] = str(utils.errorCodeMap[condition]) cond = error.addElement(condition) + cond.attributes["xmlns"] = XMPP_STANZAS self.pytrans.send(el) Magnus

Next Message by Thread: click to view message preview

Google Talk user seeks PyMSN Transport for fun, frolics and perhaps more...

firstly, may I apologise if this message represent a major faux pas on my part; I'm a new subscriber but could find no FAQ to consult before I posted a message. the reason for my message is to ask for recommendations of open (I've noticed some transports allow users from only their own server) PyMSN transports. I currently use msn.jabber,anywise.com but, although service is good, I would like to use a server that keeps their transport version up-to-date (anywise is using 10.2). so, if anyone knows of, or administrates, an open PyMSN transport that is kept up-to-date and is stable, please get in touch. by the way, as an established MSN Messenger user who has for ideological reasons, at least in part, recently switched to Jabber, I've gone to extreme lengths to find a decent MSN Transport, less bothered users may not go to the same lengths. I think it would make a great deal of sense for the PyTransports list to maintain a page similar to http://imfederation.com/networks.html that lists stability and features of open, PyTransports. Many thanks, Sandeep