Hi. I was sending a file to a contact through PyMSNt just now. The file was apparently to large and an error message was issued. The only problem is that I did not receive the error message, but the MSN contact did :)
The error message was: A file 'xxx.xxx' was rejected because it was over the size limit of 524288. To send larger files to this person, please use Jabber. See http://jabber.oscarh.net for details. -- Oscar Hellstr?m, [EMAIL PROTECTED] web: personal.oscarh.net jid: [EMAIL PROTECTED] icq: 52604556 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://modevia.com/pipermail/py-transports/attachments/20060305/5ea7f7e0/attachment.pgp From [EMAIL PROTECTED] Sun Mar 5 07:05:56 2006 From: [EMAIL PROTECTED] (Daniel Henninger) Date: Sun Mar 5 07:06:06 2006 Subject: [py-transports] JID Migration In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> >>> Yet another thing is detecting IP address and client version of ICQ >>> contact. I wrote patches for PyICQ but it's seems they are removed >>> from latest svn. >> >> I didn't "remove" anything like that, so if that's the case then it's >> just that something is buggy. I still see the parts that are >> supposed to detect those pieces. I haven't tested that though. >> Please file a bug report. > > I'll get lates svn and will check for that code or adapt old patches > to latest svn. Aha, found out what was wrong. Functionality is back in. =) Daniel From [EMAIL PROTECTED] Sun Mar 5 12:48:28 2006 From: [EMAIL PROTECTED] (Norman Rasmussen) Date: Sun Mar 5 12:48:35 2006 Subject: [py-transports] Idea for handling invisible In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> JEP-0018 isn't even Historical, it's Rejected - "Implementation of the protocol described herein is not recommended under any circumstances." Rather privacy lists, as defined in RFC 3921, and examples of use in 'JEP-0126: Invisibility' (http://www.jabber.org/jeps/jep-0126.html) should be used. If any privacy/invisible changes are made, they need to be with regards to the latter, _not_ the former. On 2/26/06, David Laban <[EMAIL PROTECTED]> wrote: > This has probably been suggested many many times before, but if I (as > [EMAIL PROTECTED]/Psi ) send: > > <presence type="invisible" > > <priority>5</priority> > <x xmlns="vcard-temp:x:update"> > <nickname>Romeo</nickname> > </x> > </presence> > > Will the pseudo-addresses (eg. [EMAIL PROTECTED]) receive: > <presence from="[EMAIL PROTECTED]/Psi" type="unavailable" > to="[EMAIL PROTECTED]" />? > > If so, the msn.montague.net gateway could use this flood of presence messages > to determine which status the MSN users see. To inform the gateway that I'm > actually available, I would send: > > <presence to="msn.montague.net" > > <priority>0</priority> > </presence> > > Then it would log onto MSN again (as invisible, because that's what all the > users @msn.montague.net see) and push the MSN users' presence info through to > jabber. It should also send: > > <presence from="msn.montague.net" type="unavailable" to="[EMAIL PROTECTED]" > > <status>Invisible</status> > </presence> > > so the client knows there is not an error. > > Would this work? > _______________________________________________ > py-transports mailing list > [email protected] > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports > -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/ From [EMAIL PROTECTED] Sun Mar 5 12:53:21 2006 From: [EMAIL PROTECTED] (Daniel Henninger) Date: Sun Mar 5 12:53:29 2006 Subject: [py-transports] Nicknames? Message-ID: <[EMAIL PROTECTED]> So. . . I've been working on getting ICQ nicknames working well but, in the end, they're not actually working the way I thought they would work. Using the patched Psi, I expected that once the nickname update came through, that my roster list would reflect the nickname instead of the [EMAIL PROTECTED] Instead, I only see the nickname listed in the 'hover over' pop-up window. Is this the expected behavior? Am I missing something? Do other clients handle the "nickname update" in a 'better' manner? I guess I just expected something more phenominal to occur. =D Also, is there a JEP that describes this nickname update? Daniel -- "The most addictive drug in the world is music." - The Lost Boyz
