Andre' PIRARD <PIRARD@vm1.ulg.ac.be> Tue, 13 February 1996 11:21 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa11743; 13 Feb 96 6:21 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa11739; 13 Feb 96 6:21 EST
Received: from list.cren.net by CNRI.Reston.VA.US id aa04957; 13 Feb 96 6:21 EST
Received: from localhost (localhost [127.0.0.1]) by list.cren.net (8.6.12/8.6.12) with SMTP id FAA12283; Tue, 13 Feb 1996 05:44:06 -0500
Received: from dimacs.rutgers.edu (root@dimacs.rutgers.edu [128.6.75.16]) by list.cren.net (8.6.12/8.6.12) with ESMTP id FAA12180 for <ietf-822@list.cren.net>; Tue, 13 Feb 1996 05:41:15 -0500
Received: from vm1.ulg.ac.be (vm1.ulg.ac.be [139.165.32.1]) by dimacs.rutgers.edu (8.6.12+bestmx+oldruq+newsunq+grosshack/8.6.12) with SMTP id FAA23511 for <ietf-822@dimacs.rutgers.edu>; Tue, 13 Feb 1996 05:40:59 -0500
Received: from BLIULG11 by vm1.ulg.ac.be (IBM VM SMTP V2R2) with BSMTP id 5967; Tue, 13 Feb 96 11:39:52 +0100
Received: from vm1.ulg.ac.be (PIRARD) by BLIULG11 (Mailer R2.10 ptf000) with BSMTP id 0036; Tue, 13 Feb 96 11:39:51 +0100
Message-Id: <199602131040.FAA23511@dimacs.rutgers.edu>
Date: Tue, 13 Feb 96 10:11:55 +0100
X-Orig-Sender: owner-ietf-822@list.cren.net
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Andre' PIRARD <PIRARD@vm1.ulg.ac.be>
To: Keith Moore <moore@cs.utk.edu>, Olle Jrnefors <ojarnef@admin.kth.se>, Patrik Fltstrm <paf@nada.kth.se>, Nathaniel Borenstein <nsb@thumper.bellcore.com>, nick@secant.com, Dave Crocker <dcrocker@networking.stanford.edu>, Greg Vaudreuil <gvaudre@CNRI.Reston.VA.US>, Ned.Freed@en.com
Cc: ietf-822@dimacs.rutgers.edu, paf@comsol.se
In-Reply-To: Message of Sun, 11 Feb 96 23:42:09 0500 from <moore@cs.utk.edu>
X-Truncated: *NOTE* Lines longer than 80 have been truncated. The longest line contained 0 characters
X-Listprocessor-Version: 8.0(beta) -- ListProcessor by CREN

On Sun, 11 Feb 96 23:42:09 0500 you said:
><ned@innosoft.com>t.com>,
>		   Keith Moore <moore@cs.utk.edu>
>Content-Type: text/plain; charset="iso-8859-1"
>Subject: If you can read this you understand the example.
>X-Mailer: MR/2 Internet Cruiser Edition v0.99p
>
>Some more samples:
>
>This comes from a newer version of Free Agent. Still the same problem: I
>would guess that this is due to the fact that they are only declaring text
>and nothing else. Rather primitive for such a hyped-up program. How to
>solve this? One possibility could perhaps be to assume that the sending
>system/program has been  using the same codepage as the receiver. There
>will of course be instances when this is wrong, but probably not so many.

I'm not sure why I received this, but I happen to have contacted Fort
for exactly this problem, with the text to include in the header.
I'm not sure they fully understood the importance.
They are now about to "implement MIME" but I have the feeling that
their intent is more related to encoding/decoding binaries than to
serve the character sets purpose.
So, it would probably help if they received a couple of other
similar requests, and that's now.

I'm taking this opportunity to checkpoint the status of the SMTP8 issue.
As I have predicted it must be 3 years ago now, many mail MUAs and MTAs
still continue to do happy 8-bit mail without much notion of MIME.
Yes, 8-bit mail very often *works* and all it takes to have it most often
work is to say that it should.

That's 3 basic rules:
1) MTAs MUST relay mail body exactly as they receive it (unless they
gateway with another mail protocol dictating otherwise, such as with
character translation). That's EASY.
2) [the user should know that] an MTA MAY return 8-bit mail for some
reason when it drops it in a local mail box (but it's of course discouraged).
3) the coded character set MUST be identified with MIME header entries.

You can see that this would solve the Fort case, the case of this
particular MUA I'm using now and many others (nothing's done because
MIME is too much to implement but if you tell people that all it takes
to at least send mail correctly is a simple addition to the header,
they will do it).

I'm not on the list any more, so use my e-mail address if you want
to contact me.

Andr.