Yeah. I should have been more specific as I did know that manually entering the JID fixed the issue. Thanks for the clarification Jorge.
-- Travis Bell On 24-Apr-06, at 11:29 AM, Jorge Merlino wrote: > On Mon, Apr 24, 2006 at 09:32:27AM -0600, Travis Bell wrote: >> James, >> >> Looks like something got broken with 0.5... I cannot register AIM/ >> ICQ/ >> MSN anymore. These functions work perfectly fine with 0.4 on the same >> server. >> >> I get this error for all the services (replace AIM with MSN & ICQ of >> course)... >> >> --------- >> Could not find a AIM Transport on your server. Please contact your >> server administrator. >> There was an error registering you with the AIM Gateway. Please try >> again later. >> --------- >> >> I running pretty much the latest SVN versions of ALL transports with >> Wildfire. If you want to see for yourself, you can see: >> >> http://www.ijabber.com/register/ <-- 0.4 works great >> http://www.ijabber.com/webreg/ <-- 0.5 doesn't work so great >> >> Cheers, >> >> -- >> Travis Bell >> > > I think there is a problem with the automatic discovery of > transports. I > had the same issue but all worked fine when instead of "auto" I > indicated the exact jid of the transport in the configuration file. > I'm using wildfire also so I don't know which of the two is to > blame for > this. > > Regards > Jorge > _______________________________________________ > py-transports mailing list > [email protected] > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports -------------- next part -------------- An HTML attachment was scrubbed... URL: http://modevia.com/pipermail/py-transports/attachments/20060424/83ecc689/attachment.html From [EMAIL PROTECTED] Tue Apr 25 00:23:59 2006 From: [EMAIL PROTECTED] (James Bunton) Date: Tue Apr 25 00:24:10 2006 Subject: [py-transports] PyMSNt & pyicq In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> On 25/04/2006, at 12:13 AM, Daniel Henninger wrote: > *blink* James? Your thoughts on this? If I'm reading this right, > yahoo-transport is sending a "subscribed" presence to the client, and > subscribing itself to all of the user's presences. That doesn't make > a lot of sense to me. If it's actually ending up effecting the end > user's roster, my understanding of 'how things work' seems to dictate > that the jabber server should say "uh... no". Looks like some custom protocol similar to what I'm using with roster-subsync. Except that this takes advantage of a bug in Jabberd 1.4.2 and old versions of Jabberd2. Basically if somebody sent you a presence type="subscribed" they would get pushed onto your roster without your authorisation. That's been fixed in recent versions (thankfully). Modern Jabber servers should ignore these packets. > Francisco, what Jabber server are you running? In the past, when I've > tried to "set" like that, I get flat out denied. And like I said, the > yahoo transport bugs me for everyone in my contact list (just like > PyICQ). I wonder if your Jabber server has special handling for this? > WEIRD! =) > >> Is some kind of way of avoiding acept every user .. (auto-import) >> contacts ? on pymsn and pyicq ? > > See my earlier post. =D > > I'd love to see the ability to kill the bazillion auth requests... > but just as far as I know we don't have a supported way of doing that. > (aside from that roster item exchange hooha, and I couldn't get that > to work with the clients I tested with) If what you are showing me > above works with some Jabber servers, then I'm certainly willing to > add it in for those servers to take advantage of. (or at least try, > if it's reasonable ;D ) > > Daniel Yeah, I don't think any clients have support for the roster exchange JEP. --- James
