similar to: Released Pigeonhole v0.4.12.rc1 for Dovecot v2.2.21

Hello Dovecot users, Here is the final v0.4.12 release of Pigeonhole for Dovecot v2.2.21. Nothing changed since the RC. Changelog v0.4.12: + Implemented the Sieve extracttext extension (RFC 5703; Section 7). It is now possible to extract body text from a message into a variable. * Increased ABI version due to changes in the Sieve interpreter's object definitions. - multiscript: Fixed

Hello Dovecot users, Here is the final v0.4.12 release of Pigeonhole for Dovecot v2.2.21. Nothing changed since the RC. Changelog v0.4.12: + Implemented the Sieve extracttext extension (RFC 5703; Section 7). It is now possible to extract body text from a message into a variable. * Increased ABI version due to changes in the Sieve interpreter's object definitions. - multiscript: Fixed

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

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, Several bugs were found in the course of the last few months, but no new features were created. So, this will be strictly a bug-fixing release. The previous Pigeonhole release should still work with the new Dovecot release, which means you are not required to upgrade. However, my advice would be to upgrade once this release candidate matures into a final release, since at

Hello Dovecot users, Several bugs were found in the course of the last few months, but no new features were created. So, this will be strictly a bug-fixing release. The previous Pigeonhole release should still work with the new Dovecot release, which means you are not required to upgrade. However, my advice would be to upgrade once this release candidate matures into a final release, since at

We are pleased to release pigeonhole 0.5.13. You can download it from locations below: https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.13.tar.gz https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.13.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Aki Tuomi Open-Xchange oy --- -

We are pleased to release pigeonhole 0.5.13. You can download it from locations below: https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.13.tar.gz https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.13.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Aki Tuomi Open-Xchange oy --- -

Hello Dovecot users, Here's the definitive 0.4.17 release. There were no changes since the release candidate. Changelog v0.4.17: - LDA Sieve plugin: Fixed handling of an early explicit keep during multiscript execution. Action side-effects and the message snapshot would be lost at the final stage where the implicit keep is evaluated. This could result in the IMAP flags assigned to the

Hello Dovecot users, Here's the definitive 0.4.17 release. There were no changes since the release candidate. Changelog v0.4.17: - LDA Sieve plugin: Fixed handling of an early explicit keep during multiscript execution. Action side-effects and the message snapshot would be lost at the final stage where the implicit keep is evaluated. This could result in the IMAP flags assigned to the

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, First, a happy new year to you all! :) In the last few weeks I got quite a few bug reports. I also found a few things myself. Some of the bugs are quite annoying, so a new release is necessary. First, I release RC1. If all is well, I'll release the definitive Pigeonhole v0.4.11 within the next few days. Changelog v0.4.11: - Sieve mime extension: Fixed the header :mime

Hello Dovecot users, First, a happy new year to you all! :) In the last few weeks I got quite a few bug reports. I also found a few things myself. Some of the bugs are quite annoying, so a new release is necessary. First, I release RC1. If all is well, I'll release the definitive Pigeonhole v0.4.11 within the next few days. Changelog v0.4.11: - Sieve mime extension: Fixed the header :mime

Hello Dovecot users, It's been a few months since the last Pigeonhole release. The main reason is that I've introduced a few big new features. Although the new features themselves probably haven't seen much testing so far, I'm now pretty confident that existing configurations are not broken by these changes. The biggest change is the addition of dict support for Sieve script

Hello Dovecot users, It's been a few months since the last Pigeonhole release. The main reason is that I've introduced a few big new features. Although the new features themselves probably haven't seen much testing so far, I'm now pretty confident that existing configurations are not broken by these changes. The biggest change is the addition of dict support for Sieve script

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

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

> On 21 Oct 2020, at 15:45, PGNet Dev <pgnet.dev at gmail.com> wrote: > > On 10/21/20 2:12 PM, @lbutlr wrote: >> Do I HAVE to have a default.sieve, that's the only thing that I can think the has changed in that folder. > RE: compile, fyi note @ > > https://wiki2.dovecot.org/Pigeonhole/Sieve/Usage#Manually_Compiling_Sieve_Scripts >