Re: [yam] Issue #10: RFC 5321 3.9: add tiny subsection

Alessandro Vesely <vesely@tana.it> Fri, 11 December 2009 13:54 UTC

Return-Path: <vesely@tana.it>
X-Original-To: yam@core3.amsl.com
Delivered-To: yam@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 732823A689F for <yam@core3.amsl.com>; Fri, 11 Dec 2009 05:54:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.66
X-Spam-Level:
X-Spam-Status: No, score=-4.66 tagged_above=-999 required=5 tests=[AWL=0.059, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
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 bC+jXd+0TOau for <yam@core3.amsl.com>; Fri, 11 Dec 2009 05:54:40 -0800 (PST)
Received: from wmail.tana.it (www.tana.it [62.94.243.226]) by core3.amsl.com (Postfix) with ESMTP id 5AB063A687E for <yam@ietf.org>; Fri, 11 Dec 2009 05:54:40 -0800 (PST)
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 ale@tana.it, TLS: TLS1.0, 256bits, RSA_AES_256_CBC_SHA1) by wmail.tana.it with esmtp; Fri, 11 Dec 2009 14:54:25 +0100 id 00000000005DC02F.000000004B224F11.00005F9D
Message-ID: <4B224F10.7050202@tana.it>
Date: Fri, 11 Dec 2009 14:54:24 +0100
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: SM <sm@resistor.net>
References: <6.2.5.6.2.20091206014538.033cdcc8@elandnews.com> <4B1BE2D5.9010405@tana.it> <6.2.5.6.2.20091206102946.04601b90@resistor.net> <01NGXSHS3NUQ0000BI@mauve.mrochek.com> <4B1CDDE8.2090100@tana.it> <6.2.5.6.2.20091207072413.047ff4a0@resistor.net> <4B1E0967.1040006@tana.it> <6.2.5.6.2.20091208135556.030cfb28@resistor.net> <4B1FC47F.40103@tana.it> <6.2.5.6.2.20091209155607.032eff40@resistor.net>
In-Reply-To: <6.2.5.6.2.20091209155607.032eff40@resistor.net>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: yam@ietf.org
Subject: Re: [yam] Issue #10: RFC 5321 3.9: add tiny subsection
X-BeenThere: yam@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Yet Another Mail working group discussion list <yam.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/yam>, <mailto:yam-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/yam>
List-Post: <mailto:yam@ietf.org>
List-Help: <mailto:yam-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yam>, <mailto:yam-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Dec 2009 13:54:41 -0000

SM wrote:
> There is some discussion about information disclosure in Section 7.  
> Please don't read this as meaning that the section should be or not be 
> changed.

FWIW, assuming the definition of forwarding has been amended, issues 
related to section 3.9 could be addressed there like so:

  7.x Privacy violations on forwarding

  Since mailbox addresses are Personally Identifiable Information,
  a.k.a. Personal Data, applications SHOULD track additions to aliases
  and lists used in forwarding as described in section 3.9, possibly
  retaining evidence of mailboxes' owners consent. The data model
  SHOULD be designed so as to allow meaningful write-access control.

That's not meant to be taken literally, just the idea.

>> You mean SPF authorization?
> 
> I mean authorization in general terms.

Section 7.1 castigates various authentication schemes, but does not 
mention that forwarders may need to tweak their configuration options 
or make specific arrangements in order to avoid rejections.