Hi all,
first, let me introduce myself: My name is Ilja Booij, I just started
working at
IC & S, and I have been appointed head dbmail developer. I'll be
monitoring this list very closely for interesting discussions, features
etc.
Currently I'm doing a rewrite of the database handling code (the stuff
in the
pgsql/ and mysql/ directories. There's a lot of code replication in
those directories that I'm now removing by using C++ classes.
For the authentication part, I'll be looking at Aaron Stone's LDAP
patch. LDAP authentication is a feature we really need to include.
When the transition of the database code to C++ is complete, we'll be
looking at some other features that will have to included for dbmail
2.0:
* Adjust Database model
- shared folders.
- save some headers(To:, From:, Subject: and maybe some more) with
message, so they do not have to be parsed every time.
- faster copy/move by using a message link table
* store used quotum of a user with user info, so the used quotum does
not have to calculated each time this number is needed (which it is
often!)
* IMAP namespaces
as stated in rfc2060:
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 an mailbox name of
"#news.comp.mail.misc", and the name "comp.mail.misc" could refer
to a different object (e.g. a user's private mailbox).
* administration GUI
Web interface seems to be the best way to go.
* LMTP Interface
for faster and better communication between
Local Mail Transport Protocol RFC 2033
* command line parser IMAP faster (combine some queries into
one query)
* TLS/SSL/Kerberos
IMAP over TLS/SSL RFC 2595
Comments are very welcome!
cheers,
Ilja
--
IC&S
Koningsweg 4
3582 GE UTRECHT
first, let me introduce myself: My name is Ilja Booij, I just started
working at
IC & S, and I have been appointed head dbmail developer. I'll be
monitoring this list very closely for interesting discussions, features
etc.
Currently I'm doing a rewrite of the database handling code (the stuff
in the
pgsql/ and mysql/ directories. There's a lot of code replication in
those directories that I'm now removing by using C++ classes.
For the authentication part, I'll be looking at Aaron Stone's LDAP
patch. LDAP authentication is a feature we really need to include.
When the transition of the database code to C++ is complete, we'll be
looking at some other features that will have to included for dbmail
2.0:
* Adjust Database model
- shared folders.
- save some headers(To:, From:, Subject: and maybe some more) with
message, so they do not have to be parsed every time.
- faster copy/move by using a message link table
* store used quotum of a user with user info, so the used quotum does
not have to calculated each time this number is needed (which it is
often!)
* IMAP namespaces
as stated in rfc2060:
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 an mailbox name of
"#news.comp.mail.misc", and the name "comp.mail.misc" could refer
to a different object (e.g. a user's private mailbox).
* administration GUI
Web interface seems to be the best way to go.
* LMTP Interface
for faster and better communication between
Local Mail Transport Protocol RFC 2033
* command line parser IMAP faster (combine some queries into
one query)
* TLS/SSL/Kerberos
IMAP over TLS/SSL RFC 2595
Comments are very welcome!
cheers,
Ilja
--
IC&S
Koningsweg 4
3582 GE UTRECHT