On Mon, Jun 9, 2008 at 11:54 AM, Vishal <[EMAIL PROTECTED]> wrote: > This doesnt work as intended. Even if i authorise once and log back > again it asks again for authorisation request. >
Maybe try, remove the auth and then reapprove the auth (the jabber server might be getting confused) > How do i dump the xml? The yahoo log error file doesnt have any xml > stuff there. You'd need to run the transport with dumpProtocol enabled, and redirect it into a log file. (Warning: this will get pretty big!) > Also recently am getting the following errors > > Mon 09 Jun 2008 15:17:41 - CVS 1.69 > Traceback (most recent call last): > File "c:\yahoo-t-0.4\yahoo.py", line 1351, in <module> > apply(each[1],each[2]) > File "c:\yahoo-t-0.4\yahoo.py", line 910, in y_sendping > self.yahooqueue(yobj.fromjid, data) > File "c:\yahoo-t-0.4\yahoo.py", line 73, in yahooqueue > s = self.userlist[fromjid].sock > KeyError: '[EMAIL PROTECTED]' > This sounds like it's trying to maintain a connection that has already closed (which it shouldn't). This should have been fixed in 1.69, but try the latest version just in case it helps. > am using jabberd on windows....will give it a try on openfire and > ejabberd and update you. > The transport is only tested on jabberd2, so you might have found something that jabberd1 doesn't like. - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "py-transports" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/py-transports?hl=en -~----------~----~----~----~------~----~------~--~---
