On 6/5/06, Jensen, Jim <[EMAIL PROTECTED]> wrote: > I am trying to test various transports with various servers. cool
It looks like wildfire wants the transport's hostname to be yahoo.localhost.jensend810.openpeak.com. Try changing the config file's Hostname to match this. Btw: when I set up my transports I only type 'msn' or 'yahoo' into the wildfire console. That way they are registered as msn.example.com and yahoo.example.com. As a point of interest, I've been working on wildfire sasl support for xmpppy. (In CVS working well) I hope to release a new version soon. (The transports also have xml config files now, very similar to the existing transport's config files) -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/ From [EMAIL PROTECTED] Tue Jun 6 09:41:52 2006 From: [EMAIL PROTECTED] (=?ISO-8859-1?Q?Arnaud_Ab=E9lard?=) Date: Tue Jun 6 09:41:58 2006 Subject: [py-transports] MSN will soon allow to add yahoo! contacts Message-ID: <[EMAIL PROTECTED]> It looks like the MSN/Yahoo! deal to make their respective networks compatible is on a good track: http://spaces.msn.com/messengersays/Blog/cns!5B410F7FD930829E!16754.entry I wonder they will just make their MSN client connect to yahoo!'s network or make a kind of transport between MSN and Yahoo! I really hope (but i doubt it will be) that it's the 2nd option.. that would make the python MSN transport compatible with yahoo ;) Cross your fingers! Arnaud -- Arnaud Ab?lard (jabber: [EMAIL PROTECTED]) Administrateur Syst?me Centre de Ressources Informatiques Universit? de Nantes From [EMAIL PROTECTED] Tue Jun 6 13:16:30 2006 From: [EMAIL PROTECTED] (Norman Rasmussen) Date: Tue Jun 6 13:16:34 2006 Subject: [py-transports] MSN will soon allow to add yahoo! contacts In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> On 6/6/06, Arnaud Ab?lard <[EMAIL PROTECTED]> wrote: > It looks like the MSN/Yahoo! deal to make their respective networks > compatible is on a good track: """As it turns out, it's been a hard problem to solve, and the team has been working hard""" WTF!!!! just do fcking XMPP federation. Problem solved! For something that was announced in October, and was supposed to be released in Q1 of 2006, I guess a few months late is about right. Maybe it'll happen before Duke Nukem Forever is released. Wake me up when they do XMPP federation. -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/ From [EMAIL PROTECTED] Tue Jun 6 13:55:15 2006 From: [EMAIL PROTECTED] (Boris Granveaud) Date: Tue Jun 6 13:55:22 2006 Subject: [py-transports] problem when upgrading PyMSN 0.10.3 => 0.11a Message-ID: <[EMAIL PROTECTED]> Hello, I would like to upgrade my a working 0.10.3 PyMSN to the 0.11a version. Here is the error message I've got: [EMAIL PROTECTED]:~/jabber/pymsnt-0.11$ ./PyMSNt.py Unable to find a reactor. Exiting... Apparently the working 0.10.3 version uses the poll reactor on my system: [EMAIL PROTECTED]:~/jabber/pymsnt-0.10.3$ ps -ef | grep pymsn msn 7173 1 0 11:13 ? 00:00:00 /usr/bin/python2.4 /usr/bin/twistd2.4 -oy /home/msn/jabber/pymsnt-0.10.3/PyMSNt.tac -r poll --pidfile /home/msn/jabber/pymsnt-0.10.3/PyMSNt.pid -l /home/msn/jabber/pymsnt-0.10.3/debug.log With 0.11, even if I specify 'poll' on config.xml, it doesn't work. Any idea? Boris.
