Re: MHonArc mail archive line wrapping

"t.petch" <daedulus@btconnect.com> Wed, 16 February 2011 12:00 UTC

Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 265FF3A6E28 for <ietf@core3.amsl.com>; Wed, 16 Feb 2011 04:00:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rP5q-dylqkzj for <ietf@core3.amsl.com>; Wed, 16 Feb 2011 04:00:58 -0800 (PST)
Received: from mail.btconnect.com (c2beaomr07.btconnect.com [213.123.26.185]) by core3.amsl.com (Postfix) with ESMTP id C55B03A6E14 for <ietf@ietf.org>; Wed, 16 Feb 2011 04:00:56 -0800 (PST)
Received: from host86-141-16-12.range86-141.btcentralplus.com (HELO pc6) ([86.141.16.12]) by c2beaomr07.btconnect.com with SMTP id BUF08530; Wed, 16 Feb 2011 12:01:19 +0000 (GMT)
Message-ID: <003101cbcdc8$42dfaf20$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: Marc Petit-Huguenin <petithug@acm.org>, Bjoern Hoehrmann <derhoermi@gmx.net>
References: <BF1B4928-ABEE-4EC0-9BE5-DDD3C6FAB9C3@apple.com><2vqll6ts0l0hjuic0t3p60sp679nh87920@hive.bjoern.hoehrmann.de> <4D5B0AB8.90509@acm.org>
Subject: Re: MHonArc mail archive line wrapping
Date: Wed, 16 Feb 2011 11:57:06 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Neutral-1, source=Queried, refid=tid=0001.0A0B0302.4D5BBC8F.00E6, actions=tag
X-Junkmail-Status: score=10/50, host=c2beaomr07.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0203.4D5BBC90.0231, ss=1, fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=single engine
X-Junkmail-IWF: false
Cc: Stuart Cheshire <cheshire@apple.com>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 12:00:59 -0000

---- Original Message -----
From: "Marc Petit-Huguenin" <petithug@acm.org>
To: "Bjoern Hoehrmann" <derhoermi@gmx.net>
Cc: "Stuart Cheshire" <cheshire@apple.com>; "IETF-Discussion list"
<ietf@ietf.org>
Sent: Wednesday, February 16, 2011 12:22 AM
>
> On 02/15/2011 01:32 PM, Bjoern Hoehrmann wrote:
> > * Stuart Cheshire wrote:
> >> In the MHonArc mail archive there are often super-long lines, which
> >> would be wrapped to the window width when viewing in most mail
> >> clients, but when viewed in a web browser they appear as long single
> >> lines which take a lot of left-to-right scrolling to read them.
> >
> > That is the result of some clients and users violating netiquette and
> > mail standards, for instance, RFC 1855, section 2.1.1:
> >
> >   - Limit line length to fewer than 65 characters and end a line
> >     with a carriage return.
> >
> > and RFC 2822 (and similarily RFC 5322), section 2.1.1:
> >
> >   There are two limits that this standard places on the number of
> >   characters in a line. Each line of characters MUST be no more than
> >   998 characters, and SHOULD be no more than 78 characters, excluding
> >   the CRLF.
> >
> > And this does not cause problems just with unwrapped lines, it also has
> > other effects, like people quoting excessively long lines on one line
> > but then write their own text properly wrapped (that's appropriate be-
> > havior if long lines are rare and most likely intentional, such as when
> > including some computer code you don't want wrapped at odd positions.)
> >
> > I note that one of the main culprits here are Apple Mail users, although
> > you seem to be using it yet have managed to send properly wrapped lines.
> > If there is something Apple Mail users can do to stop their netiquette
> > and standards violations, I would apprciate any pointer you may have.

If only Apple Mail users would stop signing mails it would be a major step
forward.

Depending on the algorithm, I either get a blank pane, and have to
get into properties to see the text, or, with more recent PKIX-based
algorithms, have to wait for a megabyte download of CRL (or, if
I am offline, a two minute lockup of my PC).

Grrr  I don't care what standard signed mails conform to, I just
want them filtered out at source:-)

Tom Petch

<snip>