Hi all,

I'm using PyMSN-t from the cvs, with support of avatar, etc. (which is great!)

I just realised that with this version the nickname of msn contacts
does not appear anymore in their status message. So, the only way of
seeing the nickname of msn contacts is to look at their vCard. I found
the previous mechanims really handy, though.

I inspected the xml output with two different msn gateways, and I saw
that actually no <status></status> is sent with the cvs version of
PyMSN, which is why the nickname is not visible as status.

XML presence with PyMSN-t 0.9.1:

<presence to='<my-jabber-id>' from='<a-msn-contact>@msn.frimouvy.org'>
<show>away</show>
<status>here comes the nickname</status>
</presence>

XML presence with PyMSN-t CVS:

<presence to='<my-jabber-id>' from='<a-msn-contact>@msn2.fritalk.com'>
<show>away</show>
<x xmlns='vcard-temp:x:update'>
<photo>859f08aac9535d6161667b40cf8d4fba9fd99745</photo>
<nickname>here comes the nickname</nickname>
</x>
</presence>

So I looked at source code, and found this in contact.py:

        def sendPresence(self):
                avatarHash = ""
                if(self.avatar):
                        avatarHash = self.avatar.getImageHash()
                
self.contactList.session.sendPresence(to=self.contactList.session.jabberID,
fro=self.jid, ptype=self.ptype, show=self.show, status=self.status,
avatarHash=avatarHash, nickname=self.nickname)

The thing here is that self.status is initialized at "", and visibly
never set as being the nickname. I don't know if all this is done
willingly, but to get the previous behaviour I suppose that
updateNickname should be changed in:

        def updateNickname(self, nickname, push=True):
                if(self.nickname != nickname):
                        if(push): self.sendPresence()
                        self.nickname = nickname
                        self.status = nickname

I hope I'm clear enough with all this. I would be pleased to give more
information about this if necessary.

regards,

Bertrand Rousseau
From [EMAIL PROTECTED]  Sun Aug 21 19:13:14 2005
From: [EMAIL PROTECTED] (Norman Rasmussen)
Date: Sun Aug 21 19:13:27 2005
Subject: [py-transports] MSN contacts nickname in status message
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

This is by design: These days the MSN status is in the status field,
and the v:card is used for the nickname.

On 21/08/05, Bertrand Rousseau <[EMAIL PROTECTED]> wrote:
> Hi all,
> 
> I'm using PyMSN-t from the cvs, with support of avatar, etc. (which is great!)
> 
> I just realised that with this version the nickname of msn contacts
> does not appear anymore in their status message. So, the only way of
> seeing the nickname of msn contacts is to look at their vCard. I found
> the previous mechanims really handy, though.
> 
> I inspected the xml output with two different msn gateways, and I saw
> that actually no <status></status> is sent with the cvs version of
> PyMSN, which is why the nickname is not visible as status.
> 
> XML presence with PyMSN-t 0.9.1:
> 
> <presence to='<my-jabber-id>' from='<a-msn-contact>@msn.frimouvy.org'>
> <show>away</show>
> <status>here comes the nickname</status>
> </presence>
> 
> XML presence with PyMSN-t CVS:
> 
> <presence to='<my-jabber-id>' from='<a-msn-contact>@msn2.fritalk.com'>
> <show>away</show>
> <x xmlns='vcard-temp:x:update'>
> <photo>859f08aac9535d6161667b40cf8d4fba9fd99745</photo>
> <nickname>here comes the nickname</nickname>
> </x>
> </presence>
> 
> So I looked at source code, and found this in contact.py:
> 
>         def sendPresence(self):
>                 avatarHash = ""
>                 if(self.avatar):
>                         avatarHash = self.avatar.getImageHash()
>                 
> self.contactList.session.sendPresence(to=self.contactList.session.jabberID,
> fro=self.jid, ptype=self.ptype, show=self.show, status=self.status,
> avatarHash=avatarHash, nickname=self.nickname)
> 
> The thing here is that self.status is initialized at "", and visibly
> never set as being the nickname. I don't know if all this is done
> willingly, but to get the previous behaviour I suppose that
> updateNickname should be changed in:
> 
>         def updateNickname(self, nickname, push=True):
>                 if(self.nickname != nickname):
>                         if(push): self.sendPresence()
>                         self.nickname = nickname
>                         self.status = nickname
> 
> I hope I'm clear enough with all this. I would be pleased to give more
> information about this if necessary.
> 
> regards,
> 
> Bertrand Rousseau
> _______________________________________________
> py-transports mailing list
> py-transports@blathersource.org
> 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 Aug 21 23:11:09 2005
From: [EMAIL PROTECTED] (Lars T. Mikkelsen)
Date: Sun Aug 21 23:11:16 2005
Subject: [py-transports] MSN contacts nickname in status message
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

On Sun, Aug 21, 2005 at 09:13:14PM +0200, Norman Rasmussen wrote:
> This is by design: These days the MSN status is in the status field,
> and the v:card is used for the nickname.

Just to elaborate. The status message is called a personal message in
Messenger, and it's one of the new features of MSN Messenger 7. IMHO,
the new design is the Right Way, since the fields are used as they are
intended to be - and it's actually quite nice once you get used to it. I
do agree, however, that many Messenger users have to learn to use the
personal message and not their nickname for status messages. :-)

Best regards,
Lars
From [EMAIL PROTECTED]  Mon Aug 22 09:23:50 2005
From: [EMAIL PROTECTED] (=?ISO-8859-1?Q?Arnaud_Ab=E9lard?=)
Date: Mon Aug 22 09:23:55 2005
Subject: [py-transports] PyMSNt 0.9.4 & 0.10 testing
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

We have been using in production PyMSNt 0.10 for now a few days and i 
noticed that avatars coming from some clients (some msn7? some trillian? 
not sure, hard to tell) aren't downloaded.

no, i have a few questions:

- when is the avatar refreshed? (if a contact changes his/her avatar, 
it's not updated) is that client side?

- if i set an avatar with my jabber client (gajim allows you to set an 
avatar) will the MSN gateway send it too?

Thanks for that great piece of software!

Arnaud


James Bunton wrote:
> Hi everybody.
> 
> I think that the avatars branch is just about stable enough to release.
> 
> The latest CVS update brings a few fixes.
> The main change is hashed spool and avatar directories.
> Your current setup should be automatically migrated. Please back up your 
> spool directory before testing this. I don't anticipate any problems 
> though.
> 
> If you have any troubles with this please let me know this week. Unless 
> there's any major troubles I'm planning a release next Monday for PyMSNt 
> 0.9.4 and 0.10.
> 
> ---
> 
> James
> 
> _______________________________________________
> py-transports mailing list
> py-transports@blathersource.org
> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports


-- 
Arnaud Ab?lard
Administrateur Syst?mes et R?seaux
Facult? de Sciences et Techniques
Universit? de Nantes
From [EMAIL PROTECTED]  Mon Aug 22 12:07:46 2005
From: [EMAIL PROTECTED] (Lars T. Mikkelsen)
Date: Mon Aug 22 12:08:07 2005
Subject: [py-transports] PyMSNt 0.9.4 & 0.10 testing
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

On Mon, Aug 22, 2005 at 11:23:50AM +0200, Arnaud Ab?lard wrote:
> We have been using in production PyMSNt 0.10 for now a few days and i 
> noticed that avatars coming from some clients (some msn7? some trillian? 
> not sure, hard to tell) aren't downloaded.

Do you get any errors on stdout? I reported some issues with avatar
transfers some time ago [1]. It might be these issues that are not yet
fixed.

> - when is the avatar refreshed? (if a contact changes his/her avatar, 
> it's not updated) is that client side?

The current CVS version will fetch the avatar as soon as the contact
changes it. In src/legacy/msnw.py there is an option (the variable
GETALLAVATARS in the top of the file) that will change this behaviour,
so the avatar is fetched only when a conversation is started with the
contact. I think James is still considering which should be the default
behaviour.

> - if i set an avatar with my jabber client (gajim allows you to set an 
> avatar) will the MSN gateway send it too?

If your Jabber client supports JEP-0153 avatars (as Gajim 0.8 does) your
MSN contacts will see your avatar.

Best regards,
Lars

[1] http://modevia.com/pipermail/py-transports/2005-June/000672.html
From [EMAIL PROTECTED]  Mon Aug 22 12:24:03 2005
From: [EMAIL PROTECTED] (Norman Rasmussen)
Date: Mon Aug 22 12:24:05 2005
Subject: [py-transports] PyMSNt patch for discovering adhoc commands
Message-ID: <[EMAIL PROTECTED]>

JEP-0050 states in section 2.2:

If additional information about a command is desired, the requester
queries for disco information on the command node:

<example 5 and 6>

A responder MUST at least provide an appropriate <identity/> and
<feature var='http://jabber.org/protocol/commands'/>, and SHOULD
include <feature var='jabber:x:data'/>. It is not required to support
additional information about a command. If the command is not
available to the requester, the responder SHOULD respond with a 403
"Forbidden" error.

This patch [1] adds the #info feature:commands reply, (and a empy
#items reply).  It missed the identity, but something is better than
nothing.

[1] http://www.darkskies.za.net/~norman/jabber/pymsnt-adhoc-disco.patch

In retrospect the disco framework needs to rather implement #info and
#items in a central class that deals with retrieving these values
transparently.  The commands node should inherit from this class, and
the enumeration of commands should use the same functions that getting
the list of nodes uses (the xml is tit-for-tat in the end).  For
operations such as set that invoke the actual commands, there could be
a method to override.

-- 
- Norman Rasmussen
 - Email: [EMAIL PROTECTED]
 - Home page: http://norman.rasmussen.co.za/
From [EMAIL PROTECTED]  Mon Aug 22 12:40:03 2005
From: [EMAIL PROTECTED] (=?UTF-8?B?QXJuYXVkIEFiw6lsYXJk?=)
Date: Mon Aug 22 12:40:07 2005
Subject: [py-transports] PyMSNt 0.9.4 & 0.10 testing
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

Lars T. Mikkelsen wrote:
> On Mon, Aug 22, 2005 at 11:23:50AM +0200, Arnaud Ab?lard wrote:
> 
>>We have been using in production PyMSNt 0.10 for now a few days and i 
>>noticed that avatars coming from some clients (some msn7? some trillian? 
>>not sure, hard to tell) aren't downloaded.
> 
> 
> Do you get any errors on stdout? I reported some issues with avatar
> transfers some time ago [1]. It might be these issues that are not yet
> fixed.

i just checked and i'm getting this:

Updated MSNOBJ received! 
%3cmsnobj%20Creator%3d%22remote%40hotmail%2ecom%22%20Size%3d%221051%22%20Type%3d%223%22%20Location%3d%22TFR2C2%2etmp%22%20Friendly%3d%22AAA%3d%22%20SHA1D%3d%22ky%2f4e5xvYQ2W1rMi49g7V8ZYHPs%3d%22%20SHA1C%3d%22m70qFH9Hw8ow65b98cd%2fL15%2fWEg%3d%22%2f%3e
getNextPacket (Avatar_Receive) [EMAIL PROTECTED] [EMAIL PROTECTED] 0
Packed fields: 0x0 0xe1e20e 0x0 0x2a1 0x2a1 0x0 0x28523b9e 0x0 0x0 0x0
processPacket [EMAIL PROTECTED] [EMAIL PROTECTED] 1
Unpacked fields: 0x0L 0x2016CE17L 0x0L 0x2A1L 0x0L 0x2L 0xE1E20EL 0x0L 
0x2A1L 0x0L
ERROR in avatar transfer:  <tlib.msnp2p.MSNP2P_Avatar_Receive instance 
at 0xb754be0c> field7,0,676477854 in state: 1
getNextPacket (Avatar_Receive) [EMAIL PROTECTED] [EMAIL PROTECTED] -1
processPacket [EMAIL PROTECTED] [EMAIL PROTECTED] 0
Parsing MSNSLPMessage INVITE MSNMSGR:[EMAIL PROTECTED] MSNSLP/1.0

plus, all the files (only a very few, which is weird) in the avatars 
folder are png files (probably normal), i have python-imaging 1.1.4 
installed...

Arnaud

-- 
Arnaud Ab?lard
Administrateur Syst?mes et R?seaux
Facult? de Sciences et Techniques
Universit? de Nantes
From [EMAIL PROTECTED]  Mon Aug 22 12:52:00 2005
From: [EMAIL PROTECTED] (=?UTF-8?B?QXJuYXVkIEFiw6lsYXJk?=)
Date: Mon Aug 22 12:52:03 2005
Subject: [py-transports] PyMSNt 0.9.4 & 0.10 testing
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

Lars T. Mikkelsen wrote:

> If your Jabber client supports JEP-0153 avatars (as Gajim 0.8 does) your
> MSN contacts will see your avatar.

hum..i guess the server also has to support JEP-0153.. unfortunatly we 
are using jabberd2 which doesn't seem to support it...

what are the jabber servers supporting JEP-0153 ? ejabberd, i guess?

AA

> 
> Best regards,
> Lars
> 
> [1] http://modevia.com/pipermail/py-transports/2005-June/000672.html
> _______________________________________________
> py-transports mailing list
> py-transports@blathersource.org
> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports


-- 
Arnaud Ab?lard
Administrateur Syst?mes et R?seaux
Facult? de Sciences et Techniques
Universit? de Nantes
From [EMAIL PROTECTED]  Mon Aug 22 13:01:51 2005
From: [EMAIL PROTECTED] 
(=?ISO-8859-1?Q?Francisco_Joaqu=EDn_Rodr=EDguez_Prados?=)
Date: Mon Aug 22 13:01:55 2005
Subject: [py-transports] MSN contacts nickname in status message
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

2005/8/22, Lars T. Mikkelsen <[EMAIL PROTECTED]>:
> do agree, however, that many Messenger users have to learn to use the
> personal message and not their nickname for status messages. :-)

Well, now the have the double space to write the fool things they used
to write only in the nickname - at least that's what my friends are
doing right now... XD

But yeah, I think so: this is the best way of merging the nickname and
status message in Jabber-MSN.

-- 
Francisco Joaqu?n Rodr?guez Prados
Fachbereich Informatik,
Fachhochschule Darmstadt,
Darmstadt, Germany
E-mail: [EMAIL PROTECTED]
JID: [EMAIL PROTECTED]
From [EMAIL PROTECTED]  Mon Aug 22 13:07:19 2005
From: [EMAIL PROTECTED] (Norman Rasmussen)
Date: Mon Aug 22 13:07:29 2005
Subject: [py-transports] PyMSNt 0.9.4 & 0.10 testing
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

I'm using jabberd2 with a patch for JEP-0153. 

See http://j2.openaether.org/bugzilla/show_bug.cgi?id=29 for the patch

If you want I have pre-built binaries for debian, look here:
http://www.darkskies.za.net/~norman/jabber/deb/

On 22/08/05, Arnaud Ab?lard <[EMAIL PROTECTED]> wrote:
> Lars T. Mikkelsen wrote:
> 
> > If your Jabber client supports JEP-0153 avatars (as Gajim 0.8 does) your
> > MSN contacts will see your avatar.
> 
> hum..i guess the server also has to support JEP-0153.. unfortunatly we
> are using jabberd2 which doesn't seem to support it...
> 
> what are the jabber servers supporting JEP-0153 ? ejabberd, i guess?
> 
> AA
> 
> >
> > Best regards,
> > Lars
> >
> > [1] http://modevia.com/pipermail/py-transports/2005-June/000672.html
> > _______________________________________________
> > py-transports mailing list
> > py-transports@blathersource.org
> > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
> 
> 
> --
> Arnaud Ab?lard
> Administrateur Syst?mes et R?seaux
> Facult? de Sciences et Techniques
> Universit? de Nantes
> _______________________________________________
> py-transports mailing list
> py-transports@blathersource.org
> 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]  Mon Aug 22 14:53:03 2005
From: [EMAIL PROTECTED] (Carlos Guzman)
Date: Mon Aug 22 14:53:27 2005
Subject: [py-transports] Keep original nickname in PyMSNt
Message-ID: <[EMAIL PROTECTED]>

Hello
 
Im developing a text only client for Jabber and using PyMSNt transfor
for connection to MSN, it works just fine but i wuld like to keep the
original MSN nickname of the users, what i intend to do is:
 
- Connect to MSN unsing PyMSNt keeping the original nickname
- Obtain this nickaname form jabber (i haven been able to get my own
vcard form the client)
- In case the user wants to, change the nickname informing what was the
original one
 
is this posible?, if so, how can it be done (maybe changing the
transport source)
 
Thanks in advance
 
Carlos Guzman
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://modevia.com/pipermail/py-transports/attachments/20050822/550f6dcb/attachment.htm
From [EMAIL PROTECTED]  Mon Aug 22 14:58:07 2005
From: [EMAIL PROTECTED] (Lars T. Mikkelsen)
Date: Mon Aug 22 14:58:22 2005
Subject: [py-transports] PyMSNt 0.9.4 & 0.10 testing
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

On Mon, Aug 22, 2005 at 02:40:03PM +0200, Arnaud Ab?lard wrote:
> getNextPacket (Avatar_Receive) [EMAIL PROTECTED] [EMAIL PROTECTED] 0
> Packed fields: 0x0 0xe1e20e 0x0 0x2a1 0x2a1 0x0 0x28523b9e 0x0 0x0 0x0
> processPacket [EMAIL PROTECTED] [EMAIL PROTECTED] 1
> Unpacked fields: 0x0L 0x2016CE17L 0x0L 0x2A1L 0x0L 0x2L 0xE1E20EL 0x0L 
> 0x2A1L 0x0L
> ERROR in avatar transfer:  <tlib.msnp2p.MSNP2P_Avatar_Receive instance 
> at 0xb754be0c> field7,0,676477854 in state: 1

Do you know if this contact is using Gaim? This looks a lot like a bug
in Gaim [1]. Do you get other errors not containing "field7,0" in the
error message?

Best regards,
Lars

[1] 
http://sourceforge.net/tracker/index.php?func=detail&aid=1222320&group_id=235&atid=100235
From [EMAIL PROTECTED]  Mon Aug 22 15:13:08 2005
From: [EMAIL PROTECTED] (=?UTF-8?B?QXJuYXVkIEFiw6lsYXJk?=)
Date: Mon Aug 22 15:13:11 2005
Subject: [py-transports] PyMSNt 0.9.4 & 0.10 testing
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>     <[EMAIL PROTECTED]>     
<[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

Lars T. Mikkelsen wrote:
> On Mon, Aug 22, 2005 at 02:40:03PM +0200, Arnaud Ab?lard wrote:
> 
>>getNextPacket (Avatar_Receive) [EMAIL PROTECTED] [EMAIL PROTECTED] 0
>>Packed fields: 0x0 0xe1e20e 0x0 0x2a1 0x2a1 0x0 0x28523b9e 0x0 0x0 0x0
>>processPacket [EMAIL PROTECTED] [EMAIL PROTECTED] 1
>>Unpacked fields: 0x0L 0x2016CE17L 0x0L 0x2A1L 0x0L 0x2L 0xE1E20EL 0x0L 
>>0x2A1L 0x0L
>>ERROR in avatar transfer:  <tlib.msnp2p.MSNP2P_Avatar_Receive instance 
>>at 0xb754be0c> field7,0,676477854 in state: 1
> 
> 
> Do you know if this contact is using Gaim? This looks a lot like a bug
> in Gaim [1]. Do you get other errors not containing "field7,0" in the
> error message?

yep, that's a gaim contact... i have some problem with users using 
trillian too...

not occurence of field7,0 in my debug.log file, though

> 
> Best regards,
> Lars
> 
> [1] 
> http://sourceforge.net/tracker/index.php?func=detail&aid=1222320&group_id=235&atid=100235
> _______________________________________________
> py-transports mailing list
> py-transports@blathersource.org
> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports


-- 
Arnaud Ab?lard
Administrateur Syst?mes et R?seaux
Facult? de Sciences et Techniques
Universit? de Nantes
From [EMAIL PROTECTED]  Mon Aug 22 16:29:43 2005
From: [EMAIL PROTECTED] (Gustavo Felisberto)
Date: Mon Aug 22 15:13:45 2005
Subject: [py-transports] PyMSNt 0.9.4 & 0.10 testing
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

Skipped content of type multipart/mixed-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
Url : 
http://modevia.com/pipermail/py-transports/attachments/20050822/2ffdcbee/signature.pgp
From [EMAIL PROTECTED]  Mon Aug 22 17:03:07 2005
From: [EMAIL PROTECTED] (Bertrand Rousseau)
Date: Mon Aug 22 17:03:16 2005
Subject: [py-transports] MSN contacts nickname in status message
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

As I could see, some of my MSN contacts have actually used this
"personal message" stuff, and then it is displayed as I like it.

Anyway, knowing about this "personal message" stuff now, I agree that
it is the good way to implement it.  The problem is on the side of the
msn messenger, so I will be pleased to answer people bothering me
because they tell me "you didn't read my nickname or what?" with
"sorry but you have to use the right function for that" :-).

Bertrand

On 8/22/05, Francisco Joaqu?n Rodr?guez Prados <[EMAIL PROTECTED]> wrote:
> 2005/8/22, Lars T. Mikkelsen <[EMAIL PROTECTED]>:
> > do agree, however, that many Messenger users have to learn to use the
> > personal message and not their nickname for status messages. :-)
> 
> Well, now the have the double space to write the fool things they used
> to write only in the nickname - at least that's what my friends are
> doing right now... XD
> 
> But yeah, I think so: this is the best way of merging the nickname and
> status message in Jabber-MSN.
> 
> --
> Francisco Joaqu?n Rodr?guez Prados
> Fachbereich Informatik,
> Fachhochschule Darmstadt,
> Darmstadt, Germany
> E-mail: [EMAIL PROTECTED]
> JID: [EMAIL PROTECTED]
> _______________________________________________
> py-transports mailing list
> py-transports@blathersource.org
> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
>
From [EMAIL PROTECTED]  Mon Aug 22 20:15:50 2005
From: [EMAIL PROTECTED] (James Bunton)
Date: Mon Aug 22 20:16:00 2005
Subject: [py-transports] PyMSNt 0.9.4 & 0.10 testing
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

Could you do `ls -1` on your spool dir so I can have a look at what  
files its trying to convert?

Thanks.

---

James



On 23/08/2005, at 2:29 AM, Gustavo Felisberto wrote:

> James Bunton wrote:
>
>> Hi everybody.
>>
>> I think that the avatars branch is just about stable enough to  
>> release.
>>
>> The latest CVS update brings a few fixes.
>> The main change is hashed spool and avatar directories.
>> Your current setup should be automatically migrated. Please back up
>> your spool directory before testing this. I don't anticipate any
>> problems though.
>>
>> If you have any troubles with this please let me know this week.
>> Unless there's any major troubles I'm planning a release next Monday
>> for PyMSNt 0.9.4 and 0.10.
>
> I was running the avatar branch with no problems, a couple of weeks ago
> i did a cvs up and now i get:
> ./PyMSNt
> Checking spool files and stringprepping any if necessary...
> Traceback (most recent call last):
>   File "main.py", line 298, in ?
>     housekeep.init()
>   File
> "/home/humpback/jabber/tanga/msn-transport/PyMSNt/src/housekeep.py",
> line  22, in init
>     noteListF[noteList.index(note)]()
>   File
> "/home/humpback/jabber/tanga/msn-transport/PyMSNt/src/housekeep.py",
> line  64, in doSpoolPrepCheck
>     filej = jid.JID(file).full()
>   File
> "/usr/lib/python2.3/site-packages/twisted/words/protocols/jabber/ 
> jid.py",
> line 104, in __init__
>     user, host, res = parse(str)
>   File
> "/usr/lib/python2.3/site-packages/twisted/words/protocols/jabber/ 
> jid.py",
> line 47, in parse
>     return prep(user, server, resource)
>   File
> "/usr/lib/python2.3/site-packages/twisted/words/protocols/jabber/ 
> jid.py",
> line 66, in prep
>     raise InvalidFormat, "Invalid character in hostname"
> twisted.words.protocols.jabber.jid.InvalidFormat: Invalid character in
> hostname
>
> I did a cvs up on my 0.9.3 dir and got the same problem. I'm attaching
> my config file (striped the password :) )
> Versions of software used:
>
> dev-lang/python-2.3.5
> dev-python/twisted-2.0.0
> dev-python/twisted-words-0.1.0
>
> -- 
> Gustavo Felisberto
> (HumpBack)
> Web: http://dev.gentoo.org/~humpback
> Blog: http://blog.felisberto.net/
> ------------
> It's most certainly GNU/Linux, not Linux. Read more at
> http://www.gnu.org/gnu/why-gnu-linux.html .
> -------------
>
> <pymsnt>
> <!-- This file contains options to be configured by the server  
> administrator. -->
> <!-- Please read through all the options in this file -->
>
> <!-- The JabberID of the transport -->
> <jid>msn.jabber.felisberto.net</jid>
>
>
> <!-- The location of the spool directory.. if relative, relative to  
> the PyMSNt dir.
> Do not include the jid of the transport -->
> <!-- <spooldir>/path/to/data</spooldir> -->
>
> <!-- The location of the PID file (if relative, relative to the PyMSNt  
> dir) -->
> <pid>PyMSNt.pid</pid>
>
>
> <!-- The IP address of the main Jabber server to connect to -->
> <mainServer>127.0.0.1</mainServer>
> <!-- The JID of the main Jabber server -->
> <mainServerJID>jabber.felisberto.net</mainServerJID>
> <!-- The website of the Jabber service -->
> <website>http://jabber.felisberto.net</website>
> <!-- The TCP port to connect to the Jabber server on (this is the  
> default for Jabberd2) -->
> <port>5349</port>
> <!-- The authentication token to use when connecting to the Jabber  
> server -->
> <secret>************</secret>
>
>
> <!-- The default language to use -->
> <lang>en</lang>
>
>
> <!-- Comment out the following options to disable them, or uncomment  
> them to enable them -->
> <!-- Send email notification messages to users -->
> <mailNotifications/>
> <!-- Send greeting on login -->
> <!-- <sessionGreeting>You have just started a session with  
> PyMSNt</sessionGreeting> -->
> <!-- Send message on successful registration -->
> <!-- <registerMessage>You have successfully registered with  
> PyMSNt</registerMessage> -->
> <!-- Allow users to register with this transport -->
> <allowRegister/>
>
>
> <!-- You can select which event loop PyMSNt will use. It's probably  
> safe to leave this as the default -->
> <!-- Use epoll for high-load Linux servers running kernel 2.6 or above  
> -->
> <!--<reactor>epoll</reactor>-->
>
> <!-- Use kqueue for high-load FreeBSD servers -->
> <!--<reactor>kqueue</reactor>-->
>
> <!-- Use poll for high-load Unix servers -->
> <!--<reactor>poll</reactor>-->
>
>
>
> <!-- HTTPS proxy settings. To use a proxy, set both these values -->
> <!--
> <proxyServer>someserver.com</proxyServer>
> <proxyPort>443</proxyPort>
> -->
>
> <!-- Set this to get debugging output -->
> <debugOn/>
> <!-- Set this to only get debugging output when a problem occurs. Only  
> applies if logging to a file -->
> <debugSmart/>
> <!-- Set the debug log file location here, (comment out to output to  
> the screen) -->
> <!-- (if relative, relative to the PyMSNt dir) -->
> <debugLog>debug.log</debugLog>
>
>
> </pymsnt>
> _______________________________________________
> py-transports mailing list
> py-transports@blathersource.org
> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports

Reply via email to