[jdev] Re: Problem with PyMSN-t

Thu Jun 23 15:34:06 CDT 2005

Hi,

I'm using Pandion. But I've tested with Exodus too and occured the same 
problem.

The tcp connection between PyMSNt and JM is established correctly (I've 
confirmed this with netstat).

the traffic is:

SENT: <message type="chat" id="sd51" 
to="tgbremen%yahoo.com at msn.quimera.sjes.gov.br" 
from="jespdb at sjes.gov.br/Pandion"><body>asdas</body><html 
xmlns="http://jabber.org/protocol/xhtml-im"><body 
xmlns="http://www.w3.org/1999/xhtml"><span style="font-weight: normal; 
font-size: 9pt; color: #004200; font-style: normal; font-family: 
arial">asdas</span></body></html><x 
xmlns="jisp:x:jep-0038"><name>megapack</name></x><active 
xmlns="http://jabber.org/protocol/chatstates"/></message>
RECV: <message xmlns="jabber:component:accept" 
to="jespdb at sjes.gov.br/Pandion" 
from="tgbremen%yahoo.com at msn.quimera.sjes.gov.br" type="error"><error 
code="405" type="wait"><not-allowed 
xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"></not-allowed><text 
xmlns="urn:ietf:params:xml:ns:xmpp-stanzas">Sorry, this message cannot 
be delivered yet. Please try again when the transport has finished 
logging in.</text></error><body>asdas</body></message>

Gaston Dombiak wrote:

>Hey Patrick,
>
>I'm using PyMSNt with JM. However, I failed to start up PyAIMt. :(
>
>Which client are you using? I'm using Exodus for my tests. If you want you 
>can try connecting to my local server just to isolate the variables and 
>confirm that it's not a client issue.
>
>Regards,
>
>  -- Gato
>
>
>"Patrick Dalla Bernardina" <patrick at jfes.trf2.gov.br> wrote in message 
>news:42B9CE4B.2070100 at jfes.trf2.gov.br...
>  
>
>>Hi,
>>
>>does anybody uses JIVE with PyMSNt or PyAIMt?
>>
>>I couldn't make them work..
>>
>>Every message I sent to an MSN or AIM user I receive a response that it is 
>>necessary to log in the transport. But I have already registered and 
>>entered my credentials
>>
>>How do I do this?
>>
>>
>>Tim Fulcher - Clickatell wrote:
>>
>>    
>>
>>>Hi All
>>>I've been seating with this for a few days now. After finally succeeding
>>>to complile both mu-conference 0.6.0 and yahoo-transport 2.3.2 I run
>>>into a segfault problem on yahoo-transport. Looking into the problem I
>>>noticed that, with the exception of the "component" call both mu and
>>>yahoo's main.c are identical (well that shouldn't be a surprise!). The
>>>error occurs when the g_main_loop_run procedure is called. But the
>>>segfault does not manifest itself if I comment out the
>>>jcr_main_new_stream proc.
>>>Is this a common fault and if so how can it be fixed?
>>>I have attached both logs:
>>>mu-conference:
>>>main.c:148 (main): Jabber Component Runtime -- 0.2.4 starting.
>>>
>>>main.c:194 (main): Main loop starting.
>>>
>>>jcr_main_stream_error.c:50 (jcr_main_new_stream): Server stream
>>>connected.
>>>
>>>jcr_deliver.c:51 (jcr_queue_deliver): packet delivery thread starting.
>>>
>>>jcr_shutdown.c:43 (jcr_server_shutdown): Server shutting down
>>>
>>>jcr_deliver.c:97 (jcr_queue_deliver): packet delivery thread exiting.
>>>
>>>jcr_deliver.c:98 (jcr_queue_deliver): Last DvryQ Buffer=''
>>>
>>>
>>>Yahoo-Transport:
>>>
>>>main.c:148 (main): Jabber Component Runtime -- 0.2.4 starting.
>>>
>>>yahoo.localhost: Yahoo! Transport v2.3.2-JCR [stable] starting.
>>>
>>>jcr_base_connect.c:34 (jcr_socket_connect): Attempting connection to
>>>127.0.0.1:5347
>>>
>>>main.c:194 (main): Main loop starting.
>>>
>>>jcr_base_connect.c:34 (jcr_socket_connect): Attempting connection to
>>>127.0.0.1:5347
>>>
>>>jcr_base_connect.c:81 (jcr_send_start_stream): Opening XML stream: sent
>>>161 bytes
>>>
>>>jcr_main_stream_error.c:50 (jcr_main_new_stream): Server stream
>>>connected.
>>>
>>>jcr_deliver.c:51 (jcr_queue_deliver): packet delivery thread starting.
>>>
>>>jcr_deliver.c:92 (jcr_queue_deliver): wrote 1 packets of 63 bytes
>>>
>>>jcr_elements.c:177 (jcr_read_data): Main Channel Error: rc=2
>>>
>>>jcr_main_stream_error.c:56 (jcr_main_close_stream): Server stream error,
>>>resetting
>>>
>>>jcr_deliver.c:97 (jcr_queue_deliver): packet delivery thread exiting.
>>>
>>>jcr_deliver.c:98 (jcr_queue_deliver): Last DvryQ Buffer=''
>>>
>>>jcr_base_connect.c:34 (jcr_socket_connect): Attempting connection to
>>>127.0.0.1:5347
>>>
>>>jcr_base_connect.c:81 (jcr_send_start_stream): Opening XML stream: sent
>>>161 bytes
>>>
>>>jcr_main_stream_error.c:50 (jcr_main_new_stream): Server stream
>>>connected.
>>>
>>>jcr_deliver.c:51 (jcr_queue_deliver): packet delivery thread starting.
>>>
>>>jcr_deliver.c:92 (jcr_queue_deliver): wrote 1 packets of 63 bytes
>>>
>>>jcr_elements.c:177 (jcr_read_data): Main Channel Error: rc=2
>>>
>>>jcr_main_stream_error.c:56 (jcr_main_close_stream): Server stream error,
>>>resetting
>>>
>>>jcr_deliver.c:97 (jcr_queue_deliver): packet delivery thread exiting.
>>>
>>>jcr_deliver.c:98 (jcr_queue_deliver): Last DvryQ Buffer=''
>>>
>>>TIA
>>>Tim Fulcher
>>>_______________________________________________
>>>jdev mailing list
>>>jdev at jabber.org
>>>http://mail.jabber.org/mailman/listinfo/jdev
>>>
>>>
>>>      
>>>
>
>
>
>_______________________________________________
>jdev mailing list
>jdev at jabber.org
>http://mail.jabber.org/mailman/listinfo/jdev
>
>  
>