similar to: Pigeonhole sieve misfile

The sieve plugin for Thundirbird likes to rapidly compile work in progress sieve scripts to continually give feedback on any errors in the script. This can trigger segmentation faults in lib-sieve with certain pathologically incomplete sieve scripts. One example: #0 tag_comparator_validate (valdtr=0x7f291aa713a0, arg=0x7fff5c3cfa58, cmd=0x7f291aa69360) at sieve-comparators.c:143 143

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

Hi Stephan Bosch, any update on this? Regards, T.B. Am 08.05.2014 um 14:37 schrieb Stephan Bosch: > T.B. schreef op 7-5-2014 10:40: >> I think it would not be a problem to develop a solution to remotely >> trigger re-filtering for me, myself and I. But that is not the point >> here. Clients like the Thunderbird Sieve Extension >> (https://github.com/thsmi/sieve,

Hi, I wonder if someone could give me a little help bringing the sieve-extdata plugin up to date to be usable with latest Dovecot/pigeonhole Trying to use both together at present I get an error: ? managesieve: Fatal: Couldn't load required plugin /usr/lib/dovecot/sieve/lib90_sieve_extdata_plugin.so: dlopen() failed: /usr/lib/dovecot/sieve/lib90_sieve_extdata_plugin.so: undefined symbol:

Hi, We've recently upgraded from Dovecot 1.2.15 with Sieve 0.1.18 (Debian Squeeze) to Dovecot 2.1.8 and Pigeonhole 0.3.1. We provide a selection of global sieve scripts to make users' lives easier and one noticed that some of these have stopped working. I tracked it down to them having personal scripts with the same name. Using a really simple sieve script: require "include";

On 04/23/2018 03:22 PM, Stephan Bosch wrote: > > > Op 20-4-2018 om 14:01 schreef Olaf Hopp: >> Hi (Stephan?), >> is it a new feature of dovecot 2.3 /pigeonhole 0.5 that a sieve "redirect" changes the envelope sender of >> a redirected mail or simply a bug ? >> >> A sends mail to B, B redirects to C >> C sees B (not A!) as envelope sender.

Hello Dovecot users, It's been a while since the last Pigeonhole Sieve and ManageSieve releases. That is why this release includes quite a few changes. Most interestingly, the include extension is updated to match the most recent specification, the Sieve interpreter now includes plugin support and ManageSieve now has support for enforcing quota on the size of scripts, the number of

Hello Dovecot users, It's been a while since the last Pigeonhole Sieve and ManageSieve releases. That is why this release includes quite a few changes. Most interestingly, the include extension is updated to match the most recent specification, the Sieve interpreter now includes plugin support and ManageSieve now has support for enforcing quota on the size of scripts, the number of

I have built and installed Pigeonhole 0.4.4 with Dovecot 2.2.15. For users with no sieve at all I am getting an error on delivery. Delivery is from exim via lmtp. Syslog: Oct 28 11:03:50 mailhost dovecot: [ID 583609 mail.crit] lmtp(18915): Fatal: master: service(lmtp): child 18915 killed with signal 11 (core not dumped - set service lmtp { drop_priv_before_exec=yes }) There is no global

Self-explanatory, I hope (note the period on the end of the username); sieve/pigeonhole does not allow you to have senders which end with a period, which means that any UNIX users with such usernames who send mail have it rejected by sieve: # useradd testuser. # su - testuser. $ mail david at example.com -s 'testing' 123 . [testuser. at levi ~]$ logout # less /var/log/maillog Aug 22

Dear Stephan Bosch, dear Dovecot community, "sieve-filter" re-filtering of existing mails is already a great progress for everyone using sieve! But as far as I know this functionality is just accessible by the server administrator. In the meanwhile everyone knows the comfort of re-executing filter scripts on his own existing mailboxes - triggered by himself! This service is already

Hello Dovecot users, Due to personal matters I haven't had time to do anything in the last few weeks. Before that I provided some pre-releases and since nobody indicated problems with those, I release them definitively now. I hope the shit storm has blown over, so that I can dedicate more of my time towards Pigeonhole development. The Sieve release involves a large architectural change,

Hello Dovecot users, Due to personal matters I haven't had time to do anything in the last few weeks. Before that I provided some pre-releases and since nobody indicated problems with those, I release them definitively now. I hope the shit storm has blown over, so that I can dedicate more of my time towards Pigeonhole development. The Sieve release involves a large architectural change,

I am looking at porting and generalizing an old in-house patch that I'm using for the CMU Sieve plugin. It allows sieve script to test & lookup arguments from LDAP. Before getting too involved in this, I'd like to discuss my goals here in the hopes that someone else also thinks this would be useful. Many heads may make better design? Goal: ------ Allows scripts which are still

Hi all, Upgraded to Dovecot 2.1.16 and Pigeonhole 0.3.4 yesterday. We use lmtp and sieve. I've now started to see in the logs the following entries: >Warning: Jz6kNv8AY1FdfQAAVMeomg: sieve: encountered corrupt binary: re-compiling script [script path] The script then appears to run correctly and the message gets stored where ever it should be. This only appears to be happening for a few

I tried searching this list, but couldn't find anything related to inode limits except for linux quotas. I wanted to add sieve support for our users, so was attempting to get our email system to use dovecot's deliver lda to handle email, instead of postfix's virtual lda, using maildir mailstore. When I did this, I noticed that emails would get stuck in the queue if a user was

Hello Dovecot users, Pigeonhole development has slowed down significantly in the last few months due to the fact that I got swamped in work. The plan is now to move active development of Pigeonhole to Dovecot v2.0, meaning that this will be the last release for v1.2 that contains significant development changes and new features. However, if a certain new feature is simple enough and there is

Hello Dovecot users, Pigeonhole development has slowed down significantly in the last few months due to the fact that I got swamped in work. The plan is now to move active development of Pigeonhole to Dovecot v2.0, meaning that this will be the last release for v1.2 that contains significant development changes and new features. However, if a certain new feature is simple enough and there is

Hello, Here is a small script that I've been running to test a problem I've been seeing. Shouldn't this result in the mail being delivered to the inbox as a new message (ie. without the \Seen flag)? require "imap4flags"; addflag "\\Seen"; removeflag "\\Seen"; Every message gets delivered to the inbox as though it's already been

Hi all, Following the instructions noted at http://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/Pipe , I am trying to make use of the Pigeonhole sieve pipe plugin to execute an application with custom arguments via my test sieve script: require ["vnd.dovecot.pipe"]; if address :is "to" "test at example.com" { pipe :args [ "first-arg",