similar to: About the changing namespace handling from v2.0 to v2.1 or later

http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc1.tar.gz http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc1.tar.gz.sig I'll probably release v2.1.0 pretty soon, unless people report some new bugs. I know v2.1 is already being used to serve mails to tens (or hundreds?) of thousands of users, so it should be pretty stable. Most of the changes since v2.1.beta1 have been for rather small

http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc1.tar.gz http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc1.tar.gz.sig I'll probably release v2.1.0 pretty soon, unless people report some new bugs. I know v2.1 is already being used to serve mails to tens (or hundreds?) of thousands of users, so it should be pretty stable. Most of the changes since v2.1.beta1 have been for rather small

Hello Timo, There seems to be something broken in v2.1 latest hg version: # 2.1.1 (94de7605f50f) 1 namespace * NAMESPACE (("" "/")("virtual/" "/")) NIL NIL * OK Namespace completed. Please note that the "OK Namespace completed." is send untagged. It worked on below version: # 2.1.1 (315f0d8cc2b2) 1 namespace * NAMESPACE ((""

Now that v2.0 seems to be getting stable, I finally started v2.1 branch: http://hg.dovecot.org/dovecot-2.1/ So far there are just some API changes to fix some annoyances and to make it simpler. They'll probably keep coming for a while more to make future work easier. As for larger upcoming features, I'm hoping for: - simplify index files and make it write only via lib-fs (but keep

http://dovecot.org/releases/2.1/beta/dovecot-2.1.beta1.tar.gz http://dovecot.org/releases/2.1/beta/dovecot-2.1.beta1.tar.gz.sig Here's the first beta release of Dovecot v2.1. This version has already been tested quite a lot, so I'm not expecting any major bugs. So please upgrade and see if you can find any problems. I'm optimistic about getting rc1 released this year and perhaps even

http://dovecot.org/releases/2.1/beta/dovecot-2.1.beta1.tar.gz http://dovecot.org/releases/2.1/beta/dovecot-2.1.beta1.tar.gz.sig Here's the first beta release of Dovecot v2.1. This version has already been tested quite a lot, so I'm not expecting any major bugs. So please upgrade and see if you can find any problems. I'm optimistic about getting rc1 released this year and perhaps even

Hi everyone, While examining dovecot versions v2.1 and v2.2 for their lucene search performances, I have noticed a huge difference in the index sizes created by them. Both versions were compiled on same system, against same libclucene, same configure options and were used with same dovecot.conf during run-time. I deleted the lucene-indexes folder and dovecot* files in the Maildir prior to

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear Eugene, patch 49 breaks compilation with Dovecot v2.1. Attached patch encloses the change in a #if. To feed the #if the actual Dovecot version, I've introduced an extra variable in extra.mk, but I cannot help with making the GNU configure stuff doing it right away. There will be numerous other ways to get the Dovecot version into the

Hi all, I have observed in kernel 4.15 cifs.ko using protocol v2.1 getting confused about whether a "filesystem object" is a file or a directory. The true state in the example below is that "Alien" is directory and "alien" is a (perl) file. However, 'file' reports the type to be the same and matching the first object accessed, e.g. Both are perl

http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc6.tar.gz http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc6.tar.gz.sig I've finally finished all of my email backlog. If you haven't received an answer to some question/bugreport, resend the mail. This is hopefully the last v2.1 RC. If I don't receive any (serious) bug reports about this release in next few days, I'll just change

http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc6.tar.gz http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc6.tar.gz.sig I've finally finished all of my email backlog. If you haven't received an answer to some question/bugreport, resend the mail. This is hopefully the last v2.1 RC. If I don't receive any (serious) bug reports about this release in next few days, I'll just change

http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc5.tar.gz http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc5.tar.gz.sig I'm still lagging behind reading emails. v2.1.0 will be released after I've finished that. RC5 is already stable and used in production, but I want to make sure that I haven't missed anything important that was reported previously. Most of the recent fixed bugs

http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc5.tar.gz http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc5.tar.gz.sig I'm still lagging behind reading emails. v2.1.0 will be released after I've finished that. RC5 is already stable and used in production, but I want to make sure that I haven't missed anything important that was reported previously. Most of the recent fixed bugs

I'm preparing to set up a new set of directors on dovecot-ee-2.1.10.3-1, but would prefer to do this a bit gradually. Will it be OK to set up a ring of directors with 2x dovecot-ee-2.1.10.3-1 and 2x dovecot-2.0.14 ? -jf

When the Sieve plugin tries to send a vacation message or redirect a message to another address it fails. dovecot: lmtp(6412, user at example.com): Error: lmtp client: DNS lookup of orange.example.com failed: connect(dns-client) failed: No such file or directory dovecot: lmtp(6412, user at example.com): Error: dAIOClYSJE8MGQAAhQ0vrQ: sieve: msgid=<4F241255.2060900 at example.com>: failed to

http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta1.tar.gz http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta1.tar.gz.sig Now that v2.0 is in beta stage I don't expect anything big to change anymore. The configuration and the APIs shouldn't change in non-backwards compatible ways. There are still bugs left to be fixed and some small features to be implemented, but I'd like to

http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta1.tar.gz http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta1.tar.gz.sig Now that v2.0 is in beta stage I don't expect anything big to change anymore. The configuration and the APIs shouldn't change in non-backwards compatible ways. There are still bugs left to be fixed and some small features to be implemented, but I'd like to

v2.1's imap/pop3 processes are linked with OpenSSL by default, because of imapc/pop3c storages. I wonder if you notice any actual (system-global) memory usage reduction when compiling without those and you have thousands of imap processes? ./configure --with-storages=mdbox sdbox maildir mbox cydir I guess I could try it myself also but maybe someone else wanting to reduce memory usage is

Dear all, I want to start my post by expressing my sincere gratitude for all the help this group has given me in Sweave/Latex/R. The tools are excellent and so is the community! On to the question. My Sweave code is intended to make lots of plots and create a *.pdf document. Sweave is perfect for this. The only problem is that I find myself using the same R code, within my Sweave input file

A lot of doveadm commands process users' mails. They can optionally process either a single user or multiple users (e.g. -A = all, -u '*@domain.org'). For example to expunge old mails from everyone's Trash, you'd use: doveadm expunge -A mailbox Trash savedbefore 30d The problem is, this doesn't work with the new director way of doing proxying. Only a single server can