Subject: Re: inline text encoding (was Attached text always BASE64 encoded?)

From: [email-masked] (Christer Lindh)
Date: Mon, 25 Oct 93 07:28:51 +0100

> We don't want Pine to be overly obnoxious to non-MIME users, but at
> the same time we want to fulfil the requirements of the MIME RFCs,
> and make sure that Pine does the right thing for our non-US-ASCII
> friends.

It does the right thing when the receiver has MIME, but with the
advance of 8bit SMTP there's no need to QP-encode. BTW, most SMTPs
in Sweden are already hacked to pass 8 bits...

So it would be nice if it was possible to turn the QP feature off,
preferably per composed mail or at least in the rc-file. Put in
"Content-Transfer-Encoding: 8bit" instead if QP is not used.

99% of my contacts does not have MIME-capabale readers yet.  They are
mostly users and have not a slightest idea on how to install metamail"
nor Pine. They get terribly confused by all this =E5 stuff...
Especially the line-breaking!  (they are sort of used to see all kinds
of weird characters instead of our national characters...)

So, in short; Pine should offer all these nice MIMEifications, they
come to great use in-house and between MIME-compliant mailers but as
most of the email world doesn't do MIME yet, please make the encoding
stuff more configurable.
--
::       [email-masked]       ::   o/        ::                      ::
:: Abalon AB, Stockholm, Sweden ::  /@         ::        Earth.        ::
::       (MIME compliant)       ::  /!>        :: Love it or leave it. ::
::   * All disclaimers apply *  ::   !  climb! ::                      ::