Both Paul and I made some changes this week to the 'anyone' and
'__public__' users, and to the way #Public folders are looked up. I just
want to make sure that we didn't mutually screw anything up worse than
it already was :-P

So I wrote code that creates the #Public folder and gives its ownership
to the 'anyone' user. I think that might be broken and it should belong
to the '__public__' user. Yes? No?

And for the changes I made to handle bug #424, when looking up a mailbox
that looks like #Users/username/mailbox..., the #Users and username are
stripped off and mailbox is looked for as being owned by that username.
When a #Public/mailbox... folder is looked up, no parts of the namespace
are stripped off. Rather, the #Public folder is found only if it belonds
to 'anyone' and auto-created otherwise. The sub-folders of #Public
belong to whomever might have created them.

There is still a bug though. Check this out:

localhost dbmail-2.1 $ telnet localhost 143 
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
* OK dbmail imap (protocol version 4r1) server 2.1 ready to run
a001 login test test
a001 OK LOGIN completed
a002 create "#Public/testbox"
a002 OK CREATE completed
a003 list "#Public" "*"
* LIST (\hasnochildren) "/" "#Public/Foo"
* LIST (\hasnochildren) "/" "#Public/testbox"
a003 OK LIST completed
a05 logout
* BYE dbmail imap server kisses you goodbye
a05 OK completed
Connection closed by foreign host.
localhost dbmail-2.1 $ telnet localhost 143
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
* OK dbmail imap (protocol version 4r1) server 2.1 ready to run
a01 login joeschmoe test
a01 OK LOGIN completed
a02 create "#Public/testbox"
a02 OK CREATE completed
a03 list "#Public" "*"
* LIST (\hasnochildren) "/" "#Public/testbox"
* LIST (\hasnochildren) "/" "#Public/TestFoo"
a03 OK LIST completed
a06 logout
* BYE dbmail imap server kisses you goodbye
a06 OK completed
Connection closed by foreign host.

Right, so there's two different sets of mailboxes appearing under the
same #Public folder, based on ownership of the mailbox. Should all
mailboxes under #Public simply be owned by '__public__'? Should we then
create an ACL entry for the mailbox creator giving them Admin rights to
the mailbox that they've created? Right now I think this is my plan.

All that said, how did this work before?
Did I royally f*** up previously working behavior?

Aaron

Reply via email to