It appears that this bug is already in the bug database. Sorry, my bad.
Should've looked there first (bugid 89).
I'll try to apply provided patches and see if it works.
Vasili Sviridov wrote:
> Will do.
>
> Or if you can quickly tell me where to dig I'll try to fix it myself
> and send you a patch..
>
> Thanks.
>
> Daniel Henninger ?????:
>
>> Can you post this as a bug report on blathersource.org so I can keep
>> track of it? Thanks! (or if you have already, then it's on my
>> list at the moment I'm working on PyAIM and not doing anything with
>> PyICQ)
>>
>> Daniel
>>
>> On Nov 9, 2005, at 12:18 AM, Vasili Sviridov wrote:
>>
>>> Bump.
>>>
>>> Vasili Sviridov ?????:
>>>
>>>> Hello all,
>>>>
>>>> I'm having a following issue with the transport:
>>>>
>>>> Status message of contacts that have it in Russian is displayed
>>>> incorrectly. It looks like an 8-bit Unicode interpretation. I
>>>> remember having same issue with receiving messages in Russian a
>>>> couple of releases ago. That's the only thing unfixed. Because
>>>> user names, v-cards, and conversations decode Russian fine.
>>>>
>>>> Thanks a lot.
>>>
>>>
From [EMAIL PROTECTED] Fri Nov 11 10:11:58 2005
From: [EMAIL PROTECTED] (Magnus Henoch)
Date: Fri Nov 11 10:11:05 2005
Subject: [py-transports] PyMSNt: no presence error for wrong password
Message-ID: <[EMAIL PROTECTED]>
I'm running PyMSNt from SVN branch 0_10_x, just updated.
When a user registers with the transport with wrong password, no
presence error when he tries to log on; PyMSNt only sends an error
message and an "unavailable" presence. PyICQt sends:
<presence type="error">
<error type="auth">
<not-authorized xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/>
<text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas">
Authentication Error!
Invalid Username or Password.
http://www.aim.com/errors/MISMATCH_PASSWD.html?ccode=us&lang=en
</text>
</error>
</presence>
It would be nice if PyMSNt would do the same.
Sending an error <message/> as PyMSNt does isn't strictly
XMPP-compliant, as XMPP requires that error stanzas be of the same
type as the stanza that caused the error (i.e. <presence/> for
<presence/>).
Additionally, this would make it possible for my automatic
registration tool to log on with negative priority on an ejabberd
server, as ejabberd discards <message/>s of type "error" when there is
no online resource with non-negative priority.
Magnus
From [EMAIL PROTECTED] Sat Nov 12 17:30:55 2005
From: [EMAIL PROTECTED] (Lars T. Mikkelsen)
Date: Sat Nov 12 17:31:09 2005
Subject: [py-transports] PyMSNt: Messages from MSN users are bounced on
errors
Message-ID: <[EMAIL PROTECTED]>
Hi,
When PyMSNt fails to deliver a message from a MSN user to a Jabber user,
the message will be bounced to the MSN user. I noticed this while the
jabber.org server was unstable earlier today. When PyMSNt attempted to
send a message to my jabber.org account, the jabber.org server bounced
the message (with a type='error' attribute) to the transport. PyMSNt
does, however, not check for the type='error' attribute and treats the
message as a regular message from me to the MSN user. The result is,
that the MSN user will receive the message he just sent.
I think the bug is similar to the one I reported earlier on presence
messages [1]. I'm attaching relevant parts of debug.log.
Best regards,
Lars
[1] http://modevia.com/pipermail/py-transports/2005-June/000638.html
-------------- next part --------------
2005/11/12 17:06 CET [Switchboard,client] << MSG <user's passport> <user's
name> 127
2005/11/12 17:06 CET [Switchboard,client] << MIME-Version: 1.0
2005/11/12 17:06 CET [Switchboard,client] << Content-Type: text/plain;
charset=UTF-8
2005/11/12 17:06 CET [Switchboard,client] << X-MMS-IM-Format:
FN=MS%20Shell%20Dlg; EF=; CO=0; CS=0; PF=0
2005/11/12 17:06 CET [Switchboard,client] <<
2005/11/12 17:06 CET [Switchboard,client] <user's message>
2005/11/12 17:06 CET [Switchboard,client] INFO :: (u'<my JID>', '<user's
passport>') :: :: gotMessage :: <legacy.msnw.Switchboard instance at
0xb7500a6c> :: {'message': <tlib.msn.MSNMessage instance at 0xb7500c8c>,
'self': <legacy.msnw.Switchboard instance at 0xb7500a6c>}
2005/11/12 17:06 CET [Switchboard,client] INFO :: <my JID> :: :: sendMessage
:: <session.Session instance at 0xb75f0fac> :: {'body': u'<user's message>',
'delay': None, 'self': <session.Session instance at 0xb75f0fac>, 'fro':
'<user's passport>@<my transport>', 'mtype': 'chat', 'to': u'<my JID>/iChat'}
2005/11/12 17:06 CET [Switchboard,client] INFO :: :: :: sendMessage ::
[...]/src/jabw.py :: {'body': u'<user's message>', 'delay': None, 'fro':
'<user's passport>@<my transport>', 'mtype': 'chat', 'to': u'<my JID>/iChat',
'pytrans': <main.PyTransport instance at 0xb75d4eec>}
[snip]
2005/11/12 17:08 CET [XmlStream,client] INFO :: <my JID> :: Message packet ::
onMessage :: <session.Session instance at 0xb75f0fac> :: {'body': u'<user's
message>', 'el': <twisted.xish.domish.Element object at 0xb7500ccc>, 'child2':
<twisted.xish.domish.Element object at 0xb7500bec>, 'froj':
<twisted.words.protocols.jabber.jid.JID instance at 0xb7500eec>, 'composing':
True, 'self': <session.Session instance at 0xb75f0fac>, 'fro': u'<my
JID>/iChat', 'mID': u'85', 'inviteTo': '', 'to': u'<user's passport>@<my
transport>', 'noerror': False, 'child': <twisted.xish.domish.Element object at
0xb7500f6c>, 'inviteRoom': '', 'mtype': u'error', 'messageEvent': True, 'toj':
<twisted.words.protocols.jabber.jid.JID instance at 0xb750090c>}
2005/11/12 17:08 CET [XmlStream,client] INFO :: <my JID> :: Message. ::
messageReceived :: <session.Session instance at 0xb75f0fac> :: {'body':
u'<user's message>', 'resource': u'iChat', 'dest': u'<user's passport>@<my
transport>', 'self': <session.Session instance at 0xb75f0fac>, 'mtype':
u'error', 'source': u'<my JID>', 'noerror': False, 'destr': None, 'groupchat':
None}
2005/11/12 17:08 CET [XmlStream,client] INFO :: <my JID> :: :: sendMessage ::
<legacy.glue.LegacyConnection instance at 0xb757c5ec> :: {'text': u'<user's
message>', 'noerror': False, 'resource': u'iChat', 'self':
<legacy.glue.LegacyConnection instance at 0xb757c5ec>, 'remoteUser': u'<user's
passport>'}
2005/11/12 17:08 CET [XmlStream,client] INFO :: (u'<my JID>', '<user's
passport>') :: :: sendMessage :: <legacy.msnw.SwitchboardSession instance at
0xb750092c> :: {'failedMessage': <function failedMessage at 0xb756e6f4>,
'noerror': False, 'message': u'<user's message>', 'tempmsncon':
<legacy.glue.LegacyConnection instance at 0xb757c5ec>, 'self':
<legacy.msnw.SwitchboardSession instance at 0xb750092c>}
2005/11/12 17:08 CET [XmlStream,client] >> MSG 13 A 101
2005/11/12 17:08 CET [XmlStream,client] >> MIME-Version: 1.0
2005/11/12 17:08 CET [XmlStream,client] >> Content-Type: text/x-clientcaps
2005/11/12 17:08 CET [XmlStream,client] >> Client-Name: PyMSNt
2005/11/12 17:08 CET [XmlStream,client] >> JabberID: <my JID>
2005/11/12 17:08 CET [XmlStream,client]
2005/11/12 17:08 CET [XmlStream,client] >> MSG 14 N 66
2005/11/12 17:08 CET [XmlStream,client] >> MIME-Version: 1.0
2005/11/12 17:08 CET [XmlStream,client] >> Content-Type: text/plain;
charset=UTF-8
2005/11/12 17:08 CET [XmlStream,client] <user's message>
From [EMAIL PROTECTED] Mon Nov 14 09:20:02 2005
From: [EMAIL PROTECTED] (Norman Rasmussen)
Date: Mon Nov 14 09:20:04 2005
Subject: [py-transports] PyMSNt JEP-0100 feature request
Message-ID: <[EMAIL PROTECTED]>
http://www.jabber.org/jeps/jep-0100.html
it would be swell if the msn gateway would understand the
jabber:iq:gateway protocol:
recv:
<iq type="get" to="msn.local" id="ac92a" >
<query xmlns="jabber:iq:gateway"/>
</iq>
send:
<iq from="msn.local" type="result" id="ac99a" to="[EMAIL PROTECTED]" >
<query xmlns="jabber:iq:gateway">
<desc>Enter the user's address:</desc>
<prompt/>
</query>
</iq>
and:
recv:
<iq type="set" to="msn.local" id="ac9ba" >
<query xmlns="jabber:iq:gateway">
<prompt>[EMAIL PROTECTED]</prompt>
</query>
</iq>
send:
<iq from="msn.local" type="result" id="ac9ba" to="[EMAIL PROTECTED]" >
<query xmlns="jabber:iq:gateway">
<prompt>[EMAIL PROTECTED]</prompt>
</query>
</iq>
This is the sort of thing that only gets used once in a blue moon, but
it does make the client experience soooo much nicer.
--
- Norman Rasmussen
- Email: [EMAIL PROTECTED]
- Home page: http://norman.rasmussen.co.za/
From [EMAIL PROTECTED] Mon Nov 14 09:28:07 2005
From: [EMAIL PROTECTED] (James Bunton)
Date: Mon Nov 14 09:28:41 2005
Subject: [py-transports] PyMSNt JEP-0100 feature request
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
On 14/11/2005, at 8:20 PM, Norman Rasmussen wrote:
> http://www.jabber.org/jeps/jep-0100.html
>
> it would be swell if the msn gateway would understand the
> jabber:iq:gateway protocol:
>
> recv:
> <iq type="get" to="msn.local" id="ac92a" >
> <query xmlns="jabber:iq:gateway"/>
> </iq>
>
> send:
> <iq from="msn.local" type="result" id="ac99a" to="[EMAIL PROTECTED]" >
> <query xmlns="jabber:iq:gateway">
> <desc>Enter the user's address:</desc>
> <prompt/>
> </query>
> </iq>
>
> and:
>
> recv:
> <iq type="set" to="msn.local" id="ac9ba" >
> <query xmlns="jabber:iq:gateway">
> <prompt>[EMAIL PROTECTED]</prompt>
> </query>
> </iq>
>
> send:
> <iq from="msn.local" type="result" id="ac9ba" to="[EMAIL PROTECTED]" >
> <query xmlns="jabber:iq:gateway">
> <prompt>[EMAIL PROTECTED]</prompt>
> </query>
> </iq>
>
> This is the sort of thing that only gets used once in a blue moon, but
> it does make the client experience soooo much nicer.
It does. Just tested then with 0_11_x branch.
It should work fine with 0.10.x as well.
---
James
