Re: [ietf-822] WSJ/gmail/ML, was a permission to... (off-topic)

Miles Fidelman <mfidelman@meetinghouse.net> Tue, 06 May 2014 11:12 UTC

Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf-822@ietfa.amsl.com
Delivered-To: ietf-822@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A9AB1A07A7 for <ietf-822@ietfa.amsl.com>; Tue, 6 May 2014 04:12:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cP6UaHnmCHCY for <ietf-822@ietfa.amsl.com>; Tue, 6 May 2014 04:12:43 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 4CE3E1A02A8 for <ietf-822@ietf.org>; Tue, 6 May 2014 04:12:43 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 43CFDCC0A7 for <ietf-822@ietf.org>; Tue, 6 May 2014 07:12:39 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id rXtf8QA4+rVg for <ietf-822@ietf.org>; Tue, 6 May 2014 07:12:30 -0400 (EDT)
Received: from Miles-Fidelmans-MacBook-Pro.local (static-173-56-67-50.nycmny.fios.verizon.net [173.56.67.50]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 7A115CC0A1 for <ietf-822@ietf.org>; Tue, 6 May 2014 07:12:30 -0400 (EDT)
Message-ID: <5368C39E.80808@meetinghouse.net>
Date: Tue, 06 May 2014 07:12:30 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26
MIME-Version: 1.0
To: ietf-822@ietf.org
References: <20140418123721.3610.qmail@joyce.lan> <5365357D.2020101@tana.it> <53653C7A.3090304@pscs.co.uk> <53655C13.9070201@isdg.net> <5365F4F8.6020605@pscs.co.uk> <536629D7.7040809@meetinghouse.net> <6.2.5.6.2.20140505075814.0c9b0a68@resistor.net> <5367DB93.3050509@meetinghouse.net> <6.2.5.6.2.20140505124909.0cbcd6a8@resistor.net> <5368388F.6080201@meetinghouse.net> <6.2.5.6.2.20140506004504.0b9b9a60@resistor.net>
In-Reply-To: <6.2.5.6.2.20140506004504.0b9b9a60@resistor.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-822/dUattPVQ8eDLFeMpsHC6wEHmZ-k
Subject: Re: [ietf-822] WSJ/gmail/ML, was a permission to... (off-topic)
X-BeenThere: ietf-822@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion of issues related to Internet Message Format \[RFC 822, RFC 2822, RFC 5322\]" <ietf-822.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-822/>
List-Post: <mailto:ietf-822@ietf.org>
List-Help: <mailto:ietf-822-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 May 2014 11:12:44 -0000

S Moonesamy wrote:
> Hi Miles,
> At 18:19 05-05-2014, Miles Fidelman wrote:
>> I haven't actually dug into the details of how Outlook does things, 
>> but... does not RFC5322's series of resent- headers start to provide 
>> a direction for standardizing mailing list use of header fields?
>
> I read the relevant text as meaning that the "resent-" headers are 
> added when a message is reintroduced.  I prefer to leave it to other 
> people to interpret what that means.  There are a few List- headers 
> which have been standardized for mailing lists.
>

Yes, I understand that.

My contention is that:
1. mailing list software performs a relatively stable, well defined, set 
of functions (re-distribution, subject tagging, adding headers and 
footers, etc.), but,
2. those functions are not performed in a standardized way, and,
3. if those functions we're standardized, a lot of things would become 
easier - including, perhaps, improved interoperation of lists with 
things like DMARC, better list-aware mail clients

It strikes me that the RFC-5322 resent-headers, which don't seem to be 
used much, might be a good starting point for such standardization - for 
a start, by getting past the overloading of the From: header that causes 
so many problems.

Miles

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra