http://dovecot.org/test/
Maildir code is still having syncing trouble. I thought about fixing
mbox code for a chance - if the same problems happen with it too then I
at least know that the problems are in indexes instead of maildir
syncing itself.
So, the biggest change in 1.0-test15 is a new fully functional superfast
mbox code. If you can make it corrupt your mboxes I'd like to know about
that. I haven't tested it too much yet, but I haven't seen corruption
for a while anymore.
Superfast as in:
- Syncing and modifying the mbox is done in one integrated loop, no
more passing through the whole mbox multiple times.
- If we know the mbox is synced and we need to modify it, we directly
jump to the message(s) needing modification and change only them. This
means that with upcoming Dovecot LDA the mbox never needs to be fully
parsed. As long as you're not expunging old messages, mboxes with sizes
of even gigabytes should be no problem.
Still a few remaining issues though:
- It gets to infinite loop with 0 sized message body. I'll fix this
soon
- Recent counters are broken
- mbox lock should be kept two extra seconds after syncing. that is
required so that we can be sure no-one else has modified the mbox (ie.
mtime changes every time)
- APPEND command doesn't yet update indexes directly, so they still
trigger a full sync
- keywords aren't implemented
- UW-IMAP style "FOLDER INTERNAL DATA" message is almost supported..
but not quite yet. We're going to use it if it exists, but we won't
insert one ourself.
This also brings to my mind supporting some other flatfile formats..
Well, I'll write another mail about that.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20040615/5c665908/attachment-0001.bin>
