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

S Moonesamy <sm+ietf@elandsys.com> Tue, 06 May 2014 08:47 UTC

Return-Path: <sm@elandsys.com>
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 94E021A0289 for <ietf-822@ietfa.amsl.com>; Tue, 6 May 2014 01:47:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.441
X-Spam-Level:
X-Spam-Status: No, score=-2.441 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.651, T_DKIM_INVALID=0.01] 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 rs0CT2I9uaeh for <ietf-822@ietfa.amsl.com>; Tue, 6 May 2014 01:47:23 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 228C41A0286 for <ietf-822@ietf.org>; Tue, 6 May 2014 01:47:23 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.150.50]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s468l6Mf006585 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 May 2014 01:47:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1399366038; bh=JtfTxZlBszBspCuI+Nfv6kGLG37R/NCWV4rcWBjFmgU=; h=Date:To:From:Subject:In-Reply-To:References; b=tE2wmK+sVJ2utr/4QaohqmJCPQbxl3PHn9o0qV9NRCI0b0JIKmbr7uZwjJdfKoRPx aY7qECEcXYee3dsY0HIMtou6yXQW+OjoRmpVvXUfHTCrkiDtEzMqjrNxTw7nYZwZtU L83K+65S8OFOGmKwwnRXOe3lZ27KaFNtis8/LdxM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1399366038; i=@elandsys.com; bh=JtfTxZlBszBspCuI+Nfv6kGLG37R/NCWV4rcWBjFmgU=; h=Date:To:From:Subject:In-Reply-To:References; b=wIqwj+jzSnaLDtafgxMB04+lpvAyOuMKzEn2GWP7M0yc8Wi/z3ZIWGpUf89p61gFd tHJ+6znqk67u5Ld/qHsDMGkVyDYsJYbd5TB1JjazE1ih9d55Oh9qeP+U5Bv9lCteFl 4keeAWCXT9jEmVKqrVKUxdxf0WF3SGF0WuudiuSo=
Message-Id: <6.2.5.6.2.20140506004504.0b9b9a60@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 06 May 2014 01:44:09 -0700
To: Miles Fidelman <mfidelman@meetinghouse.net>, ietf-822@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <5368388F.6080201@meetinghouse.net>
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>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-822/-RDY8pjsAuTUL2cYBG5FYSLjxvw
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 08:47:24 -0000

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.

I trimmed the headers of the message which I received from this mailing list:

   From: Miles Fidelman <mfidelman@meetinghouse.net>
   MIME-Version: 1.0
   To: ietf-822@ietf.org
   Subject: Re: [ietf-822] WSJ/gmail/ML, was a permission to... (off-topic)
   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>
   Content-Transfer-Encoding: 7bit
   Content-Type: text/plain; charset="us-ascii"; Format="flowed"
   Errors-To: ietf-822-bounces@ietf.org
   Sender: "ietf-822" <ietf-822-bounces@ietf.org>

There aren't any Resent- headers in the above.  I looked at a message 
that passed through another mailing list implementation; there 
weren't any Resent- headers.

Regards,
S. Moonesamy