Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [tlug] 文字化け problem
- Date: Thu, 13 Feb 2020 10:46:26 +0900
- From: Jim Blackson <blackson@example.com>
- Subject: Re: [tlug] 文字化け problem
- References: <97b27fe7-b159-b117-8252-5cea8f6b9e5e@sonic.net>
On 2020-02-10 09:19 -0800 (Mon), steve wrote: > I've been having a problem with mail from TLUG since about June of last > year. I also have seen this problem. First garbled message was the [tlug] [announcement] Nomikai - June 14th, 2019 sent by "Justin" <tlug@example.com>. The header included the lines: Content-Type: text/plain; charset="utf-8" ... Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by altair.a1d.local id x549aTJA090625 This same message received on the TLUG-Admin list had a different encoding: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit > The first instance I show a problem was in a message dated 6/3/2019 with the > subject:'[tlug] Books for free' but I don't save all threads from Joe > Larabell <joe@example.com>. ... That message came through OK for me. Header shows Content-Type: multipart/mixed; apparently containing text and html. The last garbled message I have is from Charles Muller <acmuller@example.com> dated Thu, 24 Oct 2019 12:07:30 +0900: [tlug] Providing usage data stats for web service subscribers My mail client is Becky! running on Windows 7 Pro, connecting to company internal mail server. Hope this helps, jimb. Jim Blackson, A1Data Corp.
- Follow-Ups:
- Re: [tlug] 文字化け problem
- From: Jim Breen
- References:
- [tlug] 文字化け problem
- From: steve
Home | Main Index | Thread Index
- Prev by Date: Re: [tlug] A Test Message in Japanese
- Next by Date: Re: [tlug] 文字化け problem
- Previous by thread: Re: [tlug] 文字化け problem
- Next by thread: Re: [tlug] 文字化け problem
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links