similar to: v2.2.36 release candidate released

Displaying 20 results from an estimated 700 matches similar to: "v2.2.36 release candidate released"

2018 Apr 03
3
2.3.1 Replication is throwing scary errors
Hi, > ------------------------------ > > Message: 2 > Date: Mon, 2 Apr 2018 22:06:07 +0200 > From: Michael Grimm <trashcan at ellael.org> > To: Dovecot Mailing List <dovecot at dovecot.org> > Subject: 2.3.1 Replication is throwing scary errors > Message-ID: <29998016-D62F-4348-93D1-613B13DA90DB at ellael.org> > Content-Type: text/plain; charset=utf-8
2018 Mar 27
0
Duplicate mails on pop3 expunge with dsync replication on 2.2.35 (2.2.33.2 works)
Hello, consider the following setup with dovecot 2.2.35: smtp/587 (subject: test 1535) | | mx2a.example.com --> dsync/ssh --> mx2b.example.com | pop3 fetch/expunge (uid 23) | !! dsync (copy from INBOX -> uid 24) /| dsync
2019 Dec 06
0
v2.2.36 to v2.3.8 maildirlock bug
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:
2019 Oct 22
2
v2.2.36 to v2.3.8 maildirlock bug
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]
2018 May 08
0
Released Pigeonhole v0.4.24.rc1 for Dovecot v2.2.36.rc1.
Hello Dovecot users, Here's a first release candidate for the upcoming Pigeonhole release for Dovecot v2.2.36. It only contains bugfixes for now. There's one experimental plugin still in the pipeline. Changelog v0.4.24: - Fix assert panics triggered by empty messages that are being forwarded using redirect or vnd.dovecot.report. This does not likely normally occur, but this is
2018 May 24
0
Released Pigeonhole v0.4.24 for Dovecot v2.2.36.
Hello Dovecot users, Here is the Pigeonhole release that goes with the new Dovecot v2.2.36 release. Apart from the changes that were already in the RC, this final release adds one new feature: a plugin for the IMAP FILTER=SIEVE capability. The is a vendor-defined feature that adds the ability to manually invoke Sieve filtering in IMAP. Changelog v0.4.24: + Implement plugin for the a
2018 May 03
0
v2.2.36 release candidate released
Thanks, that fixes it for me. ? John ? From: dovecot [mailto:dovecot-bounces at dovecot.org] On Behalf Of Timo Sirainen Sent: Thursday, 3 May, 2018 13:52 To: John van der Kamp <jkamp at amazon.nl> Cc: Dovecot Mailing List <dovecot at dovecot.org> Subject: Re: v2.2.36 release candidate released ? On 2 May 2018, at 12.52, John van der Kamp <jkamp at amazon.nl <mailto:jkamp at
2018 May 08
0
Released Pigeonhole v0.4.24.rc1 for Dovecot v2.2.36.rc1.
Hello Dovecot users, Here's a first release candidate for the upcoming Pigeonhole release for Dovecot v2.2.36. It only contains bugfixes for now. There's one experimental plugin still in the pipeline. Changelog v0.4.24: - Fix assert panics triggered by empty messages that are being forwarded using redirect or vnd.dovecot.report. This does not likely normally occur, but this is
2018 May 24
0
Released Pigeonhole v0.4.24 for Dovecot v2.2.36.
Hello Dovecot users, Here is the Pigeonhole release that goes with the new Dovecot v2.2.36 release. Apart from the changes that were already in the RC, this final release adds one new feature: a plugin for the IMAP FILTER=SIEVE capability. The is a vendor-defined feature that adds the ability to manually invoke Sieve filtering in IMAP. Changelog v0.4.24: + Implement plugin for the a
2018 May 23
0
v2.2.36 released
https://dovecot.org/releases/2.2/dovecot-2.2.36.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.36.tar.gz.sig This is the last planned v2.2.x release. We didn't fix everything reported (especially build changes) to try to minimize any unexpected breakages. v2.3.2 will be out with a lot of fixes hopefully in a few weeks. That will start becoming the recommended version to run then. *
2018 May 23
0
v2.2.36 released
https://dovecot.org/releases/2.2/dovecot-2.2.36.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.36.tar.gz.sig This is the last planned v2.2.x release. We didn't fix everything reported (especially build changes) to try to minimize any unexpected breakages. v2.3.2 will be out with a lot of fixes hopefully in a few weeks. That will start becoming the recommended version to run then. *
2019 Dec 08
0
v2.2.36 to v2.3.8 maildirlock bug
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
2019 Dec 06
2
v2.2.36 to v2.3.8 maildirlock bug
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). --
2019 Dec 08
1
v2.2.36 to v2.3.8 maildirlock bug
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
2018 May 02
2
v2.2.36 release candidate released
There seems to be a problem with new user directories and the imapc backend. On a test setup I get the following error in the log: May 02 10:09:58 imap(user1 at domain.com): Error: Couldn't create mailbox list lock /tmp/tmp0Y5TMn/dovecot1/users/user1 at domain.com/imapc/mailboxes.lock: file_create_locked(/tmp/tmp0Y5TMn/dovecot1/users/user1 at domain.com/imapc/mailboxes.lock) failed:
2013 May 09
1
Crossrealm Kerberos problems
I am running dovecot 2.1.7 on Debian Squeeze 64 bit, config information at the end of the email. I am working on a Kerberos/GSSAPI based setup that requires cross-realm authentication. I have regular GSSAPI working, I can log in using pam_krb5 with password based logins or with the GSSAPI support when using a kerberos ticket in the default realm. However when I attempt to authenticate using
2008 Oct 01
5
ustack()s of SIGSEGV''ed programs
Hi all, I am trying to write a D script which would print ustack() for every program in the system receiving SIGSEGV. All the stacks printed in trap()/sigtoproc() context do not have meaningful symbols. The following solves the problem to some degree but I''d much rather have a self-contained D script. dtrace -w -n ''fbt:genunix:sigtoproc:entry/arg2 == 11/ {
2020 Oct 07
1
Version controlled (git) Maildir generated by Dovecot
Or on a testing system I can just stop Dovecot, remove everything that doesn't start with a number and restart Dovecot and connect Thunderbird and see the results. Thank you. > ---------- P?vodn? e-mail ---------- > Od: Gerald Galster <list+dovecot at gcore.biz> > Komu: dovecot at dovecot.org > Datum: 7. 10. 2020 14:36:43 > P?edm?t: Re: Version controlled (git) Maildir
2006 Oct 24
15
How to emit associative array after ^C
Boy am I a dummy. I want to simply dump out unfreed allocations when I terminate the script. What''s the secret sauce? #!/usr/sbin/dtrace -s pid$1::MyAlloc:return { bufs[arg1] = walltimestamp; } pid$1::MyFree:entry /bufs[arg0]/ { bufs[arg0] = 0; } This message posted from opensolaris.org
2017 May 26
0
Replication failure between 2 Samba4 DCs
Hello guys: I'm running two Zentyal servers with Samba 4.1.17 on each one. We're experiencing some problems such as: - When a user changes his password, it is not replicated the change on secondary DC. - Some Windows machines have reported trust relationship broken. On DC1 I run this: params.c:pm_process() - Processing configuration file "/etc/samba/shares.conf" ldb_wrap open