Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: double byte chars in From header
- To: tlug@example.com
- Subject: Re: double byte chars in From header
- From: Dmytro Kovalov <dmytro.kovalov@example.com>
- Date: Thu, 16 Nov 2000 11:40:13 +0900
- Content-Type: text/plain; charset=us-ascii
- In-Reply-To: Your message of "Thu, 16 Nov 2000 11:01:00 +0900." <14867.16348.326851.154914@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <nedi-B.A.tjH.dl0E6@example.com>
- Resent-Sender: tlug-request@example.com
vp@example.com said: -> =?ISO-2022-JP?B?GyRCJUAlUyVDJUklKCVJJSIlayVJGyhC?= -> Is it a VM problem? What does the standard say? Yes, that's a standard. Try playing with MM_CHARSET variable. export MM_CHARSET=koi8-u (this is what I have). If I get mail with any of the headers encoded as: =?koi8-u?... they all understood by mh's scan. Unfortunately, I don't have any idea how to make it to understand more than one charset (in headers, not body). Even if I get header with 'koi8-r' (JFYI: koi8-u is a superset of koi8-r) with such setting I can't see such header ;( -- Dmytro
- References:
- double byte chars in From header
- From: Viktor Pavlenko <vp@example.com>
Home | Main Index | Thread Index
- Prev by Date: double byte chars in From header
- Next by Date: double byte chars in From header
- Prev by thread: double byte chars in From header
- Next by thread: double byte chars in From header
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links