In researching bug #474, I realized that we currently allow arbitrary
mailboxes to begin with #. According to RFC 3501, section 5.1:
5) Two characters, "#" and "&", have meanings by convention, and
should be avoided except when used in that convention.
and then:
5.1.2. Mailbox Namespace Naming Convention
By convention, the first hierarchical element of any mailbox name
which begins with "#" identifies the "namespace" of the remainder of
the name. This makes it possible to disambiguate between different
types of mailbox stores, each of which have their own namespaces.
For example, implementations which offer access to USENET
newsgroups MAY use the "#news" namespace to partition the
USENET newsgroup namespace from that of other mailboxes.
Thus, the comp.mail.misc newsgroup would have a mailbox
name of "#news.comp.mail.misc", and the name
"comp.mail.misc" can refer to a different object (e.g., a
user's private mailbox).
It occurs to me that we should be preventing such mailboxes from being
created. This may have to happen in 2.2. In fact, I may have recently
un-disallowed such mailboxes. I'll have to check back on this.
I also wonder if there isn't some cleaner abstraction that could be made,
so that any mailbox beginning with # is passed through a single set of
functions that figure out what to do with it. This is more 2.3 work.
Aaron
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
