Daniel Henninger <[EMAIL PROTECTED]> writes: > Annnnd that would be the problem. ;D It's only going to try 5222 > right now. I'm not sure what the best way to do other ports is. > What I'm leaning towards is that I would type in: > > [EMAIL PROTECTED]:12001 > > (and you don't have to specify the :whatever part if you run on 5222) > If you want to use it in the meantime, edit src/web/ handler.py, look > for 5222, and change it to 12001. =)
So, PyICQ-t is trying to log in to the Jabber server, to determine if the password is right? This might be a job for JEP-0070: http://www.jabber.org/jeps/jep-0070.html Magnus (still only proposing, not coding...) From [EMAIL PROTECTED] Sat Mar 11 17:14:31 2006 From: [EMAIL PROTECTED] (Daniel Henninger) Date: Sat Mar 11 17:14:45 2006 Subject: [py-transports] [PyICQ-t] Can't login to the web interface In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> That's pretty cool, it's not far from what I'm doing right now, but I could beef it up some to be fully compliant with that JEP. Daniel On Mar 11, 2006, at 12:04 PM, Magnus Henoch wrote: > Daniel Henninger <[EMAIL PROTECTED]> writes: > >> Annnnd that would be the problem. ;D It's only going to try 5222 >> right now. I'm not sure what the best way to do other ports is. >> What I'm leaning towards is that I would type in: >> >> [EMAIL PROTECTED]:12001 >> >> (and you don't have to specify the :whatever part if you run on >> 5222) >> If you want to use it in the meantime, edit src/web/ handler.py, look >> for 5222, and change it to 12001. =) > > So, PyICQ-t is trying to log in to the Jabber server, to determine if > the password is right? This might be a job for JEP-0070: > http://www.jabber.org/jeps/jep-0070.html > > Magnus (still only proposing, not coding...) > _______________________________________________ > py-transports mailing list > [email protected] > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports > >
