similar to: Huge difference between the lucene index size created by v2.1 and v2.2

OK, gurus, I've spent the last 2 days crawling through all of the posts and web postings regarding shared folders, and I simply cannot get it to work. I'm sure that there is something simple that I've overlooked, but cannot for the life of me see it :) Here's my current config: # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-46-generic x86_64 Ubuntu

I have a CentOS 7 server that is running out of memory and I can't figure out why. Running "free -h" gives me this: ????????????? total??????? used??????? free????? shared? buff/cache?? available Mem:?????????? 3.4G??????? 2.4G??????? 123M??????? 5.9M??????? 928M??????? 626M Swap:????????? 1.9G??????? 294M??????? 1.6G The problem is that I can't find 2.4G of usage.? If I look

I would like to report a bug we are seeing on an new deployment here: Linux: Debian Jessie, inside a Docker container Dovecot version: 2.2.23 (806d709) / 2.2.23-1~bpo8+1 doveconf -n: http://pastebin.com/2xA2xuRw Filesystem: CephFS - Jewel After migrating our users from our old server to our new one we can't access a few mailboxes. Backtrace follows: root at dovecot:/# gdb --args

On 11.05.2016 22:45, Daniel van Ham Colchete wrote: > I can confirm that this bug also happens on the latest version available: > > root at dovecot:/# dovecot --version > 2.2.devel (ebf2e93) > root at dovecot:/# dpkg -l|grep dovecot > ii dovecot-core 2:2.2.24-1~auto+23 amd64 > secure POP3/IMAP server - core files > ii dovecot-dbg

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

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

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

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

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

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

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

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

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

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

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