Re: I-D Action:draft-newman-email-subaddr-01.txt

Randall Gellens <randy@qualcomm.com> Wed, 05 December 2007 22:55 UTC

Return-path: <discuss-bounces@apps.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J039X-0004Pj-Rn; Wed, 05 Dec 2007 17:55:39 -0500
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1J039W-0004PI-M4 for discuss-confirm+ok@megatron.ietf.org; Wed, 05 Dec 2007 17:55:38 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J039W-0004OQ-BS for discuss@apps.ietf.org; Wed, 05 Dec 2007 17:55:38 -0500
Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J039U-0005vV-P5 for discuss@apps.ietf.org; Wed, 05 Dec 2007 17:55:38 -0500
Received: from totoro.qualcomm.com (totoro.qualcomm.com [129.46.61.158]) by ithilien.qualcomm.com (8.14.2/8.12.5/1.0) with ESMTP id lB5MtZxr011314 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 5 Dec 2007 14:55:35 -0800
Received: from dhcp-407d.ietf70.org (vpn-10-50-16-21.qualcomm.com [10.50.16.21]) by totoro.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id lB5MtS1e013500; Wed, 5 Dec 2007 14:55:29 -0800 (PST)
Mime-Version: 1.0
Message-Id: <p06240604c37cd9904025@dhcp-407d.ietf70.org>
In-Reply-To: <2639.1196849327.522853@peirce.dave.cridland.net>
References: <E1It5KL-00032t-Up@stiedprstage1.ietf.org> <20071203094351.GA19449@nic.fr> <2639.1196720643.545129@peirce.dave.cridland.net> <20071204161659.GA19161@nic.fr> <2639.1196812257.522519@peirce.dave.cridland.net> <4755EF6C.8060703@cs.utk.edu> <2639.1196849327.522853@peirce.dave.cridland.net>
X-Mailer: Eudora for Mac OS X
X-message-flag: Warning: Outlook in use. Upgrade to Eudora: <http://www.eudora.com>
Date: Wed, 5 Dec 2007 14:45:46 -0800
To: Dave Cridland <dave@cridland.net>, Keith Moore <moore@cs.utk.edu>
From: Randall Gellens <randy@qualcomm.com>
Subject: Re: I-D Action:draft-newman-email-subaddr-01.txt
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Random-Sig-Tag: 1.0b28
X-Spam-Score: -4.0 (----)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: Apps Discuss <discuss@apps.ietf.org>
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: general discussion of application-layer protocols <discuss.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@apps.ietf.org>
List-Help: <mailto:discuss-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=subscribe>
Errors-To: discuss-bounces@apps.ietf.org

At 10:08 AM +0000 12/5/07, Dave Cridland wrote:

>  Whereas, if the MLM is explicitly told that the convention is in 
> use within the ADMD (at least for this subscriber), then it can 
> perform that kind of action without the need for potentially 
> dangerous guesswork.

There isn't any way to tell the MLM, though, aside from some 
administrative interface that is beyond the reach of most users of 
most MLMs.  That's why I'm not convinced that the list server text is 
worth keeping.

>  FWIW, I think there's a BCP to be written on MLMs; the state of the 
> art is getting quite refined, these days, and it's another area I 
> can't really find much documentation. (List-* header fields not 
> withstanding).

There's also a document a while back on using standard addresses, 
such as the -request address, and standard commands, IIRC.  But a BCP 
on MLMs would be a good thing.

>  That said, it has been suggested that MLMs might want to go a step 
> further, and rewrite messages such that a message from 
> <keith+something@example.net> copied to a mailing list which has a 
> (Subaddress-enabled) subscriber of <keith+ietf@example.net> would 
> cause the MLM to go as far as rewriting headers to the subscribed 
> address.

This makes me nervous.  There may be some reason why a particular 
subaddress was used for a message.  I don't think the MLM is in any 
position to know what is the right thing to do here.  I'd be 
delighted if my MUA would let me assign a default From address (or 
"personality" or "account") to use when I send a message to a 
particular recipient.  The MUA is in the best position to do this, 
and there is still the opportunity for the user to correct it.  There 
is no chance for this at the MLM.
-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly-selected tag: ---------------
We adore chaos because we love to produce order.
                                  --M. C. Escher