Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: tlug-digest V1 #298
- To: tlug@example.com
- Subject: Re: tlug-digest V1 #298
- From: "A.Tomita,Jr." <Alberto@example.com>
- Date: Thu, 26 Sep 1996 13:49:22 +0900
- Content-Type: text/plain; charset=ISO-2022-JP
- In-reply-to: Your message of "Wed, 25 Sep 1996 17:00:10 GMT." <199609251700.RAA23832@example.com>
- Reply-To: tlug@example.com
- Sender: owner-tlug
In message <199609251700.RAA23832@example.com> you wrote: > From: turnbull@example.com (Stephen J. Turnbull) > Date: Wed, 25 Sep 96 10:02 JST > Subject: Re: 日本語のSubject line ... > A sample Nihongo header follows: > > >From: =?ISO-2022-JP?B?GyRCQG4wZhsoSg==?= <mkawai@example.com> > >Date: Mon, 23 Sep 1996 19:24:37 -0000 > >Subject: [ISSHO-J: 98] Why ISSHO for me > > and one with the subject in Japanese: > > >From: Kiyoshi Adachi <BXH05371@example.com> > >Date: Sat, 21 Sep 1996 10:15:00 +0900 > >Subject: [ISSHO-J: 95] =?ISO-2022-JP?B?GyRCNmU9IyRORT41b0BoGyhC?= > > Note the MIME/quoted-printable encoding. This is required for > compliance to the relevant RFCs. All mail transfer agents that I know > of mung the headers. Usually not the Subject header, of course, but > they do add "received" and "message-id" and "x-authentication" and so > on. Many of them do this with non-8-bit clean code (often located in > old versions of system libraries; it's not necessarily the MTA's > fault), so in that case even the "untouched" headers can get trashed. > I think it's RFC822 (maybe RFC821) that specifies that the header > section must be in 7-bit ASCII. Check out RFC-MIME (I think it's > 1463?) for that. According to CJK.INF, it's RFC 1521 and 1522: "MIME (Multipurpose Internet Mail Extensions) Parts One and Two: Mechanisms for Specifying and Describing the Format of Internet Message Bodies," by Nathaniel Borenstein and Ned Freed, September 1993. Another relevant one is RFC 1468: "Japanese Character Encoding for Internet Messages," by Jun Murai et al., June 1993. CJK.INF has some details on how MIME encoding is performed, and lots of other useful info. You may want to take a look at it: CJK.INF Version 2.1 (July 12, 1996) Copyright (C) 1995-1996 Ken Lunde. All Rights Reserved. ftp://ftp.ora.com/pub/examples/nutshell/ujip/doc/cjk.inf BTW, TLUG is listed in the Appendix, under "Mailing Lists": TLUG (Tokyo Linux User's Group) Mailing List majordomo@example.com tlug@example.com > Still think it's worth it? I don't know whether Issho does the > MIME-encoding or if everybody is just using a compliant mailer.... It's the later. Running the ML with Listprocessor, there's not much to be done at the server's side. It depends mostly on the subscriber's set up being MIME-complaint. --- Alberto Tomita, Jr. http://www.ishiilab.dnj.ynu.ac.jp/~Alberto e-mail: alberto@example.com ----------------------------------------------------------------- a word from the sponsor will appear below ----------------------------------------------------------------- TLUG September 28th meeting is sponsored by Fusion Systems Japan, Inc., a global professional services firm. http://www.fsj.co.jp No. 2 Toshin Aobadai Building 9F, 3-17-13 Aobadai, Meguro-ku, Tokyo 153, Japan Tel: (03)5456-7561 Fax: (03)5458-4422 info@example.com
Home | Main Index | Thread Index
- Prev by Date: More imagemaps and HTTPd
- Next by Date: Saturday Meeting Place
- Prev by thread: More imagemaps and HTTPd
- Next by thread: Saturday Meeting Place
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links