29 lines
1.1 KiB
Plaintext
29 lines
1.1 KiB
Plaintext
MBOX-Line: From tss at iki.fi Fri Dec 9 21:40:42 2011
|
|
To: imap-protocol@u.washington.edu
|
|
From: Timo Sirainen <tss@iki.fi>
|
|
Date: Fri Jun 8 12:34:47 2018
|
|
Subject: [Imap-protocol] LIST reply with trailing separator, once more
|
|
In-Reply-To: <alpine.OSX.2.00.1112092123160.931@hsinghsing.panda.com>
|
|
References: <1323492410.15365.102.camel@hurina>
|
|
<alpine.OSX.2.00.1112092123160.931@hsinghsing.panda.com>
|
|
Message-ID: <1323495642.15365.123.camel@hurina>
|
|
|
|
On Fri, 2011-12-09 at 21:25 -0800, Mark Crispin wrote:
|
|
|
|
> You can solve the conundrum by making "select/" be selectable.
|
|
|
|
I worry about potential security and other problems if that is done. For
|
|
example if there's an ACL for "select", it would also have to match
|
|
"select/". And with SPECIAL-USE if there's a \Trash attribute for
|
|
"Trash", it would probably also have to be returned for "Trash/". And
|
|
probably all kinds of other little things that aren't immediately
|
|
obvious.
|
|
|
|
Maybe most of the problems could be avoided by translating "select/"
|
|
into "select" in the IMAP layer (and back when needed), but that's quite
|
|
a lot of extra code just for handling something that I don't think
|
|
clients should be doing anyway.
|
|
|
|
|
|
|