Displaying 20 results from an estimated 900 matches similar to: "v2.2.31 release candidate released"
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
2017 Jun 26
0
v2.2.31 released
https://dovecot.org/releases/2.2/dovecot-2.2.31.tar.gz
https://dovecot.org/releases/2.2/dovecot-2.2.31.tar.gz.sig
This should be a great and stable release for the summer :) v2.2.32 is planned for the end of August. Hopefully soon afterwards we can get back to v2.3.
* LMTP: Removed "(Dovecot)" from added Received headers. Some
installations want to hide it, and there's not
2017 Jun 26
0
v2.2.31 released
https://dovecot.org/releases/2.2/dovecot-2.2.31.tar.gz
https://dovecot.org/releases/2.2/dovecot-2.2.31.tar.gz.sig
This should be a great and stable release for the summer :) v2.2.32 is planned for the end of August. Hopefully soon afterwards we can get back to v2.3.
* LMTP: Removed "(Dovecot)" from added Received headers. Some
installations want to hide it, and there's not
2017 Jun 23
1
v2.2.31 release candidate released
On 23 Jun 2017, at 3.44, Mark Moseley <moseleymark at gmail.com> wrote:
>
> It'd be great if https://dovecot.org/list/dovecot/2016-June/104763.html
> could make it into this RC (assuming you guys approved it back when it was
> submitted)
I'll try to get it to 2.2.32. 2.2.31 won't have any changes anymore that aren't absolutely required.
2017 Jun 29
3
NOTIFY broken in 2.2.31?
Hi,
I just updated my Dovecot to the new build in Fedora 26, which is based
on 2.2.31. After I did that, Evolution (3.24.3) is no longer receiving
notifications about new mail in folders other than inbox (the same
version of Evo that worked fine against Dovecot 2.2.30.2). The only
folder that still gets notifications is inbox.
I see there have been changes to NOTIFY code in this release. What
2017 Aug 24
1
v2.2.32 released
https://dovecot.org/releases/2.2/dovecot-2.2.32.tar.gz
https://dovecot.org/releases/2.2/dovecot-2.2.32.tar.gz.sig
Two more fixes since rc2. And repeating:
There are various changes in this release that can be used to significantly reduce disk IO with:
1) NFS storage especially, but I guess also other remote filesystems and even some with local disks
2) When mail storage and INDEX storage are
2017 Aug 24
1
v2.2.32 released
https://dovecot.org/releases/2.2/dovecot-2.2.32.tar.gz
https://dovecot.org/releases/2.2/dovecot-2.2.32.tar.gz.sig
Two more fixes since rc2. And repeating:
There are various changes in this release that can be used to significantly reduce disk IO with:
1) NFS storage especially, but I guess also other remote filesystems and even some with local disks
2) When mail storage and INDEX storage are
2018 Mar 08
2
Extra intermediate certificate when using ssl_alt_cert
I just added an ECDSA certificate to my mail server using ssl_alt_cert (the RSA certificate is specified by ssl_cert), both certificate files contain the certificate and a single intermediate (which currently happens to be the same intermediate from Let?s Encrypt).
When connecting to the server using either RSA or ECDSA ciphers, the server sends the proper certificate, but also sends two
2017 May 31
8
v2.2.30.1 released
https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz
https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz.sig
Due to some release process changes I didn't notice that one important bugfix wasn't included in the v2.2.30 release branch before I made the release. So fixing it here with v2.2.30.1. Also included another less important fix.
- quota_warning scripts weren't
2017 May 31
8
v2.2.30.1 released
https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz
https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz.sig
Due to some release process changes I didn't notice that one important bugfix wasn't included in the v2.2.30 release branch before I made the release. So fixing it here with v2.2.30.1. Also included another less important fix.
- quota_warning scripts weren't
2019 Jan 16
2
auth-worker: Error: double free or corruption (fasttop)
Dear list,
since the distri upgrade to glibc 2.28, i can't build working dovecot
binary's.
Older with glibc 2.27 are working. The distri is LFS based.
MariaDB 10.2.18 and 10.3.11 makes no difference. Having this on
different systems.
Messages Log:
Dec 19 17:10:38 test kernel: traps: auth[30189] general protection
ip:7f4b96d6598c sp:7ffef1f31710 error:0 in
2018 Mar 10
1
quota-status: Issues with uppercase recipient address
Hello list,
Dovecot Version: 2.2.34 (874deae) on FreeBSD
MTA: Postfix 3.3.0
I've got an issue with the quota-status service:
Something breaks when receiving mail with a recipient address that includes non-lowercase characters,
for example foo at Example.com instead of foo at example.com:
postfix log:
postfix/smtp/smtpd[83387]: NOQUEUE: reject_warning: RCPT from
2020 Aug 25
2
zlib errors after upgrading
> On 25/08/2020 14:35 Robert Nowotny <rnowotny at rotek.at> wrote:
>
>
> I get ZLIB Errors after dovecot upgrade from 2.3.10.1 to 2.3.11.3
>
>
> Aug 21 15:27:34 lxc-imap dovecot: imap(acsida)<63870><jZk...>: Error: Mailbox Sent: UID=40826: read(zlib(/home/vmail/virtualmailboxes/acsida/storage/m.2409)) failed:
2017 Jun 22
0
Released Pigeonhole v0.4.19.rc1 for Dovecot v2.2.31.rc1.
Hello Dovecot users,
This small release is mainly about adjusting to changes in the Dovecot
API. There is one significant fix.
Changelog v0.4.19:
* This release adjusts Pigeonhole to several changes in the Dovecot API,
making it depend on Dovecot v2.2.31. Previous versions of Pigeonhole
will produce compile warnings with the recent Dovecot releases (but
still work ok).
- Fixed bug in
2017 Jun 26
0
Released Pigeonhole v0.4.19 for Dovecot v2.2.31.
Hello Dovecot users,
Here's the definitive 0.4.19 release. There is one additional fix.
Changelog v0.4.19:
* This release adjusts Pigeonhole to several changes in the Dovecot API,
making it depend on Dovecot v2.2.31. Previous versions of Pigeonhole
will produce compile warnings with the recent Dovecot releases (but
still work ok).
- Fixed bug in handling of implicit keep in some
2017 Jun 22
0
Released Pigeonhole v0.4.19.rc1 for Dovecot v2.2.31.rc1.
Hello Dovecot users,
This small release is mainly about adjusting to changes in the Dovecot
API. There is one significant fix.
Changelog v0.4.19:
* This release adjusts Pigeonhole to several changes in the Dovecot API,
making it depend on Dovecot v2.2.31. Previous versions of Pigeonhole
will produce compile warnings with the recent Dovecot releases (but
still work ok).
- Fixed bug in
2017 Jun 26
0
Released Pigeonhole v0.4.19 for Dovecot v2.2.31.
Hello Dovecot users,
Here's the definitive 0.4.19 release. There is one additional fix.
Changelog v0.4.19:
* This release adjusts Pigeonhole to several changes in the Dovecot API,
making it depend on Dovecot v2.2.31. Previous versions of Pigeonhole
will produce compile warnings with the recent Dovecot releases (but
still work ok).
- Fixed bug in handling of implicit keep in some
2018 Mar 10
3
Extra intermediate certificate when using ssl_alt_cert
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
<br>
</div>
<blockquote type="cite">
<div>
On 10 March 2018 at 14:49 John Fawcett <
<a href="mailto:john@voipsupport.it">john@voipsupport.it</a>> wrote:
</div>
<div>
2018 Mar 10
2
Extra intermediate certificate when using ssl_alt_cert
> On 10 March 2018 at 15:20 John Fawcett <john at voipsupport.it> wrote:
>
>
> On 10/03/18 14:06, Aki Tuomi wrote:
> >
> >> On 10 March 2018 at 14:49 John Fawcett < john at voipsupport.it
> >> <mailto:john at voipsupport.it>> wrote:
> >>
> >>
> >> On 08/03/18 18:43, Peter Linss wrote:
> >>> I just added
2017 May 31
0
v2.2.30.1 released
On 2017-05-31 15:24, Timo Sirainen wrote:
> https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz
> https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz.sig
>
> Due to some release process changes I didn't notice that one important
> bugfix wasn't included in the v2.2.30 release branch before I made the
> release. So fixing it here with v2.2.30.1. Also included