> In fact I was under the impression that INBOX is a reserved folder name,
> that it should always be there, and you are not allowed to create
> subfolders of it. I don't think many enforce the no-subfolder of INBOX
> rule, and I may just be remembering wrong.
I haven't read the IMAP RFCs. I do know that Outlook permits you to create
sub-folders of INBOX.
> As these IMAP stores are developers and we look to share POP3 and
> IMAP stores, the POP3 handler will just know to always user user.INBOX.
This would make sense for when we re-do the repositories, or even if we were
to rewrite parts of Cornerstone. But the current discussion has been to
simply to keys, not hierarchies as an intermediate solution allowing
immediate work on IMAP.
Yes, it is trivial to change the James code to use user.INBOX. But then
admins would have to rename all of their existing file system and JDBC
repositories to use it. THAT is what I am suggesting we avoid by the simple
expedient of declaring that user.INBOX === user as a unique (special case)
mapping. If you have an alternative, that's fine, too.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
