search for: extprogram

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

...ieve-filter(kas): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x66a71) [0x7f020e717a71] -> /usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7f020e717ada] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f020e6d32ee] -> /usr/lib/dovecot/modules/sieve/lib90_sieve_extprograms_plugin.so(+0x4baf) [0x7f020dae0baf] -> /usr/lib/dovecot/modules/sieve/lib90_sieve_extprograms_plugin.so(+0x58ca) [0x7f020dae18ca] -> /usr/lib/dovecot/modules/sieve/lib90_sieve_extprograms_plugin.so(script_client_fail+0x2f) [0x7f020dae199f] -> /usr/lib/dovecot/modules/sieve/lib90_sieve_ext...

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

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=0...

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

Just discovered the Pigeonhole Sieve Extprograms plugin (https://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/Extprograms <https://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/Extprograms>)? I currently have Postfix configured to run a script to store all incoming messages into a Mysql DB and a batch job that retrieves the messages in the DB,...

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

> 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/examp...

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

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

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

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 'vnd.dovecot.filter' while configuring available extensions" and the same for vnd.dovecot.extdata. And of course for the user script, "error: require command: unknown Sieve capability `vnd.dovecot.filter'"...

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 configuration file > (/etc/dovecot/conf.d/90-sieve.conf)...

...required plugin /usr/local/lib/dovecot/lib90_sieve_plugin.so: > dlopen() failed: /usr/local/lib/dovecot/lib90_sieve_plugin.so: undefined symbol: > mail_deliver_ctx_get_log_var_expand_table Oh i guessing this requires the newest Dovecot source too (maybe you should put notice on the wiki that extprograms run-via-socket is broken until a new release?) After installed newest Dovecot and Sieve, I getting this: dovecot: lmtp(test at example.com): Debug: auth input: dovecot: lmtp(testl at example.com): Fatal: master: service(lmtp): child 7033 killed with signal 11 (core dumps disabled) With set mail...

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

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, > Piegeonhole 0.4....

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 execution even...

...l/lib/dovecot/lib90_sieve_plugin.so: > > dlopen() failed: /usr/local/lib/dovecot/lib90_sieve_plugin.so: undefined symbol: > > mail_deliver_ctx_get_log_var_expand_table > > Oh i guessing this requires the newest Dovecot source too (maybe you > should put notice on the wiki that extprograms run-via-socket is broken until > a new release?) > > After installed newest Dovecot and Sieve, I getting this: > > dovecot: lmtp(test at example.com): Debug: auth input: > dovecot: lmtp( > testl at example.com): Fatal: master: service(lmtp): child > 7033 killed with signa...

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

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: