similar to: v1.2.11 released

v1.1 plans have changed a bit. I'll release v1.1.alpha1 soon and hope to have a stable v1.1 in a month or two. The rest of the features that didn't make it into v1.1 will go to v1.2. I'll write more about this when v1.1 alpha is released. I also did a bit of benchmarking. v1.1's performance improvements are looking pretty great, it seems to be twice as fast as v1.0. v1.0:

http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz.sig This is the first alpha release of Dovecot v1.1. I hope that it stabilizes into final release within a few months. There are a lot of new features since v1.0. The most important ones are listed at the end of this post. This is the only v1.1.alpha announcement I send

http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz.sig This is the first alpha release of Dovecot v1.1. I hope that it stabilizes into final release within a few months. There are a lot of new features since v1.0. The most important ones are listed at the end of this post. This is the only v1.1.alpha announcement I send

http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta9.tar.gz http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta9.tar.gz.sig Some changes since beta8: - This release should work perfectly with NFS attribute cache enabled. - Fixes to handling what should be written to cache file and when - Some index handling optimizations - IMAP LIST: dbox and cydir can now return children state Beta9 will

Hello Dovecot users, Pigeonhole development has slowed down significantly in the last few months due to the fact that I got swamped in work. The plan is now to move active development of Pigeonhole to Dovecot v2.0, meaning that this will be the last release for v1.2 that contains significant development changes and new features. However, if a certain new feature is simple enough and there is

Hello Dovecot users, Pigeonhole development has slowed down significantly in the last few months due to the fact that I got swamped in work. The plan is now to move active development of Pigeonhole to Dovecot v2.0, meaning that this will be the last release for v1.2 that contains significant development changes and new features. However, if a certain new feature is simple enough and there is

The biggest problem with getting v1.0 out was getting its index file code stable. v1.1 plans included doing large changes to the index file code, so it's important to get the new code stable as soon as possible. Since I've managed to stay pretty productive for the last few weeks, I've been mostly just coding the index changes. Once I'm sure that the code is again fully working

Hi! After searching for hours now, I give up and have to ask here. I try to use the expire plugin but it always tries to expire my mails instead of the mails of the user. I read about the "Mail location setting problem (v1.1-v1.2) and configured a "mail" extra field in the userdb, but that doesn't have the effect I want. I have not idea, what I could try out more, so I ask

http://dovecot.org/releases/1.1/dovecot-1.1.5.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.5.tar.gz.sig http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha3.tar.gz http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha3.tar.gz.sig A combined release announcement for a change. :) Largest changes since v1.1.4: * Dovecot prints an informational message about authentication problems

http://dovecot.org/releases/1.1/dovecot-1.1.5.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.5.tar.gz.sig http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha3.tar.gz http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha3.tar.gz.sig A combined release announcement for a change. :) Largest changes since v1.1.4: * Dovecot prints an informational message about authentication problems

Hi all We are planning to upgrade Dovecot from production version 1.0.10 to latest version 1.2.9 Users are using maildir style mailboxes with ~20 GB of messages on SLES10 server. Upgrade will be done by installing new server and then migrating mailboxes from old on new server. Since dovecot-uidlist file have new format and index files have changed in v1.1, what must be done to have new

Hello, While updating the ManageSieve implementation to the latest draft specification I noticed a major omission in the way script names are handled. Essentially, script names are directly appended to the sieve storage directory path and suffixed with '.sieve'. This does not take the use of '../' in script names into account. Therefore, clever virtual users that know the

Hello, While updating the ManageSieve implementation to the latest draft specification I noticed a major omission in the way script names are handled. Essentially, script names are directly appended to the sieve storage directory path and suffixed with '.sieve'. This does not take the use of '../' in script names into account. Therefore, clever virtual users that know the

Dear All, I constantly encounter 'dovecot-auth', 'login-imap', 'login-pop3' and 'imap' processes consume 100% CPU. I run 'ps' and found those hanged up processes were running for a long time. I am wondering whether dovecot.conf has some configuration parameters that timeout those processes (or kill those after certain period of time). I am using dovecot

I was thinking about documentation for alternate storage. We have a few mentions at: http://wiki2.dovecot.org/MailboxFormat/dbox http://wiki2.dovecot.org/Tools/Doveadm http://wiki2.dovecot.org/Tools/Doveadm/Altmove But I was thinking it would be helpful if there could be a page about alternate storage. I could write the page, but I currently have so many unknowns that I think it would be

http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta4.tar.gz http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta4.tar.gz.sig This release fixes a memory corruption bug related to MODSEQ handling in earlier v1.2 releases. Memory corruption means that it's a security bug and possibly exploitable. MODSEQ code is new in v1.2, so v1.1 and older releases are not affected. Other than that, there

http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta4.tar.gz http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta4.tar.gz.sig This release fixes a memory corruption bug related to MODSEQ handling in earlier v1.2 releases. Memory corruption means that it's a security bug and possibly exploitable. MODSEQ code is new in v1.2, so v1.1 and older releases are not affected. Other than that, there

I just downloaded 1.2.11 and compiled from source including mysql support and using default directory locations. I walked thru the included example conf file and tweaked it out and get an invalid configuration file. I trimmed out all of the commented sections to make the non-default config super easy to navigate during troubleshooting. Remaining config which gives an error of

Hi all, Lets say I have a maildir which doesn't contain any dovecot files but has some emails lying around in it. If I add a message to this mailbox using deliver, dovecot creates the uidlist file with a single entry (the message that was just delivered). When I then log in to the mailbox, all the other messages are added into the uidlist file in the normal order (directory list order I

Hello Dovecot users, This is a simultaneous release of new versions of Sieve-related software for Dovecot v1.1 and v1.2. Only the Sieve implementation itself has seen significant development. The ManageSieve packages only have small fixes and the ManageSieve patches are updated as usual to match the new Dovecot releases. Changelog Sieve v0.1.5: * Ported the implementation of the Sieve