Displaying 20 results from an estimated 3000 matches similar to: "v2.2.30 release candidate released"
2017 Jun 01
0
v2.2.30 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
2017 May 30
7
v2.2.30 released
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
2017 May 30
7
v2.2.30 released
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
2017 Jun 01
3
v2.2.30 released
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
>>
2017 May 31
0
v2.2.30 released
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
2020 Jul 23
2
dsync fails for existing user: "Error: Failed to initialize user: Namespace '': Mailbox list driver imapc: missing imapc_password" ?
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
2022 Dec 22
2
Dovecot v2.3.20 released
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
2022 Dec 22
2
Dovecot v2.3.20 released
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
2017 May 31
0
v2.2.30 released
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
2017 Jun 23
0
v2.2.31 release candidate released
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
2020 Jul 03
0
Quota: How/where to set/change
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
2017 May 31
1
v2.2.30 released
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
2017 Jun 13
0
v2.2.30 released
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
2017 Jun 20
4
v2.2.31 release candidate released
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
2017 Jun 20
4
v2.2.31 release candidate released
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
2017 May 31
1
v2.2.30 released
On 05/31/2017 12:54 PM, James wrote:
> This can be avoided if "--with-storages=maildir,imapc" is used to build.
> I could not find a proper solution in the time I had.
Recently Timo said "Don't use --with-storages=maildir. The benefits are
very close to zero. I think I'll just remove that configure option
entirely". So, it's been removed, I suppose.
--
2016 Oct 27
3
v2.2.26 released
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
2016 Oct 27
3
v2.2.26 released
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
2020 Nov 10
3
SSL alert number 42
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
2019 Mar 27
0
doveadm backup doesn't transfer mail from root INBOX
Hi,
I'm trying to migrate IMAP mails from dovecot 1.1.20apple0.5 (osx) to
dovecot 2.2.33.2 (ubuntu). I'm using "doveadm backup" to migrate my data.
It works fine for all subfolders, but the root INBOX stay empty on the new
server. I suspect a problem related with hierarchy separator ("." on
previous server, "/" on new) or with the namespace prefix (set to