similar to: Released Pigeonhole v0.5.0 for Dovecot v2.3.0.

Hello Dovecot users, Here is the Pigeonhole release candidate that goes with the Dovecot v2.3 release candidate. Of course, a large part of this release consists of compatibility changes for Dovecot v2.3. Apart from that, not much changed, just a few additions and fixes that accumulated over the last few months. Most of these changes will be back-ported to Pigeonhole v0.4, but that release will

Hello Dovecot users, Here is the Pigeonhole release candidate that goes with the Dovecot v2.3 release candidate. Of course, a large part of this release consists of compatibility changes for Dovecot v2.3. Apart from that, not much changed, just a few additions and fixes that accumulated over the last few months. Most of these changes will be back-ported to Pigeonhole v0.4, but that release will

As soon as possible after release.? I'm the maintainer for pigeonhole, and Adam Weinberger is the maintainer for dovecot (I'm AKA ler at FreeBSD.org). Sent from my T-Mobile 4G LTE Device -------- Original message --------From: "@lbutlr" <kremels at kreme.com> Date: 12/19/17 4:19 AM (GMT-06:00) To: dovecot at dovecot.org Subject: Re: Released Pigeonhole v0.5.0.rc1 for

Hello Dovecot users, This is a bugfix release to mend some problems that were found in v0.5.0. The imap4flags bug is actually not first seen in the 0.5.0 release (it is ancient), but I included the fix for it anyway. Changelog v0.5.0.1: - imap4flags extension: Fix binary corruption occurring when setflag/addflag/removeflag flag-list is a variable. - sieve-extprograms plugin: Fix segfault

Hello Dovecot users, This is a bugfix release to mend some problems that were found in v0.5.0. The imap4flags bug is actually not first seen in the 0.5.0 release (it is ancient), but I included the fix for it anyway. Changelog v0.5.0.1: - imap4flags extension: Fix binary corruption occurring when setflag/addflag/removeflag flag-list is a variable. - sieve-extprograms plugin: Fix segfault

> On 18 Dec 2017, at 14:58, Stephan Bosch <stephan at rename-it.nl> wrote: > > Here is the Pigeonhole release candidate that goes with the Dovecot > v2.3 release candidate. Of course, a large part of this release consists > of compatibility changes for Dovecot v2.3. Apart from that, not much > changed, just a few additions and fixes that accumulated over the last > few

Hello Dovecot users, Here's the Pigeonhole RC that goes with Dovecot v2.2.20. Due to the earlier described conflict, RC1 will not compile with the new Dovecot release. I am not really in hurry to make a definitive release of Pigeonhole, since v0.4.9 still compiles fine with Dovecot v2.2.20. Still, if no big bugs emerge in the next few days, I will make a final release. So, please test this

Hello Dovecot users, Here's the Pigeonhole RC that goes with Dovecot v2.2.20. Due to the earlier described conflict, RC1 will not compile with the new Dovecot release. I am not really in hurry to make a definitive release of Pigeonhole, since v0.4.9 still compiles fine with Dovecot v2.2.20. Still, if no big bugs emerge in the next few days, I will make a final release. So, please test this

Hello Dovecot users, Here's the Pigeonhole RC that goes with the Dovecot RC. There is a conflict with the t_str_trim() function. To be able to quickly release Dovecot, Timo has reverted the involved change so that 0.4.9 will still compile with the final Dovecot v2.2.20 release. This Pigeonhole RC will therefore not compile against the final Dovecot release (only against v2.2.20.rc1), which I

Hello Dovecot users, Here's the Pigeonhole RC that goes with the Dovecot RC. There is a conflict with the t_str_trim() function. To be able to quickly release Dovecot, Timo has reverted the involved change so that 0.4.9 will still compile with the final Dovecot v2.2.20 release. This Pigeonhole RC will therefore not compile against the final Dovecot release (only against v2.2.20.rc1), which I

Hello Dovecot users, I got a bit stalled by our recent switch to Git, but here is the final v0.4.10 release of Pigeonhole for Dovecot v2.2.21. Nothing of consequence changed since the last RC. Changelog v0.4.10: + Implemented the Sieve mime and foreverypart extensions (RFC 5703). These are fully implemented. The interaction with the editheader extension needs some work, but this should

Op 3/3/2018 om 9:35 AM schreef Stephan Bosch: > Op 3/3/2018 om 9:15 AM schreef Stephan Bosch: >> Op 3/3/2018 om 2:57 AM schreef Jan: >>> Hello! >>> >> We're looking into it. > Right, this is not reproducible in the test suite, but I can reproduce > it when I replicate your setup. I created a special test suite that reproduces the problem reliably. This

Hello Dovecot users, Here is a new Pigeonhole release that goes with the new Dovecot v2.2.34 release. This release is not strictly necessary, as previous versions should be usable as well. This release only contains bugfixes. Changelog v0.4.22: - Fixed filesystem path handling problem: sieve plugin could have assert-crashed with specific path lengths with: "Panic: file realpath.c: line

Hello Dovecot users, Here is a new Pigeonhole release that goes with the new Dovecot v2.2.34 release. This release is not strictly necessary, as previous versions should be usable as well. This release only contains bugfixes. Changelog v0.4.22: - Fixed filesystem path handling problem: sieve plugin could have assert-crashed with specific path lengths with: "Panic: file realpath.c: line

Hello Dovecot users, Now that Dovecot v2.1.0 is out there, I release Pigeonhole v0.3.0. The most significant new features are support for the Sieve editheader extension and the sieve-filter tool. I haven't received much feedback on these new features, which can either mean that they are mostly bug-free or that not many people have tried these, so these are still considered experimental.

Hello Dovecot users, Now that Dovecot v2.1.0 is out there, I release Pigeonhole v0.3.0. The most significant new features are support for the Sieve editheader extension and the sieve-filter tool. I haven't received much feedback on these new features, which can either mean that they are mostly bug-free or that not many people have tried these, so these are still considered experimental.

Op 3/3/2018 om 9:15 AM schreef Stephan Bosch: > Op 3/3/2018 om 2:57 AM schreef Jan: >> Hello! >> > We're looking into it. Right, this is not reproducible in the test suite, but I can reproduce it when I replicate your setup. Regards, Stephan. >> Dovecot 2.2.34 (874deae) >> Pigeonhole version 0.4.22 (22940fb7) >> >> After the update to pigeonhole

Op 3/3/2018 om 2:57 AM schreef Jan: > Hello! > We're looking into it. Regards, Stephan. > Dovecot 2.2.34 (874deae) > Pigeonhole version 0.4.22 (22940fb7) > > After the update to pigeonhole version 0.4.22 the following > configuration does not work. With version 0.4.21 it works. > > dovecot.conf (only sieve configuration) >

Hello Dovecot users, Here's the Pigeonhole release that goes with Dovecot v2.3.1. You will need this release for Dovecot v2.3.1, because the previous v0.5.0.1 release will not work. Apart from compatibility changes, it only contains bugfixes. Changelog v0.5.1: - Explicitly disallow UTF-8 in localpart in addresses parsed from Sieve script. - editheader extension: Corrected the stream

Hello Dovecot users, Here's the Pigeonhole release that goes with Dovecot v2.3.1. You will need this release for Dovecot v2.3.1, because the previous v0.5.0.1 release will not work. Apart from compatibility changes, it only contains bugfixes. Changelog v0.5.1: - Explicitly disallow UTF-8 in localpart in addresses parsed from Sieve script. - editheader extension: Corrected the stream