RE: Abuse notification in Chinese (was:black hat .cn networks)
GB2312 is working on my system (not on your quoted text, but on the original as it came back to me posted to the list). I know nearly nothing about encoding, so I check with the translator and she confirmed that it was done in that. If that's not working for everyone, somebody give me a better idea of how to post it. Daryl -----Original Message----- From: hardie@equinix.com [mailto:hardie@equinix.com] Sent: Wednesday, May 09, 2001 12:22 PM To: Daryl G. Jurbala Cc: nanog@merit.edu Subject: Re: Abuse notification in Chinese (was:black hat .cn networks) Daryl, I don't see these as valid hanzi when viewed as GB2312, BIG5, or EUC-TW, the three most common encodings I'm aware of (mainland, Hong Kong, and Taiwan, respectively). Can you indicate what encoding these are in? regards, Ted Hardie
For what it's worth, here are two pretty generic messages that you can send, translated into Chinese (In Chinese Simplified -HZ encoding).
-----
Dear <Abusive Autonomous System>, The following unsolicited email appears either to have originated on and/or traversed your network, or to have come from a client of yours. If you simply have an open mail relay, please fix it. Please look into this. Regards,
親愛的ä¸çŸ¥å的系統ï¹
　以下ä¸æ˜Žä¿¡ä»¶é¡¯ç¤ºå‡ºå®ƒä¾†è‡ªäºŽæˆ–發é€åˆ°è²´ç¶²çµ¡ï¹æˆ–æ ˜¯ä¾†æºäºŽè²´ç¶²çµ¡çš„æŸä¸€å®¢å®¢'簟Ｈ缛裟阌? open email relayï¹èª¢OE⑺î›æ‹šîŠ?
è¬è¬!
------
Dear <Abusive Autonomous System>, A system on my network was attacked or compromised by a system appearing to originate from your network. Below you will find relevant log entries and other information I have on this issue. Your immediate attention in resolving this matter is necessary and appreciated. Regards,
親愛的ä¸çŸ¥å的系統ï¹
我蘘網絡系統被貴網絡系統侵入或是兼容。我已OEâ‘¾åš “Pçš„log entries
和其它信æ¯åˆ—放在下é¢ã€‚若貴網能盡快解>Qæ¤ä¸€?-é¡Œï¹æˆ ‘'fOEâ‘·f分感è¬ã€‚
------
Daryl G. Jurbala Infrastrucutre Manager Silverchair Science + Commuications 215.823.5077 http://www.silverchair.com
Daryl, It's actually in UTF-8 encoding. Somehow I missed the charset part of the mime type in the original headers: Delivered-To: nanog-outgoing@merit.edu Received: by segue.merit.edu (Postfix, from userid 56) id B1B485FA2B; Wed, 9 May 2001 11:37:14 -0400 (EDT) Received: from exchange.olympus.ctv.com (unknown [192.102.244.27]) by segue.merit.edu (Postfix) with ESMTP id ABCA45FC81 for <nanog@merit.edu>; Wed, 9 May 2001 11:26:29 -0400 (EDT) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Subject: Abuse notification in Chinese (was:black hat .cn networks) X-MimeOLE: Produced By Microsoft Exchange V6.0.4418.65 Date: Wed, 9 May 2001 11:21:56 -0400 Message-ID: <7F9129AC1C69A148AB8AC2A418AD58E70C4F11@exchange.olympus.ctv.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Abuse notification in Chinese (was:black hat .cn networks) Thread-Index: AcDX10McqQaO/ybXTr2Ra8HWoTp+rQAxCfJw From: "Daryl G. Jurbala" <DJurbala@Antiphony.com> To: <nanog@merit.edu> Sender: owner-nanog@merit.edu When I render it as UTF-8, the text is composed of valid simplified chinese characters. It may be that your mailer (exchange V6, apparently) is converting it to UTF-8 from whatever encoding you are composing in. As you no doubt know, GB2312 will be most widely understood as an encoding in Mainland China, so disabling that conversion will probably a good idea. regards, Ted Hardie
GB2312 is working on my system (not on your quoted text, but on the original as it came back to me posted to the list). I know nearly nothing about encoding, so I check with the translator and she confirmed that it was done in that.
If that's not working for everyone, somebody give me a better idea of how to post it. Daryl
-----Original Message----- From: hardie@equinix.com [mailto:hardie@equinix.com] Sent: Wednesday, May 09, 2001 12:22 PM To: Daryl G. Jurbala Cc: nanog@merit.edu Subject: Re: Abuse notification in Chinese (was:black hat .cn networks)
Daryl, I don't see these as valid hanzi when viewed as GB2312, BIG5, or EUC-TW, the three most common encodings I'm aware of (mainland, Hong Kong, and Taiwan, respectively). Can you indicate what encoding these are in? regards, Ted Hardie
For what it's worth, here are two pretty generic messages that you can send, translated into Chinese (In Chinese Simplified -HZ encoding).
-----
Dear <Abusive Autonomous System>, The following unsolicited email appears either to have originated on and/or traversed your network, or to have come from a client of yours. If you simply have an open mail relay, please fix it. Please look into this. Regards,
親æââºÃ§Å¡âä¸Â知åÂÂçšâ系統ï¹Â
ãâ¬â¬Ã¤Â»Â¥Ã¤Â¸â¹Ã¤Â¸Âæˎ信件顯示åâ¡ÂºÃ¥Â®Æä¾â èâ¡ÂªÃ¤ÂºÅ½Ã¦Ëâçâ¢Â¼Ã©â¬Âå˰貴網絡ï¹ÂæËâæ ˯ä¾â æºÂ于貴網絡çšâæŸÂä¸â¬Ã¥Â®Â¢Ã¥Â®Â¢'簟Ｈç¼âºÃ¨Â£Å¸Ã©ËÅ? open email relayï¹Â誢OEââºîÂâºÃ¦â¹Å¡Ã®ÂÅ ?
è¬Âè¬Â!
------
Dear <Abusive Autonomous System>, A system on my network was attacked or compromised by a system appearing to originate from your network. Below you will find relevant log entries and other information I have on this issue. Your immediate attention in resolving this matter is necessary and appreciated. Regards,
親æââºÃ§Å¡âä¸Â知åÂÂçšâ系統ï¹Â
æËâèËË網絡系統被貴網絡系統侵åâ¦Â¥Ã¦Ëâæ˯åâ¦Â¼Ã¥Â®Â¹Ã£â¬âæËâå·²OEââ¾åš âPçšâlog entries
Ã¥âÅÃ¥â¦Â¶Ã¥Â®Æä¿¡æ¯åËâæâ¾åŨä¸â¹Ã©Â¢ãâ¬âèâ¹Â¥Ã¨Â²Â´Ã§Â¶Â²Ã¨Æ½çâºÂ¡Ã¥Â¿Â«Ã¨Â§Â£>Qæ¤ä¸â¬?-é¡Åï¹ÂÃ¦Ë â'fOEââ·fÃ¥Ëâ æâŸè¬Âãâ¬â
------
Daryl G. Jurbala Infrastrucutre Manager Silverchair Science + Commuications 215.823.5077 http://www.silverchair.com
Hardie;
When I render it as UTF-8, the text is composed of valid simplified chinese characters. It may be that your mailer (exchange V6, apparently) is converting it to UTF-8 from whatever encoding you are composing in. As you no doubt know, GB2312 will be most widely understood as an encoding in Mainland China, so disabling that conversion will probably a good idea.
Various people in various places in the world are using various encoding schemes for various purposes. Unicode was an attempt to unify them. Microsoft contributed a lot. As usual, the attempt resulted in additional several encoding schemes (such as UTF-8, UTF-16) none of which is useful for any purpose. Honest people have already abandoned it. The rest are now working on unifying localization schemes of domain names, which is wrongly labeled as IDN (Internationalized Domain Name). Use GB2312 with EUC, if you want to communicate with people in mainland China. Masataka Ohta PS Japanese use ISO-2022-JP encoding for email only. Though hosts support their host-local encoding, ISO-2022-JP is the encoding for email. Situationis worse with WWW.
Daryl, It's actually in UTF-8 encoding. Somehow I missed the charset part of the mime type in the original headers:
AS ISO-2022-JP is compatible with other ISO 2022 based encoding scheme such as ASCII, we don't need MIME and its charset label.
participants (3)
-
Daryl G. Jurbala -
hardie＠equinix.com -
Masataka Ohta