Two important fixes: the last one. I added more asserts anyway which try to catch similiar
- Fixes the recently reported dovecot-auth crashes with unexpected client input
- Fixes mbox corruption in some not-so-common cases. Hopefully this is
mistakes and avoid losing data.
Others:
- Added oe-ns-eoh workaround for pop3. Fixes outlook/netscape problems with buggy mails.
- lock_method = dotlock works now properly
- Cache file compression crashed in some situations
- auth_cache fixes from Andrey
Also I have about 80% of the code written for keywords support. It's about the last major missing feature from v1.0, so naming should change into 1.0-alphas soon. From there on it should be mostly about stabilization, cleaning up the code and maybe some optimization.
Timo Sirainen wrote:
Also I have about 80% of the code written for keywords support. It's about the last major missing feature from v1.0, so naming should change into 1.0-alphas soon. From there on it should be mostly about stabilization, cleaning up the code and maybe some optimization.
Maybe I've not been paying enough attention (or just don't know IMAP well enough), but could you explain a little about the function/use of this "keywords" functionality, please?
-- Curtis Maloney
On 8.12.2004, at 04:58, Curtis Maloney wrote:
Timo Sirainen wrote:
Also I have about 80% of the code written for keywords support. It's about the last major missing feature from v1.0, so naming should change into 1.0-alphas soon. From there on it should be mostly about stabilization, cleaning up the code and maybe some optimization.
Maybe I've not been paying enough attention (or just don't know IMAP well enough), but could you explain a little about the function/use of this "keywords" functionality, please?
Basically it means you can assign keywords to messages with whatever names you want. Mozilla/TB's labels are implemented with keywords. With Dovecot 0.99.x I called them custom flags.
Also I have about 80% of the code written for keywords support. It's about the last major missing feature from v1.0, so naming should change into 1.0-alphas soon. From there on it should be mostly about stabilization, cleaning up the code and maybe some optimization.
What about fixing IPv6 support?
// Brad
On 8.12.2004, at 06:53, Brad wrote:
Also I have about 80% of the code written for keywords support. It's about the last major missing feature from v1.0, so naming should change into 1.0-alphas soon. From there on it should be mostly about stabilization, cleaning up the code and maybe some optimization.
What about fixing IPv6 support?
I'm not aware of it having any problems, so I'm guessing you mean the lack of ability to listen both IPv4 and IPv6 with BSDs? That means support for listening in multiple sockets which isn't very high priority to me and it's probably somewhat annoying to implement. Maybe.
Timo wrote:
Also I have about 80% of the code written for keywords support. It's about the last major missing feature from v1.0, so naming should change into 1.0-alphas soon. From there on it should be mostly about stabilization, cleaning up the code and maybe some optimization.
Now those are the kind of announcements that will generate a nice amount of traffic. :P
And what about MY features? Waaaaaaah. ;)
Seriously though, unless I missed something some pet peeves of mine will be missing from 1.0 then, as in:
- Quota, both IMAP QUOTA (RFC 2087) and maildirsize support.
- More extensive and selective logging options.
Regards,
Christian Balzer
Christian Balzer Network/Systems Engineer NOC chibi@gol.com Global OnLine Japan/Fusion Network Services http://www.gol.com/
On 8.12.2004, at 07:48, Christian Balzer wrote:
Seriously though, unless I missed something some pet peeves of mine will be missing from 1.0 then, as in:
- Quota, both IMAP QUOTA (RFC 2087) and maildirsize support.
- More extensive and selective logging options.
I wouldn't call these "major features". Quota will most likely be a plugin because everyone wants to implement it a bit differently. Anyway, both of these will be in v1.0.
Timo Sirainen wrote:
Also I have about 80% of the code written for keywords support. It's about the last major missing feature from v1.0, so naming should change into 1.0-alphas soon. From there on it should be mostly about stabilization, cleaning up the code and maybe some optimization.
I still get a lot of
Dec 10 01:49:27 one dovecot: IMAP(ts@example.com): file mail-cache-fields.c: line 356 (mail_cache_header_fields_get): assertion failed: (buffer_get_used_size(dest) == sizeof(hdr) + (sizeof(uint32_t)*2
- hdr.fields_count) Dec 10 01:49:27 one dovecot: child 15274 (imap) killed with signal 6
errors, even after clearing all dovecot files in my maildir
On 10.12.2004, at 02:50, Tom Sommer wrote:
I still get a lot of
Dec 10 01:49:27 one dovecot: IMAP(ts@example.com): file mail-cache-fields.c: line 356 (mail_cache_header_fields_get): assertion failed: (buffer_get_used_size(dest) == sizeof(hdr) + (sizeof(uint32_t)*2 + 2) * hdr.fields_count) Dec 10 01:49:27 one dovecot: child 15274 (imap) killed with signal 6
errors, even after clearing all dovecot files in my maildir
Please try 1.0-test58. It's not completely fixed, but I'd like to know if instead of the assert you get:
Duplicate field in header: xxx
and if so, what is the header that is duplicated? What IMAP clients are accessing the mailbox?
participants (5)
-
Brad
-
Christian Balzer
-
Curtis Maloney
-
Timo Sirainen
-
Tom Sommer