[Dovecot] 1.0 roadmap

[Fintec]

Hi Timo,

I'd like to add complete Public Shared Folders for virtual users (as
discussed previously on list) to the wish list.

Main problems with ACL implementation currently are:
1) Namespace prefixes are currently ignored, therefore vfile global
acl's must be used which are less flexible
2) Unable to use anything more than lrwsiea acl listing in vfile. Adding
any more of the ACLs, for example k, dovecot reports:
dovecot: IMAP(user1 at domain.com): ACL file /etc/dovecot-acls/Management
line 1: Unknown ACL 'k'
3) Global ACLs stop other non-ACL restricted public namespace
directories working (in my configuration)

UPDATE: apparently 2) is fixed with b8 but I haven't had a chance to
test.

Gavin


On Mon, 2006-06-12 at 01:25 +0300, Timo Sirainen wrote:
> I've read about one month back this list's messages. I've still 216
> messages from this year marked as "unread" which I should look into more
> (+258 older ones). Also I've 180 "unread" messages in my INBOX also
> which might contain something useful. So those messages could still
> contain something that should be added to this list.
> 
> Anyway looking at my current TODO, I think the following things should
> be fixed before v1.0. Additions, comments, patches and such welcome. :)
> 
> Help would be welcome in checking if these bugs are still there:
> 
>  - Thunderbird+POP3 DELE error. Was this fixed already? Could someone try
>    this? See http://www.dovecot.org/list/dovecot/2005-June/007497.html
>    and the rest of the thread. Basically put thousands of messages into
>    mailbox, start downloading them and see if error comes.
> 
>  - Solaris sendfile is broken? Is it? Can someone try? You can test it
>    with maildir by setting mail_save_crlf=yes, saving a somewhat large
>    mail and FETCHing it (and truss that it really uses sendfile)
> 
>  - passdb passwd + passdb shadow -> passdb_password isn't reset to NULL
>    (ie. probably doesn't allow logging in if the shadow password is correct?)
> 
>  - maildir: rename foo foo.xyz -> infinite loop possible? (doesn't seem so?
>    why did I think it could be? look at the code)
> 
> Important:
> 
>  - dict-server should have some config file which lists the allowed dicts
>  - LDA: empty mail gives an error.
>  - deliver: delivering mail to box smaller than mbox_min_index_size give
>    close() errors
>  - mbox: CRLFs in headers break the mbox
>  - index: when mailbox is deleted/renamed and someone else had it open, we get
>    stat() error messages in log file. Handle at least the most common places
>    where it happens.
>  - lib-storage
>     - limit folder hierarchy levels? user can now create eg. a/a/a/a/...
>       and then start renaming them from end to beginning, which probably will
>       at some point start causing syscall failures which will fill up logs.
> 
> Probably should be done:
> 
>  - mbox: dirty mode should be stored to index
>  - quota code should probably be always doing some quota_set_critical()
>    instead of using mail_storage_set_critical(), so that quota_last_error()
>    would work properly
>  - rfc2557 support for BODYSTRUCTURE, as specified by RFC3501
>  - keywords: add some limits to how many there can be
>     - don't return \* in PERMANENTFLAGS when we're full
>  - mbox: how well does dirty sync + status work? it reads the last mail every
>    time? not very good..
>  - maildir: we probably shouldn't do duplicate detection/fixing?.. or at least
>    stat() the old file before trying, because we might have just previously
>    seen the old file and then new file and then we try to fix it..
>