Re: [MORG] I-D Action:draft-ietf-morg-list-specialuse-03.txt

Barry Leiba <> Wed, 17 November 2010 00:42 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4EAAA3A68AC for <>; Tue, 16 Nov 2010 16:42:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.016
X-Spam-Status: No, score=-102.016 tagged_above=-999 required=5 tests=[AWL=-0.039, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id AG8zlsf1dcrg for <>; Tue, 16 Nov 2010 16:42:06 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id D48213A68A9 for <>; Tue, 16 Nov 2010 16:42:03 -0800 (PST)
Received: by iwn40 with SMTP id 40so1519022iwn.31 for <>; Tue, 16 Nov 2010 16:42:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=Cp2BfdTJkvbQZ7FW3Cg32vRDA7i6vEk69v3Z9G/z2+4=; b=HzW67SA9Ki12ZjWi9HvOeoXyvTORMHJHRbwKOQyVuKj90XdfW3G9wfpidhViI8BNEJ r3kiZlqOH953bGQb90sElIkQxM46JTaUqUvz30pVqoEW6spPnkqXyQUDU3KDRnTlWCUC TLgkA+nCd/WOEBcFLMYhP/9gGsyP8QdhsDkKc=
DomainKey-Signature: a=rsa-sha1; c=nofws;; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=IbOUqR13WaJW7kZipsglpTdgV/6Im/YgF1/HB5XdIsTSGNEBx+9Q3b3++VZZkYGLuy Vwqucfffm1cpSINGa2YcfYrlwqxhPG9aSaq1XtCR6yEbCuUxJsv6byCkcuNTwujk86eM jRRu/0C16eLzeNn4E2pyNxl2ni0KDWRsddZLU=
MIME-Version: 1.0
Received: by with SMTP id m14mr6274061ibx.128.1289954557486; Tue, 16 Nov 2010 16:42:37 -0800 (PST)
Received: by with HTTP; Tue, 16 Nov 2010 16:42:37 -0800 (PST)
In-Reply-To: <>
References: <> <> <>
Date: Wed, 17 Nov 2010 08:42:37 +0800
X-Google-Sender-Auth: Pr3-BGUk2YOs_Yxau2bjfEJ-O60
Message-ID: <>
From: Barry Leiba <>
To: Timo Sirainen <>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [MORG] I-D Action:draft-ietf-morg-list-specialuse-03.txt
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 17 Nov 2010 00:42:21 -0000

>> > I think the document could use a note explaining that the special-use
>> > flags apply only to the authenticated user's personal mailboxes.  (Or
>> > the opposite, if you so desire!)  In other words, if you did a LIST
>> > on another user's mailboxes (per NAMESPACE), should the \Inbox show
>> > up on their INBOX?
>> >
>> Ah, good point. I think \Inbox and friends shouldn't be shown for
>> INBOXes (etc.) of other users.

I wonder when y'all last read this doc: \Inbox has been out for a while now.

I'm not sure we want to restrict things, and forbid using a shared
mailbox for some functions.  While I agree that in most cases you'll
want to have all the special-use boxes in the user's private
namespace, I'd rather keep any discussion of that as non-normative

What do you folks think of that suggestion?

> Also maybe this example should use "*" instead of "%":
>     C: t3 LIST (SPECIAL-USE) "" "%"
>     S: * LIST (\Sent) "/" SentMail
>     S: * LIST (\Marked \Drafts) "/" MyDrafts
>     S: * LIST (\Trash) "/" Trash
>     S: t3 OK done
> And a small note that it's not required that the special-use mailboxes
> exist on root level (especially when server uses e.g. INBOX/ namespace
> prefix), and with "*" it's guaranteed to return all of them.

OK, sure.  Reasonable change.

>> CREATE command "USE" parameter: In some server implementations, some
>>    special uses may imply automatic action by the server.  For example,
>>    creation of a "\Junk" mailbox might cause the server to start placing
>>    messages that have been evaluated as spam into the mailbox.  Server
>>    implementors SHOULD consider the consequences of allowing a user (or
>>    client program) to designate the target of such automatic action.
> Maybe make it clearer with a note something like: "(e.g. mailboxes
> containing spaces, line feeds, quotes or '`' characters might break some
> scripts)".

Hm.  That's not what that security note is talking about at all.  I
could certainly add your note as well (though I don't know that it's a
security consideration), but it's entirely orthogonal to the paragraph
you cited.