similar to: Pigeonhole Sieve Extprograms Plugin

trying to install Pigeonhole Sieve Extprograms how do I determine what is correct path for dovecot.config ? I did the hg clone http://hg.rename-it.nl/pigeonhole-0.3-sieve-extprograms/ './autogen.sh' seemed to have worked, but './configure' fails with # ./configure --with-dovecot=/usr/local/lib/dovecot ... checking whether to build static libraries... yes checking for

Hi, I upgraded to Dovecot 2.2.9 from Debian's wheezy-backports today (which should contain the "sieve_extprograms" plugin and thus also the vnd.dovecot.{pipe,filter,execute} capabilities. However when I add require "vnd.dovecot.filter"; to my sieve script via managesieve, the server reports error: require command: unknown Sieve capability: 'vnd.dovecot.filter'

Hello, I want to install Dovecot Pigeonhole and use the Extdata and Extprograms plugins. According to the dovecot documentation[1,2], those plugins need to be compiled. So two questions: * Are either of these plugins built into the Pigeonhole that is available in the CentOS 7 extras repo? * Is it possible to use these plugins with Pigeonhole installed from yum? Does the compilation

Hello! I've tried to use extprograms pipe feature but stuck with "Broken pipe" errors in mail log: May 17 15:18:57 backend1 dovecot: lmtp(20338, user at domain.tld): Debug: 3VMVFWFKllFyTwAArRg8UA: sieve: action pipe: running program: learn May 17 15:18:57 backend1 dovecot: script: Error: write(response) failed: Broken pipe May 17 15:18:57 backend1 dovecot: lmtp(20338, user at

The sieve-extprograms extension strips Return-Path headers before passing mail off to the external program. The patch to remove this behavious is trivial (and attached), but since it appears to be deliberate I felt I should investigate further. I believe this is basically a cut-and-paste error. The code to strip Return-Path has been there since the sieve-pipe plugin for Dovecot 1.x, and I believe

Hi, On a new install-from-source with Dovecot 2.2.16rc1, Piegeonhole 0.4.6 and a grab of the newest Extdata code, I confirmed basic Sieve functionality is working (made a simple sieve script with a test on message subject resulting in a fileinto action). But I cannot get Sieve to see Extdata or Extprograms. sievec reports "Warning: sieve: ignored unknown extension

Also, of course I have entered this in 90-plugins.conf plugin { seive_plugins = sieve_extdata sieve_extprograms sieve_extensions = +vnd.dovecot.filter +vnd.dovecot.extdata } And enabled sieve for lmtp (as I noted, I have tested that simple sieve scripting is working OK) protocol lmtp { mail_plugins = " sieve" } > On a new install-from-source with Dovecot 2.2.16rc1, >

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

I've tried to use sieve-filter for my inbox (~6000 messages). It failed after some work with this backtrace: sieve-filter(kas): Error: socketpair() failed: Too many open files sieve-filter(kas): Panic: file script-client-local.c: line 155 (script_client_local_disconnect): assertion failed: (pid >= 0) sieve-filter(kas): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x66a71)

Hello, I want to install Dovecot Pigeonhole and use the Extdata and Extprograms plugins on CentOS 7. I prefer to install software via yum, and a reasonably new version of Dovecot is available in the CentOS repo. But according to the dovecot documentation, these plugins need to be compiled, so I don't know if yum is out of the question? * Does anyone know if either of these plugins built

I need to connect to a database in a script called using Sieve extprograms plugin. When delivering mail, Sieve is running as the mail recipient user, which means any files, either the sieve script or the extprograms it invokes, are run under that user's permissions. What would be a way to hide the database credentials in a more restricted file? I can think of... * Store the credentials in

Op 4/21/2017 om 6:08 PM schreef Thomas: > Hello, > > I seem to be having some issues trying to setup a pipe to PHP scripts > using Sieve Extprograms. I am trying to allow each individual mailbox > to setup its own PHP pipe rules (in other words, each user should be > able to pipe incoming emails to a user defined PHP script). > > I have the following lines in my main Sieve

Hello, I was testing the extprograms plugin. I think I had it working in the past, but many things have changed since then, so no use trying to figure out where it broke - starting over again... Debug-enabled log give me: Apr 27 04:11:36 mail dovecot: lmtp(test at example.com): Debug: qOGyA0DePHVaOyHEM/SpMA: sieve: action execute: running program: test.sh Apr 27 04:11:36 mail dovecot: lmtp(test

On 04/23/2018 03:46 PM, Olaf Hopp wrote: > 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

Hi, I'm hoping to get some clarification of the differences between calling a script using the Sieve extprograms plugin execute method via direct execution or using the socket feature. Being naive, I see the socket option and think that way you tell Dovecot to spawn a daemon and I think that's going to be far superior in performance. But if that really was the difference, why would direct

I've been trying to pipe a message to an external script, and simplifying it as much as possible, I still get a broken pipe error. Can anyone point me in the right direction? X-Sieve: Pigeonhole Sieve 0.3.1 Using this script for debugging: -------------------------------- #!/bin/bash cat > /dev/null exit 0 server log contains: -------------------- Apr 21 19:45:18 generator dovecot:

On 4/30/2015 8:50 PM, E.B. wrote: >> I switched from running my extprograms execute script directly >> to running with dovecot socket. Log shows only this >> >> dovecot: lmtp(test at example.com): Debug: wdi0Tb5VPlGfPnEAM/SpMA: sieve: action execute: running program: test >> dovecot: lmtp(test at example.com): Debug: Namespace : Using permissions from

Hi, I'm just a beginner of extprograms plugin of sieve. When I execute a process via execute or pipe command, the process start with "root" privilege. Why? I believe the process must be executed with recipient privilege. Give me some checkpoints, or hints, please. My setup is as follows: Ubuntu 14.04.2 LTS 64bit + dovecot-core, dovecot-sieve plugin { sieve = ~/.dovecot.sieve

> I switched from running my extprograms execute script directly > to running with dovecot socket. Log shows only this > > dovecot: lmtp(test at example.com): Debug: wdi0Tb5VPlGfPnEAM/SpMA: sieve: action execute: running program: test > dovecot: lmtp(test at example.com): Debug: Namespace : Using permissions from /vmail/example.com/test: mode=0770 gid=default > dovecot: script:

Hello, I seem to be having some issues trying to setup a pipe to PHP scripts using Sieve Extprograms. I am trying to allow each individual mailbox to setup its own PHP pipe rules (in other words, each user should be able to pipe incoming emails to a user defined PHP script). I have the following lines in my main Sieve configuration file (/etc/dovecot/conf.d/90-sieve.conf):