similar to: Released Pigeonhole v0.4.19.rc1 for Dovecot v2.2.31.rc1.

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

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

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

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, Here's the Pigeonhole RC that goes with the Dovecot RC. Changelog v0.4.9.rc1: * Properly implemented checking of ABI version for Sieve interpreter plugins, much like Dovecot itself does for plugins. This will prevent plugin ABI mismatches. + Implemented a vnd.dovecot.environment extension. This builds upon the standard environment extension and adds a few more

Hello Dovecot users, Pigeonhole v0.4.12 still compiles against Dovecot v2.2.22.rc1, but only with warnings. That is the primary reason for this new release. However, there are also a few significant changes as listed below. When no significant problems are reported, a definitive release will follow closely after Dovecot v2.2.22 is released. Changelog v0.4.13: * redirect action: Added the

Hello Dovecot users, Here's the Pigeonhole RC that goes with the Dovecot RC. Changelog v0.4.9.rc1: * Properly implemented checking of ABI version for Sieve interpreter plugins, much like Dovecot itself does for plugins. This will prevent plugin ABI mismatches. + Implemented a vnd.dovecot.environment extension. This builds upon the standard environment extension and adds a few more

Hello Dovecot users, Pigeonhole v0.4.12 still compiles against Dovecot v2.2.22.rc1, but only with warnings. That is the primary reason for this new release. However, there are also a few significant changes as listed below. When no significant problems are reported, a definitive release will follow closely after Dovecot v2.2.22 is released. Changelog v0.4.13: * redirect action: Added the

Hello Dovecot users, Here's a release candidate for a quick Pigeonhole release, mostly containing fixes. One fix addresses a problem caused by the previous release. Changelog v0.4.20: + Made the retention period for redirect duplicate identifiers configurable. For accounts that perform many redirects, the lda-dupes database could grow to impractical sizes. Changed the default

Hello Dovecot users, Here is the Pigeonhole hole release candidate that goes with the Dovecot release candidate. Nothing really special going on, just a few changes and fixes that accumulated over the last few months. Changelog v0.4.21: * redirect action: Always set the X-Sieve-Redirected-From header to sieve_user_email if configured. Before, it would use the envelope recipient instead if

Hello Dovecot users, Here's a first release candidate for the upcoming Pigeonhole release for Dovecot v2.2.36. It only contains bugfixes for now. There's one experimental plugin still in the pipeline. Changelog v0.4.24: - Fix assert panics triggered by empty messages that are being forwarded using redirect or vnd.dovecot.report. This does not likely normally occur, but this is

Hello Dovecot users, Here is the Pigeonhole release candidate that goes with the Dovecot v2.3.2 release candidate. Much like version 0.4.24 for Dovecot v2.2, this release consists mostly of fixes that accumulated over the last few months. Beyond that, this release contains the new IMAP FILTER=SIEVE capability, which was also released earlier with 2.2.24 (with a few additional fixes).

Hello Dovecot users, Here is the Pigeonhole release candidate that goes with the Dovecot v2.3.3 release candidate. It consists only of bugfixes. Changelog v0.5.3: - Fix assertion panic occurring when managesieve service fails to open INBOX while saving a Sieve script. This was caused by a lack of cleanup after failure. - Fix specific messages causing an assert panic with actions that

Hello Dovecot users, Here's a release candidate for a quick Pigeonhole release, mostly containing fixes. One fix addresses a problem caused by the previous release. Changelog v0.4.20: + Made the retention period for redirect duplicate identifiers configurable. For accounts that perform many redirects, the lda-dupes database could grow to impractical sizes. Changed the default

Hello Dovecot users, Here is the Pigeonhole hole release candidate that goes with the Dovecot release candidate. Nothing really special going on, just a few changes and fixes that accumulated over the last few months. Changelog v0.4.21: * redirect action: Always set the X-Sieve-Redirected-From header to sieve_user_email if configured. Before, it would use the envelope recipient instead if

Hello Dovecot users, Here's a first release candidate for the upcoming Pigeonhole release for Dovecot v2.2.36. It only contains bugfixes for now. There's one experimental plugin still in the pipeline. Changelog v0.4.24: - Fix assert panics triggered by empty messages that are being forwarded using redirect or vnd.dovecot.report. This does not likely normally occur, but this is

Hello Dovecot users, Here is the Pigeonhole release candidate that goes with the Dovecot v2.3.2 release candidate. Much like version 0.4.24 for Dovecot v2.2, this release consists mostly of fixes that accumulated over the last few months. Beyond that, this release contains the new IMAP FILTER=SIEVE capability, which was also released earlier with 2.2.24 (with a few additional fixes).

Hello Dovecot users, Here is the Pigeonhole release candidate that goes with the Dovecot v2.3.3 release candidate. It consists only of bugfixes. Changelog v0.5.3: - Fix assertion panic occurring when managesieve service fails to open INBOX while saving a Sieve script. This was caused by a lack of cleanup after failure. - Fix specific messages causing an assert panic with actions that

Hello Dovecot users, This upcoming release is all about bug fixes, of which only one is really important. It affects the new imapsieve plugin. Changelog v0.4.15: - imapsieve plugin: For any mail transaction, the mailbox was opened a second time, even if no mailbox rule matched. This was unintentional, useless and caused problems when the imapsieve plugin was used with other plugins like