similar to: maildirlock fails

It seems something like this has been reported already, however, I was unable to find any changelog entries or patches: http://dovecot.2317879.n4.nabble.com/maildirlock-time-unit-td65122.html -- Best regards, Martynas Bendorius > On 12 Apr 2019, at 01:08, Martynas Bendorius <martynas at martynas.it> wrote: > > Hello, > > Maildirlock seems to panic on locking: > [root

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

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]

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

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:

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

Hello, 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 every file there, including indexes and mails without S=... if we'd read filesizes Eample: # ls -l '1567026317.M331058P4751.testing.server.com,S=3086,W=3148:2,S' -rw-------

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

What is the time unit maildirlock will accept? I've tried 20s, 20 sec, 20 secs, 20 seconds, all results in: Fatal: Invalid timeout value: 20s And if you don't specify time unit you just get: Panic: BUG: No IOs or timeouts set. Not waiting for infinity. This is on 2.3.3. 2.2 worked fine without needing time unit specified. -------------- next part -------------- A non-text attachment

<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> <br> </div> <blockquote type="cite"> <div> On 27 October 2018 at 21:32 Kris von Mach < <a href="mailto:mach@swishmail.com">mach@swishmail.com</a>> wrote: </div> <div>

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 ?alter? the user?s mail stores without a bit more guidance. Has anyone found a good

This appears to be a bug. On 10/15/2018 9:46 PM, Kris von Mach wrote: > What is the time unit maildirlock will accept? > > I've tried 20s, 20 sec, 20 secs, 20 seconds, all results in: > Fatal: Invalid timeout value: 20s > > And if you don't specify time unit you just get: > Panic: BUG: No IOs or timeouts set. Not waiting for infinity. > > This is on 2.3.3. 2.2

On 22/10/2019 05:44, lty--- via dovecot wrote: > 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:

Don't think maildirlock uses dovecot config, but sure. maildirlock is a utility that comes with dovecot... #? /usr/local/libexec/dovecot/maildirlock -h Usage: maildirlock <path> <timeout> ?- SIGTERM will release the lock. # /usr/local/libexec/dovecot/maildirlock /home2/vpopmail/domains/swishmail.com/mach/Maildir 20s Fatal: Invalid timeout value: 20s #

Hello I have Samba that joined Windows 2003 based ADS. At least "net ads testjoin" and "net rpc testjoin" gives that "Join is OK". Alas clients can't connect to Samba server. In a log I see following messages : [2005/04/08 14:51:41, 0] tdb/tdbutil.c:(725) tdb(/web/opt/etc/smbprivate//secrets.tdb): tdb_lock failed on list 2 ltype=2 (Resource temporarily

Hello What is sequence for "auth methods" running in ADS mode ? How I can find this ? With best regards Martynas