On 7/24/06, x <[EMAIL PROTECTED]> wrote: > i use ejabberd and with this i can configure access > rules so i can restrict which users can use msn > gateway.
yea, ejabberd is superior here. The other servers don't do acl's yet :-( On 7/25/06, James Bunton <[EMAIL PROTECTED]> wrote: > Neither of these would be too hard to do. > At the moment only option (aside from editing code) is to enable > <allowRegister/> let the users register, > then disable <allowRegister/> in the config file. This would only cover case #1 right? It can't allow/deny users talking to whitelisted MSN users. -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/ From [EMAIL PROTECTED] Wed Jul 26 09:45:58 2006 From: [EMAIL PROTECTED] (Vladimir Vrzic) Date: Wed Jul 26 09:46:13 2006 Subject: [py-transports] Pymsnt Error <error code='405' type='wait'> In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Any more ideas about this? On Fri, 2006-07-21 at 17:09 +0200, Vladimir Vrzic wrote: > > > Having the same problem as of PyMSN 0.11.1. All the remote MSN > > > ports/servers are accessible, though. > > > > Accessible from the computer that is running the transport? Not the > > computer with the client (unless they're the same). > > Accessible from the computer running the transport, of course. We're > running a public server with a couple of thousands of registered users. > > > Also double-check your password. > > The passwords are good -- all accounts had the same problem after > upgrading to 0.11.1. I had to revert to PyMSNt 0.10.3 because the > service is in heavy use, and now everything is working properly, as it > was. > > > What version of Twisted are you running, and what exact error are you > > getting? > > Twisted 2.1.0, running on FreeBSD 5.4-STABLE i386. The error is: > > Failed to connect to MSN servers: [Failure instance: Traceback (failure > with no frames): exceptions.Exception: Timeout > _______________________________________________ > py-transports mailing list > [email protected] > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports From [EMAIL PROTECTED] Thu Jul 20 02:21:33 2006 From: [EMAIL PROTECTED] (wx) Date: Sun Jul 30 13:18:58 2006 Subject: [py-transports] The pymsnt-gw return "timeout" message when I register serivce with jabber-client, but it work well once in a way Message-ID: <[EMAIL PROTECTED]> Hi, I have jabberd2s11 installed with pymsnt0.11.1, The pymsnt-gw return "timeout" message always when I register serivce with jabber-client, and ,sometime it will work well once in a way. I don't known what is happen,could you help me? thanks wx 2006-07-20 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://modevia.com/pipermail/py-transports/attachments/20060720/f8c9b799/attachment.htm From [EMAIL PROTECTED] Mon Jul 31 20:23:45 2006 From: [EMAIL PROTECTED] (Gregoire Menuel) Date: Mon Jul 31 20:24:27 2006 Subject: [py-transports] PyICQt bugs Message-ID: <[EMAIL PROTECTED]> Hi ! I'm one of the administrators of the biggest francophone jabber server. We wanted to switch from jit to PyICQt. Unfortunately we encountered some problems. When launching the transport we encountered tracebacks, these issues were already reported on blathersource : http://www.blathersource.org/bugs_view.php?projid=pyicq-t&bugid=263 http://www.blathersource.org/bugs_view.php?projid=pyicq-t&bugid=132 But more important was that the transport was using 25% of the cpu, I don't know if this is linked with the tracebacks but I suppose so. We switched back to jit, but we are eager to use PyICQt. Do you know when these bugs will be resolved ? Thanks ! -- Gr?goire Menuel JID : [EMAIL PROTECTED] From [EMAIL PROTECTED] Mon Jul 31 20:29:57 2006 From: [EMAIL PROTECTED] (Daniel Henninger) Date: Mon Jul 31 20:30:35 2006 Subject: [py-transports] PyICQt bugs In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> I don't really have any timeframes for now for when "anything" will be fixed with pyicqt. =/ I've got another project (posted about it in my blog) that is consuming my time at the moment. If others submit patches to me though, I'm quite willing to apply them and even try to clean up the code a little and put out a releease. =) What version are you using btw? (loooots of fixes in SVN, but also one big problem ;D ) Daniel On Jul 31, 2006, at 4:23 PM, Gregoire Menuel wrote: > Hi ! > I'm one of the administrators of the biggest francophone jabber > server. > We wanted to switch from jit to PyICQt. Unfortunately we encountered > some problems. > > When launching the transport we encountered tracebacks, these issues > were already reported on blathersource : > http://www.blathersource.org/bugs_view.php?projid=pyicq-t&bugid=263 > http://www.blathersource.org/bugs_view.php?projid=pyicq-t&bugid=132 > > But more important was that the transport was using 25% of the cpu, I > don't know if this is linked with the tracebacks but I suppose so. > We switched back to jit, but we are eager to use PyICQt. > Do you know when these bugs will be resolved ? > > Thanks ! > -- > Gr?goire Menuel > JID : [EMAIL PROTECTED] > _______________________________________________ > py-transports mailing list > [email protected] > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
