similar to: Released Pigeonhole v0.4.0 for Dovecot v2.2.1.

Hello Dovecot users, Much time passed since I last released a new Pigeonhole, so quite a few unreleased fixes were pending until now. Development of new features is shifted to the upcoming Pigeonhole v0.4 for Dovecot v2.2. I intend to release v0.4.0 shortly after Dovecot v2.2.0. Changelog v0.3.4: * Changed error handling to be less of a nuisance for administrators. Strictly

Hello Dovecot users, Much time passed since I last released a new Pigeonhole, so quite a few unreleased fixes were pending until now. Development of new features is shifted to the upcoming Pigeonhole v0.4 for Dovecot v2.2. I intend to release v0.4.0 shortly after Dovecot v2.2.0. Changelog v0.3.4: * Changed error handling to be less of a nuisance for administrators. Strictly

Op 3/3/2018 om 6:29 PM schreef Stephan Bosch: > Op 3/3/2018 om 6:17 PM schreef Jan: >>>>> 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 occurs when Sieve

thanks you AKi for alway responding! >> Pigeonhole download page has links for extdata plugin up to v0.4 but >> nothing more and no link to the master repository >> >> https://pigeonhole.dovecot.org/download.html >> >> I want to use with dovecot 2.3.2rc1 but v0.4 won't compile with it. > > Seems to need v0.5 for it. What are you using it for? For a

Pigeonhole download page has links for extdata plugin up to v0.4 but nothing more and no link to the master repository https://pigeonhole.dovecot.org/download.html I want to use with dovecot 2.3.2rc1 but v0.4 won't compile with it. Thanks for helping ------------------------------------------------- ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's

Hello Dovecot users, Now that I am not preoccupied anymore, I quickly release a new version of Pigeonhole for Dovecot v2.2. This consists mainly of bug fixes. One new feature is that the Sieve plugin will try to pass temporary failures (e.g. from mail storage) back to LDA/LMTP as much as possible. However, this change turned out a little bigger than I would have liked, so experiment with it

Hello Dovecot users, Now that I am not preoccupied anymore, I quickly release a new version of Pigeonhole for Dovecot v2.2. This consists mainly of bug fixes. One new feature is that the Sieve plugin will try to pass temporary failures (e.g. from mail storage) back to LDA/LMTP as much as possible. However, this change turned out a little bigger than I would have liked, so experiment with it

>>> 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 occurs when Sieve editheader, Sieve redirect and LMTP are > combined. > > Now to fix it... Hello Stephan! Thank you for your quick reply

Hello Dovecot users, Here's the Pigeonhole RC that goes with the Dovecot RC. It includes a few small fixes and one new feature. Changelog v0.4.8.rc1: * LDA Sieve plugin: Dovecot changed the deliver_log_format setting to include %{delivery_time}. This prompted changes in Pigeonhole that make this release dependent on Dovecot v2.2.17. + Implemented magic to make sieve_default script

Hello Dovecot users, Here's the Pigeonhole RC that goes with the Dovecot RC. It includes a few small fixes and one new feature. Changelog v0.4.8.rc1: * LDA Sieve plugin: Dovecot changed the deliver_log_format setting to include %{delivery_time}. This prompted changes in Pigeonhole that make this release dependent on Dovecot v2.2.17. + Implemented magic to make sieve_default script

On 5/11/2015 6:24 PM, Brad Smith wrote: > On 05/10/15 18:42, Stephan Bosch wrote: >> Hello Dovecot users, >> >> Here's the Pigeonhole RC that goes with the Dovecot RC. It includes a >> few small fixes and one new feature. >> >> Changelog v0.4.8.rc1: >> >> * LDA Sieve plugin: Dovecot changed the deliver_log_format setting to >> include

On 5/11/2015 9:26 AM, Dominik Breu wrote: > Hello, > > did an test Install on my system get some nice SEGFAULT > wich backtrace here: https://dominikbreu.de/Stikked/view/8b6b7e5b > version is following: > aptitude versions dovecot-sieve i 2:2.2.17~rc1-1~auto+4 I cannot view that URL (some broken SSL error). You can just put the backtrace in the email itself. Regards,

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

Hello Dovecot users, Here's the definitive 0.4.16 release. There were no changes since the release candidate. The reported replication issues are still open, since we haven't been able to reproduce them so far. Changelog v0.4.16: * Part of the Sieve extprograms implementation was moved to Dovecot, which means that this release depends on Dovecot v2.2.26+. * ManageSieve: The PUTSCRIPT

Hello Dovecot users, Here's the definitive 0.4.16 release. There were no changes since the release candidate. The reported replication issues are still open, since we haven't been able to reproduce them so far. Changelog v0.4.16: * Part of the Sieve extprograms implementation was moved to Dovecot, which means that this release depends on Dovecot v2.2.26+. * ManageSieve: The PUTSCRIPT

Hello Dovecot users, It's been about 5 months since the last Pigeonhole release, so it is high time for a new one. However, the main reason to make a release now is the fact that Dovecot v2.2.15 has one change that causes problems with the previous release of Pigeonhole. Unlike recent earlier releases, this release has a few big new features. Most notably, I implemented a generic Sieve

Hello Dovecot users, It's been about 5 months since the last Pigeonhole release, so it is high time for a new one. However, the main reason to make a release now is the fact that Dovecot v2.2.15 has one change that causes problems with the previous release of Pigeonhole. Unlike recent earlier releases, this release has a few big new features. Most notably, I implemented a generic Sieve

Hi, I think the sieve_extprograms is mature enough for an initial release and that is why I've included the sieve_extprograms plugin into the main Pigeonhole v0.4 source tree. It is still a plugin, but is no longer provided as a separate package. This should make things easier. It will be released along with Pigeonhole v0.4.0. Regards, Stephan.

Hello Dovecot users, Now that Dovecot v2.2.13 is released, I can release a new Pigeonhole. Due to changes in Dovecot, this Pigeonhole release will not compile cleanly against older Dovecot releases. This release is mainly about bugfixes. One notable addition is that I have updated the "vnd.dovecot.duplicate" extension to the new IETF draft "duplicate" extension. Changelog