[Top] [All Lists]

Forwarding: dropped mail

1991-07-22 14:37:51
This message was not delivered due to problems at our site. It is being resent.
The following is a copy of the message:

Received: from (-:RUTGERS.EDU:-) by via TCP 
with SMTP id AA24153; Thu, 11 Jul 91 11:48:59 EDT
Received: from by (5.59/SMI4.0/RU1.4/3.08) 
        id AA21308; Thu, 11 Jul 91 11:47:31 EDT
Received: by (5.59/SMI4.0/RU1.4/3.08) 
        id AA28981; Thu, 11 Jul 91 11:07:27 EDT
Received: from uvaarpa.Virginia.EDU by 
        id AA28977; Thu, 11 Jul 91 11:07:24 EDT
Received: from uvacs.cs.Virginia.EDU by uvaarpa.Virginia.EDU id aa11809;
          11 Jul 91 11:07 EDT
Received: from phil.cs.Virginia.EDU by uvacs.cs.Virginia.EDU (4.1/5.1.UVA)
        id AA07597; Thu, 11 Jul 91 11:06:28 EDT
Posted-Date: Thu, 11 Jul 91 11:06:48 EDT
Return-Path: <rja7m(_at_)phil(_dot_)cs(_dot_)Virginia(_dot_)EDU>
Received: by phil.cs.Virginia.EDU (4.1/SMI-2.0)
        id AA04471; Thu, 11 Jul 91 11:06:48 EDT
Date: Thu, 11 Jul 91 11:06:48 EDT
From: rja7m(_at_)phil(_dot_)cs(_dot_)virginia(_dot_)edu
In-Reply-To: Nathaniel Borenstein <nsb(_at_)thumper(_dot_)bellcore(_dot_)com>
       "Re: charset philosophy" (Jul 11,  9:34am)
X-Mailer: Mail User's Shell (7.2.3 5/22/91)
To: ietf-822(_at_)dimacs(_dot_)rutgers(_dot_)edu
Subject: Re: EBCDIC on the Internet

  It seems to me that the world of EBCDIC-only mail isn't really part
of the Internet proper (since RFC822 requires US ASCII).  The thing to
do would maybe be to not explicitly include a Content-type
text/us-ebcdic and instead leave that to agreement amongst the "local
enclave" of EBCDIC users.

  I think that if anything is said, it should be made explicit that
EBCDIC hosts talking to US-ASCII hosts have to talk US-ASCII across
the SMTP link.  In other words, the burden of ASCII-EBCDIC
transformation should always be with the EBCDIC gateway host.

  It would be a bad thing if messages encoded in EBCDIC suddenly
showed up on the rest of the net...