similar to: sieve_extprograms plugin calling bash script

Hello, i use sieve extension sieve_extprograms to send incoming mail to some script. For security reasons it is needed that script-paths etc. are registered in dovecot.conf This is my current dovecot.conf plugin { sieve = ~/.dovecot.sieve sieve_plugins = sieve_extprograms sieve_extensions = +vnd.dovecot.pipe +vnd.dovecot.filter +vnd.dovecot.execute sieve_pipe_bin_dir =

Hello List, i have a problem when using sieve-plugin sieve_extprograms. I use dovecot 2.2.18 and bundled pigeonhole 0.4.6 (Ubuntu 14.04.3 LTS) i have enabled sieve_extprograms and vnd.dovecot.filter to send mail to user-defined script and get changed content back. My script previously was used with procmail and is working fine. Using same script with vnd.dovecot.filter leads to odd behavior. I

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

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: Fatal: recv(MSG_PEEK) failed:

Op 9/21/2015 om 2:34 PM schreef Hajo Locke: > Hello, > > i use sieve extension sieve_extprograms to send incoming mail to some > script. > For security reasons it is needed that script-paths etc. are > registered in dovecot.conf > This is my current dovecot.conf > > plugin { > sieve = ~/.dovecot.sieve > sieve_plugins = sieve_extprograms > sieve_extensions

Hi, > Can you enable mail_log plugin, try again, and send updated logs? > Aki Sure, but logs contain same info. 1. When I move a message from Inbox to Spam it matches both rules and sieve executing both scripts in sequence: Debug: Spam: Mailbox opened because: SELECT Debug: imapsieve: mailbox Spam: APPEND event Debug: sieve: Pigeonhole version 0.4.21 (92477967) initializing Debug: sieve:

I have an email where I need to edit the body. I know this is generally a bad idea, but in this case I need to do it. The email comes in automatically every week or two, and so I thought that SIEVE would be the way to go. if header :contains "from" "theaddress at tehdomain" { if body :raw :contains "A string" { # Magic happens here } } It looks

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

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

I currently have a basic script to process some mails, it runs from cron every 10 minutes, basically, sieve copies some mails to subfolder on mail arrival, script fetches mails if any from this subfolder then processes these mail, get maybe 1 or 2 or often none but cron runs the script every 10 minutes, most times not needed as nothing is retrieved it's pretty crude - but works getmail

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

Hello, I'm experiencing some strange problem with imapsieve mailbox rules matching. I have Ubuntu Server 18.04.1 LTS with Postfix 3.3.0, Dovecot 2.2.33.2 and Rspamd 1.7.9. The problem occurs with Microsoft Outlook 2016 mail client. When moving with Outlook, APPEND event is logged instead of MOVE. However, when moving with another client, MOVE event is logged. So without APPEND event in

On 23/10/2020 13:22, @lbutlr wrote: > On 22 Oct 2020, at 19:09, Stephan Bosch <stephan at rename-it.nl> wrote: >> You need to include the extprograms plugin: > I have, and vnf.dovecot.pipe doesn't give the error. > > sieve_plugins = sieve_imapsieve sieve_extprograms > > ?\_(?)_/? > > I am not using filter now though, so I haven't try to track down

On 20/10/2020 23:37, @lbutlr wrote: > On 20 Oct 2020, at 13:46, @lbutlr <kremels at kreme.com> wrote: >> It looks like what I need to do is enable and use vnd.dovecot.filter > error: require command: unknown Sieve capability `vnd.dovecot.filter'. > > Is this not available to a user? I guess I can put the in global, but ick. You need to include the extprograms plugin:

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

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

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

Is is possible (I?m sure it is, so how) to strip multipart messages that are HTML and text of the HTML portion and leave the bare text message without also stripping other parts (like images or attached files). Or also to take messages that are only HTML and strip the HTML and replace it with a plain text version? I used to do this a long time ago with procmail and lynx, but it was never

On 24 Sep 2020, at 22:07, Sami Ketola <sami.ketola at dovecot.fi> wrote: > I think this should be > > require ["environment"]; > > instead. I eventually stumbled on a syntax that worked. Putting all of this in one place: - You need to turn on the sieve_extprograms plugin: sieve_plugins = sieve_extprograms - Then you need to enable vnd.dovecot.environment:

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