similar to: Released Pigeonhole v0.3.1 for Dovecot v2.1.6

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

Hello Dovecot users, The last few releases had an annoying bug that made the Sieve editheader and imap4flags ineffective when multiple scripts were executed sequentially (sieve_before/sieve_after). That is why I am making a new release. Unlike the previous release, this release also adds a new feature: support for the Sieve extracttext extension. Changelog v0.4.12: + Implemented the Sieve

Hello Dovecot users, The last few releases had an annoying bug that made the Sieve editheader and imap4flags ineffective when multiple scripts were executed sequentially (sieve_before/sieve_after). That is why I am making a new release. Unlike the previous release, this release also adds a new feature: support for the Sieve extracttext extension. Changelog v0.4.12: + Implemented the Sieve

Hi, Yesterday, I committed two important and rather big changes to the Pigeonhole repository. The first creates a generic interface for implementing Sieve script storages. It was already possible to some extent to read Sieve scripts from other sources than the local filesystem, such as Dovecot dict, but that was still pretty limited, as it was not possible to do this with

Hello Dovecot users, Apart from unfinished development of the date extension, this is a set of bug-fix releases. A few portability issues were found, a few stupidities were fixed and the ManageSieve proxy now also works with TLS. Most notably, the include extension had an issue regarding the expansion of $HOME in the personal include path. I've built a project site at:

Hello Dovecot users, Apart from unfinished development of the date extension, this is a set of bug-fix releases. A few portability issues were found, a few stupidities were fixed and the ManageSieve proxy now also works with TLS. Most notably, the include extension had an issue regarding the expansion of $HOME in the personal include path. I've built a project site at:

Michael Kliewe wrote: > Hi Per, > > On 25.08.2015 11:40, Per Jessen wrote: >> sieve and managesieve are both working fine, have been for years. Now >> I want to add a sieve_after script: >> >> /etc/dovecot/conf.d/90-sieve.conf : >> >> plugin { >> sieve = ~/.dovecot.sieve >> sieve_dir = ~/sieve >> sieve_before = >>

Hello List, first thanks for previous hints, you helped me a lot. Unfortunately i have new problem with sieve and executing multiple scripts sequentially. This is current conf which is complete working : #CONF1 plugin { sieve = ~/sieve/.dovecot.sieve sieve_plugins = sieve_extprograms sieve_extensions = +vnd.dovecot.pipe +vnd.dovecot.filter +vnd.dovecot.execute +editheader

Hi, A few new Pigeonhole features that enthusiasts can experiment with: - Recently, I implemented support for the "imapsieve" extension in Sieve and its IMAP counterpart (https://tools.ietf.org/html/rfc6785). This is now in the Pigeonhole master branch. This allows running Sieve scripts at IMAP activity, rather than at delivery. There are also facilities for the familiar

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 https://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration#Executing_Multiple_Scripts_Sequentially the conditions under which you need to

On June 7, 2018 6:47:54 PM GMT+02:00, Will Foster <sadsfae at funcamp.net> wrote: >Hi Folks, > >I am having a problem configuring imapsieve via dovecot-pidgeonhole on >CentOS7. > >After following the docs here: > >https://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/IMAPSieve > >I get: > >dovecot[22026]: managesieve: Fatal: Plugin 'sieve_imapsieve'

> 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 >

Am 12.02.2015 um 15:47 schrieb Martin ?tefany: > Hello, > > I've ran into problem with Dovecot and dsync replication. Everything > works perfectly, including replication of sieve scripts, except fact > that if user activates the 'managesieve' ruleset (I'm using currently > Roundcubemail) on "mail1" host, it wouldn't be activated on

sieve and managesieve are both working fine, have been for years. Now I want to add a sieve_after script: /etc/dovecot/conf.d/90-sieve.conf : plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_before = sieve_after = ~/sieve/personal.sieve sieve_subaddress_sep = + } I have compiled ~/sieve/personal.sieve to ~/sieve/personal.svbin, but it doesn't seem to be read. Any

Hi Folks, I am having a problem configuring imapsieve via dovecot-pidgeonhole on CentOS7. After following the docs here: https://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/IMAPSieve I get: dovecot[22026]: managesieve: Fatal: Plugin 'sieve_imapsieve' not found from directory /usr/lib64/dovecot/sieve dovecot[22026]: doveconf: Error: managesieve-login: dump-capability process returned 89

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