Op dinsdag 11 oktober 2005 15:27, schreef Renato Botelho:
> Hello
>
> I have a ejabberd-0.9.8 and trying to use pyICQt-0.6, but I'm having
> some problems, here is pyICQt debug log

Not sure if you are experiencing the same problem, but recently someone had a 
problem with PyMSNt. The problem that caused him much headaches was this:

He didn't changed:
<!-- The JabberID of the transport -->
<jid>msn</jid>

into:
<!-- The JabberID of the transport -->
<jid>msn.yourserver.com</jid>

HTH

-- 
Mvg, Sander Devrieze.
xmpp:[EMAIL PROTECTED]

ejabberd, the expandable Jabber daemon. --
http://ejabberd.jabber.ru/
From [EMAIL PROTECTED]  Tue Oct 11 22:43:31 2005
From: [EMAIL PROTECTED] (Andreas van Cranenburgh)
Date: Tue Oct 11 22:43:35 2005
Subject: [py-transports] ejabberd + pyICQt problems
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

On Wed, Oct 12, 2005 at 12:40:36AM +0200, Sander Devrieze wrote:
> He didn't changed:

You mean "he changed", :P

> <!-- The JabberID of the transport -->
> <jid>msn</jid>
> 
> into:
> <!-- The JabberID of the transport -->
> <jid>msn.yourserver.com</jid>

When I switched to ejabberd, I did the same thing. But I didn't do it to
fix a problem, just because it's nice to share your transport with the
world. (Eg. now, because I'm the only one that has chatstate support I
believe :) )

-- 
        Andreas        [ http://unstable.nl | xmpp:[EMAIL PROTECTED] ]
                       [  callto:ils.seconix.com/[EMAIL PROTECTED]   ]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : 
http://modevia.com/pipermail/py-transports/attachments/20051012/5aea48de/attachment.pgp
From [EMAIL PROTECTED]  Tue Oct 11 22:55:43 2005
From: [EMAIL PROTECTED] (Sander Devrieze)
Date: Tue Oct 11 22:55:47 2005
Subject: [py-transports] ejabberd + pyICQt problems
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

Op woensdag 12 oktober 2005 00:43, schreef Andreas van Cranenburgh:
> On Wed, Oct 12, 2005 at 12:40:36AM +0200, Sander Devrieze wrote:
> > He didn't changed:
>
> You mean "he changed", :P

No, he didn't; he only changed it after a long time :-p

<snip>

-- 
Mvg, Sander Devrieze.
xmpp:[EMAIL PROTECTED]

ejabberd, the expandable Jabber daemon. --
http://ejabberd.jabber.ru/
From [EMAIL PROTECTED]  Tue Oct 11 23:08:33 2005
From: [EMAIL PROTECTED] (Andreas van Cranenburgh)
Date: Tue Oct 11 23:08:37 2005
Subject: [py-transports] ejabberd + pyICQt problems
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

On Wed, Oct 12, 2005 at 12:55:43AM +0200, Sander Devrieze wrote:
> Op woensdag 12 oktober 2005 00:43, schreef Andreas van Cranenburgh:
> > On Wed, Oct 12, 2005 at 12:40:36AM +0200, Sander Devrieze wrote:
> > > He didn't changed:
> >
> > You mean "he changed", :P
> 
> No, he didn't; he only changed it after a long time :-p

Haha, my mistake. I thought you referred to the guy who actually fixed
it. The ambiguity of language.... (www.lojban.org comes to mind :) )

-- 
        Andreas        [ http://unstable.nl | xmpp:[EMAIL PROTECTED] ]
                       [  callto:ils.seconix.com/[EMAIL PROTECTED]   ]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : 
http://modevia.com/pipermail/py-transports/attachments/20051012/92dd23e0/attachment.pgp
From [EMAIL PROTECTED]  Thu Oct 13 15:00:56 2005
From: [EMAIL PROTECTED] (Sascha)
Date: Thu Oct 13 15:01:04 2005
Subject: [py-transports] extended informations and functionality from
        original messengers?
Message-ID: <[EMAIL PROTECTED]>

is there a way in py transports to receive information about a file 
transfer... or even videoconferencing started from the original MSN 
messenger

i dont know how msn send the data but i tested and saw that i dont have 
any kind of message when i try to send a file from my original MSN 
messenger to my Jabber client.. on the clientside i have no kind XML output.

AND it would be interesting for me to know about other functions that 
are not just textbased, also the fonttype and fontcolor of my 
(messenger)-partner etc...

is there a way to receive or access these informations?

greetz

Reply via email to