On Thu, May 2, 2013, at 04:05 PM, Robert Mueller wrote: > A couple of things: > > 1. Should we block creation of INBOX.sub in the alt namespace mode? In > theory, only the top level "[Ii][Nn][Bb][Oo][Xx]" is special, but it > *might* confuse some clients that INBOX.sub and Inbox.sub are different > folders. > > 2. Should it be possible to block creation of the <illegal> folders and > to help with (1), INBOX.[...everything except Inbox...] in the Non-Alt > namespace mode? If we did that, we could create a script that went > through and renamed all the existing bogus ones in some way sanely, and > know that no invisible or confusing folders will ever be created in the > future...
Much as it pains me to say it - I think these things should probably be configuration options with sane defaults. So what's a sane default? Our case is kind of special that we allow BOTH modes, and we're going to have to think about how that affects sieve as well. We already (currently in 2.5-git) block INBOX.INBOX from appearing in any CREATE command, so I'm pretty happy with this as the defaults: 1) You are only allowed to create subfolders of "Inbox" with the same spelling as the one we return (in altnamespace mode) 2) In non-altnamespace mode, allow creating anything. If it isn't visible in altnamespace, that's whoever decided to change the config's lookout. (that's for the default, we might lock it down more at FastMail) Bron. -- Bron Gondwana br...@fastmail.fm
