Re: mail vs. news ???

ned+ietf-822@mrochek.com Sun, 23 February 2003 06:45 UTC

Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h1N6jx628800 for ietf-822-bks; Sat, 22 Feb 2003 22:45:59 -0800 (PST)
Received: from nixon.xkey.com (h42-rt.sv.meer.net [205.217.153.42]) by above.proper.com (8.11.6/8.11.3) with SMTP id h1N6jqd28729 for <ietf-822@imc.org>; Sat, 22 Feb 2003 22:45:53 -0800 (PST)
Received: (qmail 21593 invoked by uid 1087); 23 Feb 2003 06:45:46 -0000
MBOX-Line: From owner-ietf-822@mail.imc.org Sat Feb 22 08:59:23 2003
Delivered-To: dan@xkey.com
Received: (qmail 11351 invoked from network); 22 Feb 2003 16:59:23 -0000
Received: from ns11.dnsprotect.com (HELO velocity.dnsprotect.com) (209.50.252.235) by h42-rt.sv.meer.net with SMTP; 22 Feb 2003 16:59:23 -0000
Received: from mail.proper.com ([208.184.76.45] helo=above.proper.com) by velocity.dnsprotect.com with esmtp (Exim 3.36 #1) id 18mcyn-0004gG-00 for dan@dankohn.com; Sat, 22 Feb 2003 11:58:25 -0500
Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h1MGlb712756 for ietf-822-bks; Sat, 22 Feb 2003 08:47:37 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [209.55.107.55]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h1MGlZd12752 for <ietf-822@imc.org>; Sat, 22 Feb 2003 08:47:35 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01KSQAW987B4002DEU@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf-822@imc.org; Sat, 22 Feb 2003 08:47:36 -0800 (PST)
Date: Sat, 22 Feb 2003 08:33:50 -0800
From: ned+ietf-822@mrochek.com
Subject: Re: mail vs. news ???
In-reply-to: "Your message dated Sat, 22 Feb 2003 10:05:34 +0000" <871y20aavl.fsf@erlenstar.demon.co.uk>
Old-To: Andrew Gierth <andrew@erlenstar.demon.co.uk>
Cc: Mark Crispin <mrc@cac.washington.edu>, Usefor Mailing List <usenet-format@rkive.landfield.com>, IETF-822 Mailing List <ietf-822@imc.org>
Message-id: <01KSQDUOCSEE002DEU@mauve.mrochek.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET="us-ascii"
Content-transfer-encoding: 7bit
References: <3E563BCB.904AAEB@oceana.com> <yl65rd33mk.fsf@windlord.stanford.edu> <Pine.LNX.4.55.0302211309490.4158@shiva1.cac.washington.edu> <871y20aavl.fsf@erlenstar.demon.co.uk>
List-Archive: <http://www.imc.org/ietf-822/mail-archive/>
List-ID: <ietf-822.imc.org>
List-Unsubscribe: <mailto:ietf-822-request@imc.org?body=unsubscribe>
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - velocity.dnsprotect.com
X-AntiAbuse: Original Domain - dankohn.com
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [0 0]
X-AntiAbuse: Sender Address Domain - mail.imc.org
Status: RO
To: dmk@skymv.com
Sender: owner-ietf-822@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-822/mail-archive/>
List-ID: <ietf-822.imc.org>
List-Unsubscribe: <mailto:ietf-822-request@imc.org?body=unsubscribe>

> >>>>> "Mark" == Mark Crispin <mrc@cac.washington.edu> writes:

>  Mark> Now we hear the claim that completely unnecessary restictions
>  Mark> in headers are necessary because of news software.

> who says those restrictions are unnecessary?

> Mail systems do not appear to make any actual use of the message-id
> header other than for logging (and internally in some odd systems).
> None of SMTP, POP3 or IMAP ever use message-ids as protocol
> parameters.  News, on the other hand, uses message-ids as protocol
> parameters _all the time_, both for readers accessing messages and for
> server-to-server transfer.

FWIW, draft-ietf-imapext-thread-12.txt is the obvious counterexample. But even
if what you say is true about the present email transport infrastructure, there
are plenty of email clients that support threading via message-id.

> (and, FWIW, I checked about a hundred thousand message-ids taken from
> mail messages here, and only one of those had whitespace in and that
> was a Chinese spam which had four spaces in place of the domain-part,
> almost certainly due to misconfigured or broken spamming software. So
> this clearly isn't a feature that anyone actually _needs_, or probably
> even wants.)

Which of course is illegal according to any of the relevant standards.

Mind you, I'm not saying that additional restrictions on message-ids in news
are inappropriate. At a minimum the restrictions of RFC 1036 have to be taken
into account. However, I do urge caution when attempting to cater to failure to
support the existing specifications in the installed base, however. This is a
game that has to be played very carefully.

				Ned