similar to: Dovecot/doveadm quota

Doesn't it currently confuse them? Because they'd reach their quota, while actually there would be a lot of disk space left :) + their whole mailbox could take a lot more space due to indexes and other files in the filesystem, and quota would not be reached. Also, I've dovecot is using fstat's st_size parameter. This is not "correct", in that the actual space used on

I think that most admins do not really care about physical disk usage as long as it's not exceeded, and most service providers prefer calculating quota against apparent usage instead of real usage, so they can charge you for that. Aki On 8.2.2020 18.16, Martynas Bendorius wrote: > Doesn't it currently confuse them? Because they'd reach their quota, while actually there would be a

I think these changes will confuse users because calculated quota wouldn't be equals with total messages sizes. Marsistynas Bendorius ????? 2020-02-07 11:07: > Is there any reason why dovecot relies on S= instead of real disk size > email takes? > > 1) compressed mails take less than than the S= specified > 2) we could avoid using "S=" for the lookups and count

I try to use Mailcrypt encrypted user keys with conjustion with dbsync replication(Dovecot 2.3.6 in FreeBSD 12.0 enviroment) but was unsuccessful. If I provide a password in mail_crypt_private_password variable directly in Dovecot config all things works as expected plugin { mail_crypt_curve = prime256v1 mail_crypt_save_version = 2 mail_crypt_require_encrypted_user_key = yes

Thank you. Will be waiting for Dovecot update. Aki Tuomi ????? 2017-02-28 20:34: >> On February 28, 2017 at 7:43 PM Max Kostikov <max at kostikov.co> wrote: >> >> >> Got it. >> Here is full backtrace output. >> > > Would appear the bug is in 'Trash' plugin. We'll open an issue about > this, thank you for reporting this. > >

Hello, Maildirlock seems to panic on locking: [root at centos7 home]# /usr/libexec/dovecot/maildirlock "/home/user/imap/domain.com/email/Maildir" 10 Panic: BUG: No IOs or timeouts set. Not waiting for infinity. Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xd90ee) [0x7f5bf02f10ee] -> /usr/lib/dovecot/libdovecot.so.0(+0xd9131) [0x7f5bf02f1131] ->

Probably I need to compile 2.2.28 from sources with debug flags. Can you tell me wich flags I need to set for more informative backtrace in gdb? Aki Tuomi ????? 2017-02-28 17:42: > Can you please issue > bt full > in gdb and post the output here? -- With best regards, Max Kostikov BBM: 24CA5DF8 | W: https://kostikov.co -- With best regards, Max Kostikov BBM: 24CA5DF8 | W:

I just recreated configuration of Dovecot 2.2.28 and got the same error but in imap service (it was there in logs too as for dovecot-lda but I don't saw it at time). > Feb 27 20:09:41 beta dovecot: imap(postmaster at peek.ru): Panic: file > mail-namespace.c: line 709 (mail_namespace_find): assertion failed: (ns > != NULL) > Feb 27 20:09:47 beta dovecot: lda(my at domain.ru):

Got it. Here is full backtrace output. # gdb /usr/local/libexec/dovecot/imap 1 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB.

Hello, Is there any ETA set for JMAP support? Thank you! >> On 11/27/2016 5:28 AM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: >> Hi! >> We are working on including JMAP support to Dovecot. At this moment I cannot give any promise for exact version, but hopefully it will be part of v2.3 >> >> Aki Tuomi >> Dovecot Oy -- Best regards, Martynas Bendorius

We are pleased to release v2.3.9.3 of Dovecot. Please find it from locations below https://dovecot.org/releases/2.3/dovecot-2.3.9.3.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.9.3.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot --- v2.3.9.3 2019-02-12? Aki Tuomi <aki.tuomi at open-xchange.com> ??? * CVE-2020-7046:

We are pleased to release v2.3.9.3 of Dovecot. Please find it from locations below https://dovecot.org/releases/2.3/dovecot-2.3.9.3.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.9.3.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot --- v2.3.9.3 2019-02-12? Aki Tuomi <aki.tuomi at open-xchange.com> ??? * CVE-2020-7046:

Hi! I posted this problem few days ago in FreeBSD bugtracker https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217364 So, the problem is in crash of dovecot-lda client while local mailbox delivery with this message in log > dovecot: lda(my at email): Panic: file mail-namespace.c: line 709 > (mail_namespace_find): assertion failed: (ns != NULL) My Dovecot config stills the same from

On 08 Dec 2019, at 05:58, @lbutlr <kremels at kreme.com> wrote: > On 06 Dec 2019, at 16:28, Martynas Bendorius <martynas at martynas.it> wrote: >> when zlib compression is enabled in dovecot, old emails remain untouched > > I?ve been considering doing this, or at least looking into how much space we?d save (answer so far, less than you might think), but I am hesitant to

Hello, Aki created this patch a while ago: http://files1.directadmin.com/services/custombuild/patches/maildirlock-crash.patch It works perfectly to fix the issue :) Regarding dsync - I don't think it's a good replacement in all the cases, is it? We use maildirlock extensively for compression of email folders (when zlib compression is enabled in dovecot, old emails remain untouched). --

Dovecot 2.3.2 still has the same issue we reported for 2.3.X: Jul 05 15:10:49 lmtp(2730445): Panic: file lib-event.c: line 182 (event_pop_global): assertion failed: (event != NULL) Jul 05 15:10:49 lmtp(2730445): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xce054) [0x7f7f7c92f054] -> /usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7f7f7c92f09a] ->

Just made FreeBSD 8.1 portupgrade to new Dovecot version 1.2.16 from 1.2.14_1. In message log I has many records such this > Jan 4 23:30:11 beta kernel: pid 15096 (dovecot-auth), uid 0: exited on s >> ignal 11 (core dumped) > > Jan 4 23:30:11 beta kernel: pid 15097 (dovecot-auth), uid 0: exited on s >> ignal 11 (core dumped) > > Jan 4 23:30:11 beta kernel: pid 15098

Dovecot version: 2.3.1 (happens with 2.3.x too) OS: CentOS 7 64-bit Mar 28 16:29:24 lmtp(30383): Panic: file lib-event.c: line 182 (event_pop_global): assertion failed: (event != NULL) Mar 28 16:29:24 lmtp(30383): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xcc7a4) [0x7fac7f5177a4] -> /usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7fac7f5177ea] ->

Core was generated by `dovecot/indexer-worker'. Program terminated with signal 11, Segmentation fault. #0 0x00007f30f7ad056d in __exchange_and_add (__val=-1, __mem=0xfffffffffffffff8) at /usr/src/debug/gcc-4.8.5-20150702/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/ext/atomicity.h:49 49 { return __atomic_fetch_add(__mem, __val, __ATOMIC_ACQ_REL); } (gdb) bt full #0

Dear all, Dovecot upgraded from v2.2.36 to v2.3.8 There is no problem with the configuration, but the lock directory seems to have an error. [root at spam dovecot]# /usr/libexec/dovecot/maildirlock /path/to/maildir 1 Panic: BUG: No IOs or timeouts set. Not waiting for infinity. 19276[root at spam dovecot]# Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xe227a) [0x7f1cb567a27a]