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 1J039f-0004XE-0f; Wed, 05 Dec 2007 17:55:47 -0500
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1J039d-0004Wu-7x for discuss-confirm+ok@megatron.ietf.org; Wed, 05 Dec 2007 17:55:45 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J039c-0004Wi-UO for discuss@apps.ietf.org; Wed, 05 Dec 2007 17:55:44 -0500
Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J039b-0005wS-Jf for discuss@apps.ietf.org; Wed, 05 Dec 2007 17:55:44 -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 lB5Mtgfl011320 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 5 Dec 2007 14:55:42 -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 lB5MtS1g013500; Wed, 5 Dec 2007 14:55:36 -0800 (PST)
Mime-Version: 1.0
Message-Id: <p06240605c37cdb81b4a7@dhcp-407d.ietf70.org>
In-Reply-To: <4756C14D.5080407@cs.utk.edu>
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> <4756C14D.5080407@cs.utk.edu>
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:51:01 -0800
To: Keith Moore <moore@cs.utk.edu>, Dave Cridland <dave@cridland.net>
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: de4f315c9369b71d7dd5909b42224370
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 7:18 AM -0800 12/5/07, Keith Moore wrote:

>  I am dubious that MUAs or users should assume that
>  there's a relationship between the subaddress and the name of the folder
>  where that mail ends up.  at least I've found good reasons for them not
>  to be the same.  though admittedly that makes for a more complex user
>  interface.

Yes -- it is better to think of them as a general ability to tag 
inbound mail for some sort of special processing.  The fact that some 
delivery agents have a default rule of delivering into a mailbox 
whose name exactly matches the detail part is merely an optimization.
-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly-selected tag: ---------------
A bird in the hand is safer than one overhead.