From xemacs-m  Wed Mar  5 18:45:01 1997
Received: from crystal.WonderWorks.COM (crystal.WonderWorks.com [192.203.206.1])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id SAA15564
	for <xemacs-beta@xemacs.org>; Wed, 5 Mar 1997 18:44:59 -0600 (CST)
Received: by crystal.WonderWorks.COM 
	id QQcfpx17765; Wed, 5 Mar 1997 19:25:23 -0500 (EST)
Date: Wed, 5 Mar 1997 19:25:23 -0500 (EST)
Message-Id: <QQcfpx17765.199703060025@crystal.WonderWorks.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Kyle Jones <kyle_jones@wonderworks.com>
To: xemacs-beta@xemacs.org
Subject: charset unrecognized
In-Reply-To: <87hgiqnjmc.fsf@sbt.net>
References: <87hgiqnjmc.fsf@sbt.net>
X-Face: /cA45WHG7jWq>(O3&Z57Y<"WsX5ddc,4c#w0F*zrV#=M
        0@~@,s;b,aMtR5Sqs"+nU.z^CSFQ9t`z2>W,S,]:[+2^
        Nbf6v4g>!&,7R4Ot4Wg{&tm=WX7P["9%a)_da48-^tGy
        ,qz]Z,Zz\{E.,]'EO+F)@$KtF&V

Michael Harnois writes:
 > Why'd this charset come through as unrecognized?
 > 
 > >From: =?UNKNOWN-8BIT?Q?J=F6rgen?= Sigvardsson <Jorgen.Sigvardsson@wermland.se>

UNKNOWN-8BIT is used as a charset when 8-bit text is encountered
in a message without an accompanying MIME character set
declaration.  8-bit data is forbidden to appear in the headers of
Internet messages.  So I suspect some trasnport agent did
8->7-bit conversion of the headers on the fly and used
UNKNOWN-8BIT as the charset because it had no choice.

