Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (1)

"Frank Ellermann" <nobody@xyzzy.claranet.de> Sun, 09 December 2007 05:05 UTC

Return-path: <ietf-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J1EMQ-00059x-7L; Sun, 09 Dec 2007 00:05:50 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J1EMO-00058n-Ax for ietf@ietf.org; Sun, 09 Dec 2007 00:05:48 -0500
Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J1EMM-0007dx-Lo for ietf@ietf.org; Sun, 09 Dec 2007 00:05:48 -0500
Received: from list by ciao.gmane.org with local (Exim 4.43) id 1J1EME-0008LC-AA for ietf@ietf.org; Sun, 09 Dec 2007 05:05:38 +0000
Received: from c-134-88-15.hh.dial.de.ignite.net ([62.134.88.15]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Sun, 09 Dec 2007 05:05:38 +0000
Received: from nobody by c-134-88-15.hh.dial.de.ignite.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Sun, 09 Dec 2007 05:05:38 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: ietf@ietf.org
From: Frank Ellermann <nobody@xyzzy.claranet.de>
Date: Sun, 09 Dec 2007 06:07:26 +0100
Organization: <http://purl.net/xyzzy>
Lines: 24
Message-ID: <fjft2g$a68$1@ger.gmane.org>
References: <E1IwpJr-0007aa-OQ@stiedprstage1.ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: c-134-88-15.hh.dial.de.ignite.net
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1914
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1914
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Subject: Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (1)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org

The IESG wrote:

> <draft-klensin-rfc2821bis-06.txt> as a Draft Standard
 
> The IESG plans to make a decision in the next few weeks,
> and solicits final comments on this action.

I-D.klensin-2821bis 3.9 as before RFC 2821 3.10 state in
essence, that relays, forwarders, and mailing lists have
no business to mess with the header of a mail:

| the message header section (RFC2822 [9]) MUST be left
| unchanged

This appears to be at odds with the mailing list RFCs,
adding various List-* header fields.  

It's disturbing if five IETF mail experts offer three
strictly incompatible opinions what mailing lists are
supposed to do with an existing "Sender" header field,
or if adding a "Sender" (as it's common practice) is
actually permitted.  

 Frank


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf