search for: v2.1

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

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

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

-----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 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

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

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

Hi, all, Please tell me about the patch and description below. https://github.com/dovecot/core/commit/5f46b863383fc94afcd2693ecae8788cb5fdd20c example-config: Use a default uncommented "namespace inbox". https://doc.dovecot.org/configuration_manual/namespace/ There's a default inbox namespace added in 10-mail.conf. If the configuration doesn't explicitly specify a

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

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 ((""

I'll release v2.1.rc6 in maybe 16 hours or so. If no problems are reported in it after a few days I'll just change version to 2.1.0. So now's a great time to try the latest v2.1 hg version to see if there are any problems. I've gone through all of my old mails. Let me know if you think something is still missing / unfixed in v2.1 hg. Preferably today. Next up: Creating

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

While trying to test v.2.1.rc1 with configure \ --with-lucene \ --without-stemmer \ [...] I get the following error: [...] /bin/sh ../../../libtool --tag=CXX --mode=compile i686-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../../.. -I../../../src/lib -I../../../src/lib-mail -I../../../src/lib-index -I../../../src/lib-storage -I../../../src/plugins/fts -I../../../src/doveadm -O2 -march=i686

http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc3.tar.gz http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc3.tar.gz.sig Whops, rc2 was missing a file. I always run "make distcheck", which should catch these, but recently it has always failed due to clang static checking giving one "error" that I didn't really want to fix. Because of that the distcheck didn't finish and

http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc3.tar.gz http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc3.tar.gz.sig Whops, rc2 was missing a file. I always run "make distcheck", which should catch these, but recently it has always failed due to clang static checking giving one "error" that I didn't really want to fix. Because of that the distcheck didn't finish and

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.1/rc/dovecot-2.1.rc7.tar.gz http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc7.tar.gz.sig Okay, one more RC, because I needed a new feature implemented and forgot I wasn't supposed to do any changes anymore before v2.1.0. After that I figured I'll just do a few more changes and release RC7. So, v2.1.0 will probably be released within 1-2 days. So, the one new