On Sat, Feb 18, 2006 at 06:58:53PM +0100, Lars T. Mikkelsen wrote: > > Please direct any bug reports to the py-transports@blathersource.org > > mailing list. I'm more likely to miss something in jadmin or jdev when > > I get back. > > I have some very minor issues with the latest release - I'm sorry I > didn't have the time to report these before you made the actual release. > > * A LogEvent() on message errors that course removal of the session > would be nice. (I.e. a LogEvent() just before s.removeMe() in > PyTransport.onMessage()). > * The session should also be removed on presence errors - just like on > message errors. > * The transport doesn't properly handle presence probes to the transport > itself (i.e. to config.jid) - these return an 'unavailable' status.
I forgot to mention this: * I haven't actually observed this (so I might be wrong), but I think there is a risk that PyTransport.onMessage() will respond to an error message with an error message (which is prohibited by RFC 3920, Section 9.3.1). I guess the last 'else:' statement should be 'elif mtype != "error":' - this is also the behaviour of rev. 105 and prior. Best regards, Lars From [EMAIL PROTECTED] Mon Feb 20 22:00:54 2006 From: [EMAIL PROTECTED] (Lars T. Mikkelsen) Date: Mon Feb 20 22:00:59 2006 Subject: [py-transports] PyAIMt & PyICQt: Disconnect on stanza errors Message-ID: <[EMAIL PROTECTED]> Hi, I'm not using PyAIMt nor PyICQt myself, however, some of my friends do and they complained about behaviour similar to what I reported earlier [1, 2] with PyMSNt. In summary, the transports don't check properly for statza errors, and this will, for example, lead to messages being bounced to legacy users. I think the best way to handle this is, to disconnect the session associated with the stanza error (at least for <message/> and <presence/> errors) - and if no such session exists simply ignore the stanza. Best regards, Lars [1] http://modevia.com/pipermail/py-transports/2005-June/000638.html [2] http://modevia.com/pipermail/py-transports/2005-November/001541.html From [EMAIL PROTECTED] Tue Feb 21 08:07:38 2006 From: [EMAIL PROTECTED] (Stian B. Barmen) Date: Tue Feb 21 08:07:44 2006 Subject: [py-transports] Pymsnt & filetransfers In-Reply-To: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> > >> What should I set the ports to in my jabber client(gajim). I > >> have these: > >> > >> file_transfer_port > >> > >> ft_override_host_to_send > > Stian> Do not configure these, they work pr. default. > > Unfortunately not for me. I have also tried PSI and > filetransfer. It gives me the exact same problem. I have just > tried setting the loglevel to 3 to see if I can see anything > wrong, but it just says that I send ftDeclined and I don't > decline the transfer > This is very strange and I have never seen this problem. When you have set up the port and opened in the firewall it should work. Have you tried to telnet to the port? Maybe through the firewall aswell? -stian -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 4490 bytes Desc: not available Url : http://modevia.com/pipermail/py-transports/attachments/20060221/fba0e174/smime.bin From [EMAIL PROTECTED] Tue Feb 21 08:43:36 2006 From: [EMAIL PROTECTED] (Hasse Hagen Johansen) Date: Tue Feb 21 08:44:02 2006 Subject: [py-transports] Pymsnt & filetransfers In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Stian B. Barmen writes: > > This is very strange and I have never seen this problem. When you have set > up the port and opened in the firewall it should work. Have you tried to > telnet to the port? Maybe through the firewall aswell? > I can telnet just fine thorught the firewall on port 8010 and it is also pymsnt which is listening on that port. But it seems it thinks that I am sending and decline(the logs said that I send ftDecline or something like that) Regards Hasse
