On 8/31/06, Joe Berry <[EMAIL PROTECTED]> wrote: > Thanks for all the advice. I will do some more testing tonight. As aim > support is important to me, do you think it makes sense to consider an > alternative jabber server, such as ejabberd?
When in doubt, make sure those bottom three options (sasl,bind,wrap) are off. This will make the transport run in legacy mode, and it should be able to connect to _any_ jabber server in this mode. BTW, switching to ejabberd doesn't make the transport config less confusing - you need to set up a single port per transport, each with their own password (sort of like jabberd1) jabberd2 pros / ejabberd cons: - jabberd2 is c, ejabberd is erlang - easier to read and build jabberd2 code. - no muc, have to run jabberd1-muc under jabberd1 or jcr or use palver (python muc). jabberd2 cons / ejabberd pros: - ejabberd _does_ cluster - if that's important to you (s2s & c2s cluster, transports can't) - ejabberd development seems to be more active (so pubsub and PEP are 'closer' to working) - comes with built in muc and irc components On 8/31/06, Daniel Henninger <[EMAIL PROTECTED]> wrote: > Twisted is, unfortunately, a mobile target for us. > James put in a twistfix thing into pymsnt that I need to incorporate > into pyaim/pyicq. PyIRCt and PyYIMt are in their library's CVS repo (as 'examples' of what the library can do) - I'm not sure if this is a better or worse idea :-P -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/ From [EMAIL PROTECTED] Thu Aug 31 21:29:11 2006 From: [EMAIL PROTECTED] (Michael Vogel) Date: Thu Aug 31 21:29:27 2006 Subject: [py-transports] PyICQ 0.7b can't connect anymore In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Daniel Henninger schrieb: > Hrm. That's uncool. That non-clean fashion message is, as you cansee for > yourself, vague and not totally helpful. Yeah, I'm sorry. How can I provide more help? Are there any debug possibilities? > How long has thisbeen going on? Since yesterday morning I think. Michael From [EMAIL PROTECTED] Thu Aug 31 23:11:01 2006 From: [EMAIL PROTECTED] (Daniel Henninger) Date: Thu Aug 31 23:11:12 2006 Subject: [py-transports] PyICQ 0.7b can't connect anymore In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> On Aug 31, 2006, at 5:29 PM, Michael Vogel wrote: > Daniel Henninger schrieb: >> Hrm. That's uncool. That non-clean fashion message is, as you >> cansee for >> yourself, vague and not totally helpful. > > Yeah, I'm sorry. How can I provide more help? Are there any debug > possibilities? Oh I didn't mean for it to sound like -you- weren't being helpful. =) Oh oh, actually there is one good debug thing you could do. Could you get a tcpdump of it and send that to me? (directly, not to the list -> [EMAIL PROTECTED]) [I'm assuming unix, if not then... well I'm not sure =) ] tcpdump -s 5000 -x -X -w pyicqdump.pcap port 5190 Is usually what I use. I'm not sure all of those flags are necessary to just record the data to a file, but hey. Anyway, I don't know how familiar you are with tcpdump (and/or ethereal/whatever the crap they've renamed it). Alternatively you can contact me via jabber and we can try to work through it. Daniel > >> How long has thisbeen going on? > > Since yesterday morning I think. > > Michael > _______________________________________________ > py-transports mailing list > [email protected] > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
