IETF Logo Mail Archive

Re: Line Wrapping Question

Ned Freed <NED@innosoft.com> Wed, 07 February 1996 21:18 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa20227; 7 Feb 96 16:18 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa20223; 7 Feb 96 16:18 EST
Received: from list.cren.net by CNRI.Reston.VA.US id aa13416; 7 Feb 96 16:18 EST
Received: from localhost (localhost [127.0.0.1]) by list.cren.net (8.6.12/8.6.12) with SMTP id PAA17324; Wed, 7 Feb 1996 15:29:40 -0500
Received: from THOR.INNOSOFT.COM (THOR.INNOSOFT.COM [192.160.253.66]) by list.cren.net (8.6.12/8.6.12) with ESMTP id PAA17290 for <ietf-822@list.cren.net>; Wed, 7 Feb 1996 15:29:32 -0500
Received: from INNOSOFT.COM by INNOSOFT.COM (PMDF V5.0-6 #2001) id <01I0XJ5VPCHS9N3WDF@INNOSOFT.COM>; Wed, 07 Feb 1996 12:28:54 -0800 (PST)
Message-Id: <01I0XK2QDNBI9N3WDF@INNOSOFT.COM>
Date: Wed, 07 Feb 1996 12:28:20 -0800 (PST)
X-Orig-Sender: owner-ietf-822@list.cren.net
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Ned Freed <NED@innosoft.com>
To: Valdis.Kletnieks@vt.edu
Cc: "Sukvinder Singh Gill (Exchange)" <sukvg@wspu.microsoft.com>, "ietf-822@list.cren.net" <ietf-822@list.cren.net>
Subject: Re: Line Wrapping Question
In-Reply-To: "Your message dated Wed, 07 Feb 1996 14:16:35 -0500" <199602071916.OAA25326@black-ice.cc.vt.edu>
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT <c=US%a=_%p=Microsoft%l=DABONE960207083118QU005600@yuri.microsoft.com> <c=US%a=_%p=Microsoft%l=DABONE960207083118QU005600@yuri.microsoft.com>
X-Listprocessor-Version: 8.0(beta) -- ListProcessor by CREN

> On Wed, 07 Feb 1996 08:31:18 PST, you said:
> > Currently, when sending Internet Mail with long lines, we
> > default to using QP encoding so that MIME aware clients
> > can unwrap the lines, and display as required on their
> > viewers. (We use 140chars as the threshold)

> Umm.. this *is* using text/enriched and not text/plain, correct?
> If it isn't, that may be the solution you need....

No. They use text/plain. Bad choice. I pointed out that text/enriched is
a viable option in my previous note on the subject.

				Ned

v2.8.7 | Report a Bug | By Email