Hi Trejkaz! Trejkaz schrieb:
>>The hostname is msn.jabber_server. >>And the jabber server's name is jabber_server. >>The both names can't be resolved by DNS. Is this the reason of error or >>any others? >> >> >Underscores are not legal in hostnames. That may explain the problem... > > I'd say they are ? you just cannot register them below the traditional top level domains. Tot kijk Matthias From [EMAIL PROTECTED] Mon Dec 19 11:59:58 2005 From: [EMAIL PROTECTED] (Bao Jianyi) Date: Mon Dec 19 11:59:39 2005 Subject: [py-transports] Exception "Invalid character in hostname" Message-ID: <[EMAIL PROTECTED]> I changed the hostname to ipaddress.(replace the jabber_server with = ipaddress) And the pymsnt is working. Best Regards, Bao Jianyi -----Original Message----- From: [EMAIL PROTECTED] = [mailto:[EMAIL PROTECTED] On Behalf Of Matthias = Wimmer Sent: 2005=C4=EA12=D4=C219=C8=D5 19:40 To: PyAIM-t/PyICQ-t/PyMSN-t Discussion Subject: Re: [py-transports] Exception "Invalid character in hostname" Hi Trejkaz! Trejkaz schrieb: >>The hostname is msn.jabber_server. >>And the jabber server's name is jabber_server. >>The both names can't be resolved by DNS. Is this the reason of error = or >>any others? >> =20 >> >Underscores are not legal in hostnames. That may explain the = problem... > =20 > I'd say they are =A1=AD you just cannot register them below the = traditional=20 top level domains. Tot kijk Matthias _______________________________________________ py-transports mailing list [email protected] http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports From [EMAIL PROTECTED] Mon Dec 19 22:31:18 2005 From: [EMAIL PROTECTED] (Lars T. Mikkelsen) Date: Mon Dec 19 22:31:23 2005 Subject: [py-transports] PyMSNt: Messages from MSN users are bounced on errors In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> On Tue, Nov 15, 2005 at 11:04:22AM +1100, James Bunton wrote: > I'll just bounce them with a prefix. On second thought, I think it will be better to destroy the session (i.e. to disconnect the user) instead. As we can't completely imitate the "The following message could not be delivered" error message in the official client, I think some contacts will get confused, especially those using a non-English client (I assume that it isn't possible to localize the prefix according to the language of the contact's MSN Messenger). As the official client doesn't guarantee delivery of messages (as far as I know), it makes sense to simply disconnect the user on errors. I think it's common on MSN Messenger, that if you send a message to a contact who goes offline shortly after, you are not sure if he got the message or not. Finally, I've never experienced stand-alone message delivery errors on Jabber. The errors are most often due to a crashed server or broken S2S. Hence, if one message fails, the next messages are likely to fail too. Actually, I would also suggest to disconnect the users on failed presence packets. Best regards, Lars From [EMAIL PROTECTED] Fri Dec 23 22:18:15 2005 From: [EMAIL PROTECTED] (James Bunton) Date: Fri Dec 23 22:18:29 2005 Subject: [py-transports] PyMSNt: Messages from MSN users are bounced on errors In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> On 20/12/2005, at 9:31 AM, Lars T. Mikkelsen wrote: > On Tue, Nov 15, 2005 at 11:04:22AM +1100, James Bunton wrote: >> I'll just bounce them with a prefix. > > On second thought, I think it will be better to destroy the session > (i.e. to disconnect the user) instead. As we can't completely imitate > the "The following message could not be delivered" error message in the > official client, I think some contacts will get confused, especially > those using a non-English client (I assume that it isn't possible to > localize the prefix according to the language of the contact's MSN > Messenger). > > As the official client doesn't guarantee delivery of messages (as far > as > I know), it makes sense to simply disconnect the user on errors. I > think > it's common on MSN Messenger, that if you send a message to a contact > who goes offline shortly after, you are not sure if he got the message > or not. > > Finally, I've never experienced stand-alone message delivery errors on > Jabber. The errors are most often due to a crashed server or broken > S2S. > Hence, if one message fails, the next messages are likely to fail too. > Actually, I would also suggest to disconnect the users on failed > presence packets. > > Best regards, > Lars I think you're right. The transport will disconnect if it receives any message errors. --- James
