similar to: v2.2.30 release candidate released

On 30 May 2017 at 21:16, Timo Sirainen <tss at iki.fi> wrote: > https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz > https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz.sig > > * auth: Use timing safe comparisons for everything related to > passwords. It's unlikely that these could have been used for > practical attacks, especially because Dovecot delays

https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz.sig * auth: Use timing safe comparisons for everything related to passwords. It's unlikely that these could have been used for practical attacks, especially because Dovecot delays and flushes all failed authentications in 2 second intervals. Also it could have worked only

https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz.sig * auth: Use timing safe comparisons for everything related to passwords. It's unlikely that these could have been used for practical attacks, especially because Dovecot delays and flushes all failed authentications in 2 second intervals. Also it could have worked only

At least doveconf -n output would help. I guess related to authentication settings. Are there any errors in logs? > On 1 Jun 2017, at 12.14, Odhiambo Washington <odhiambo at gmail.com> wrote: > >> On 30 May 2017 at 21:16, Timo Sirainen <tss at iki.fi> wrote: >> >> https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz >>

Le 30/05/2017 ? 20:16, Timo Sirainen a ?crit : > https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz > https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz.sig > > * auth: Use timing safe comparisons for everything related to > passwords. It's unlikely that these could have been used for > practical attacks, especially because Dovecot delays and flushes all

Hi experts. in the output of imapsync I found: Host2: found quota, presented in raw IMAP Sending: 7 GETQUOTAROOT INBOX Sent 22 bytes Read: * QUOTAROOT INBOX "User quota" * QUOTA "User quota" (STORAGE 420325 1953125) 7 OK Getquotaroot completed (0.001 + 0.000 secs). Host2: Quota current storage is 430412800 bytes. Limit is 2000000000 bytes. So

This is a followup to my thread "Recommended Protocols?". The error message is as follows: dovecot: imap-login: Disconnected: TLS: SSL_read() failed: SSL routines:ssl3_read_bytes:sslv3 alert bad certificate: SSL alert number 42 I have selected both SSL/TLS and STARTTLS on the Thunderbird side, with identical results. The first question that I have is this. Is there any way to know

Hi, I have a fedora28 system with dovecot-2.3.5 and I'm trying to figure out why I'm increasingly receiving duplicate emails. The message IDs are exactly the same. It's always two of the same messages. I don't think it's ever occurred in the inbox. It doesn't happen with every message or seemingly in every folder. I've read about dovecot deduplicate, but of course I

i'm attempting to dsync from a remote/other IMAP store to my current/new dovecot instance testing remote's IMAP access from the local/dovecot box, i can successfully login openssl s_client \ -crlf \ -4 \ -showcerts \ -bind 10.0.1.10 \ -connect remote-imap.example.com:993 \ -cert /sec/vmail/client.EC.crt.pem \ -key /sec/vmail/client.EC.key.pem \ -CAfile

On 30/05/2017 19:16, Timo Sirainen wrote: > https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz There is a build problem in the configure/make/libtool process when using "./configure ... --with-storages=maildir ...". libtool: link: cc -G -h lib10_quota_plugin.so -o .libs/lib10_quota_plugin.so .libs/quota.o .libs/quota-count.o .libs/quota-fs.o .libs/quota-dict.o

On 31/05/2017 8:54 PM, James wrote: > On 30/05/2017 19:16, Timo Sirainen wrote: > >> https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz > > There is a build problem in the configure/make/libtool process when > using "./configure ... --with-storages=maildir ...". This was deliberate - see the mailing list archives dated around 9 May 2017. Refer the commit

Hi, Same symptoms here when upgrading from 2.2.29 to 2.2.30. Getting back to 2.2.29 resolve the problem. The client here is a webmail ( rainloop ). User automatically logout as if the auth did'nt succed although log show successfull login attempt My configuration 2.2.29.1 (e0b76e3): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.18 (29cc74d) # OS: Linux 4.11.2-gentoo-xxxx-std-ipv6-64

unfortunately after re-installing 2.3.11.3, those broken-pipe errors appear again. (on different, new files) so for sure there is something broken with zlib. I will go back to2.3.10.1 now. attached is the configuration file, though it did not change between 2.3.10.1 and 2.3.11.3 Robert Am 26.08.2020 um 09:42 schrieb Robert Nowotny: > I had 4 broken mdbox files for 4 different users. >

Hi all! I have two dovecot servers with dsync replication over tcp. Replication works fine except for one user. # doveadm replicator status username priority fast sync full sync success sync failed customer at example.com none 00:00:33 07:03:23 03:22:31 y If i run dsync manually, i get the following error message: dsync-local(customer at example.com): Debug: brain M: -- Mailbox

We are pleased to release v2.3.20 of Dovecot. https://dovecot.org/releases/2.3/dovecot-2.3.20.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.20.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Regards, Aki Tuomi Open-Xchange oy -- + Add dsync_features=no-header-hashes. When this setting is enabled and one dsync side

We are pleased to release v2.3.20 of Dovecot. https://dovecot.org/releases/2.3/dovecot-2.3.20.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.20.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Regards, Aki Tuomi Open-Xchange oy -- + Add dsync_features=no-header-hashes. When this setting is enabled and one dsync side

On Tue, Jun 20, 2017 at 12:45 PM, Timo Sirainen <tss at iki.fi> wrote: > https://dovecot.org/releases/2.2/rc/dovecot-2.2.31.rc1.tar.gz > https://dovecot.org/releases/2.2/rc/dovecot-2.2.31.rc1.tar.gz.sig > > Unless new bugs are found, this will be the final v2.2.31 release, which > will be released on Monday. > > * LMTP: Removed "(Dovecot)" from added Received

http://dovecot.org/releases/2.2/dovecot-2.2.26.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.26.tar.gz.sig There were some changes since rc1: https://github.com/dovecot/core/commit/54d654098032d96975b70749b505fae538e97f7a Mainly there are quite a lot of director fixes and improvements. Here's the full list of changes: * master: Removed hardcoded 511 backlog limit for listen(). The

http://dovecot.org/releases/2.2/dovecot-2.2.26.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.26.tar.gz.sig There were some changes since rc1: https://github.com/dovecot/core/commit/54d654098032d96975b70749b505fae538e97f7a Mainly there are quite a lot of director fixes and improvements. Here's the full list of changes: * master: Removed hardcoded 511 backlog limit for listen(). The

https://dovecot.org/releases/2.2/rc/dovecot-2.2.31.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.31.rc1.tar.gz.sig Unless new bugs are found, this will be the final v2.2.31 release, which will be released on Monday. * LMTP: Removed "(Dovecot)" from added Received headers. Some installations want to hide it, and there's not really any good reason for anyone to