similar to: Pigeonhole v0.5.13 released

Server: Ubuntu 10.04 LTS 32bit There seems to be an incompatibility when compiling Pigeonhole against Dovecot v2.2.13.rc1. # make check with Pigeonhole throws up the following error message: <snip> Test case: ./tests/extensions/editheader/addheader.svtest: 1: Test 'Addheader - first' SUCCEEDED 2: Test 'Addheader - last' SUCCEEDED 3: Test 'Addheader - framed'

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

Hello! 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) --------------------------------------------------------------- managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope

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

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

In order to simplify auto-response suppression and other filtering, I want to synthesise an Auto-Submitted header on notification mails that should have them but do not. In a sieve file I add the following: if anyof ( header :contains ["From","Sender"] ?info at example.com" ) { if header :contains "Subject" [" just joined "," just left

Hi all, I want to add a custom header to incoming emails from a particular sender. This is what my user Sieve script looks like: require ?editheader?; if address :is "From? ?special-sender at example.com? { addheader ?X-My-Custom-Header? ?Header Value"; } I have enabled the editheader extension in my Dovecot configuration: plugin { ? sieve_extensions = +editheader }

Hello. We have currently set dovecot.sieve to insert the text "[SPAM]" at the beginning of an e-mail's subject when it's X-Spam-Score is above 80%. After we set our system as stated the following errors occur: 1) When an e-mail's subject contains control characters like [Ctrl+V|^V], dovecot.sieve terminates with an error and an e-mail is not able to be sent. When a MIME

Hi Stephan, Sorry for the delay - this was on version 2.3.4.1 (f79e8e7e4). Relevant bits from the config: # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.0-9-amd64 x86_64 Debian 10.4 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric

Hi Everybody, I'm using dovecot 2.1.14 from http://xi.rename-it.nl/debian/ with debian squeeze stable. In general, sieve works fine for me, but "addheader :last ..." from the editheader extension causes a crash when it processes a message. I was able to narrow this down a bit: It only happens if "addheader :last" is the first editheader command executed in a script.

Hi there, on my mail server (postfix, dovecot 2.2.27 in Debian 9) I have an automatic forwarding (with sender_bcc_maps in Postfix) for all the emails sent in smtp from the same server, that are then put in the Sent folder with a sieve rule. In this way, however, when a user sends an e-mail to himself, both copies end up in the Sent folder and it's not good. To resolve, I tried using

> On 13/05/2020 21:10 Peter Folta <mail at peterfolta.net> wrote: > > > Hi all, > > I want to add a custom header to incoming emails from a particular sender. This is what my user Sieve script looks like: > > require ?editheader?; > > if address :is "From? ?special-sender at example.com? { > addheader ?X-My-Custom-Header? ?Header Value";

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

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