similar to: Sieve filter script EXECUTION FAILED

> On 30/10/2020 19:25 Bernd Petrovitsch <bernd at petrovitsch.priv.at> wrote: > > > On 30/10/2020 17:11, @lbutlr wrote: > [...] > > echo $1 | sed -e '|</head>|<style>* {color:white !important; background-color: black !important; } </style></head>|' > > What should the sed stuff do? > TTBOMK '|' is not known by sed ...

On 30 Oct 2020, at 12:34, @lbutlr <kremels at kreme.com> wrote: > I am not sure about the $1. I think filter just pipes the message (or part of the message. > > I will see what happens without the echo I suppose. > > Nope, still the same. > > 32: starting `:contains' match with `i;ascii-casemap' comparator: > 32: matching value `<!DOCTYPE

On 10/30/20 10:11 AM, @lbutlr wrote: > So, I have the sieve working up to the point that it calls the script, and the script is called (I get different errors if the script is not there, for example). > > filter action > execute program `darkmode.sh' > [[EXECUTION ABORTED]] > > There's no other error logged (for example, when I had sieve_filter_bin_dir

On 30 Oct 2020, at 11:25, Bernd Petrovitsch <bernd at petrovitsch.priv.at> wrote: > On 30/10/2020 17:11, @lbutlr wrote: > [...] >> echo $1 | sed -e '|</head>|<style>* {color:white !important; background-color: black !important; } </style></head>|' > > What should the sed stuff do? Changes </head> to <style>* {color:white

On 10/21/20 2:12 PM, @lbutlr wrote: > Do I HAVE to have a default.sieve, that's the only thing that I can think the has changed in that folder. RE: compile, fyi note @ https://wiki2.dovecot.org/Pigeonhole/Sieve/Usage#Manually_Compiling_Sieve_Scripts https://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration#Executing_Multiple_Scripts_Sequentially the conditions under which you need to

On 27/10/2020 15:30, @lbutlr wrote: > On 26 Oct 2020, at 21:04, Stephan Bosch <stephan at rename-it.nl> wrote: >> 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. >>>

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 10/21/20 1:10 PM, @lbutlr wrote: > I have trace logs enabled for user scripts, but I think only error get logged for upper level, and only along the lines of "could not compile <name of sieve>". verify that you can compile the scripts manually, even as root then double-check your perms on your sieve/ dir, making sure that the write perms are correct for your dovecot

Hello good people, I have dovecot- 2.3.7.2 (Ubuntu Ubuntu 20.04.1 LTS) running fine. However, I have a hitch with mail filtering. Using SOGo as the webmail UI, I created a filter rule which resulted into the rule below: require ["fileinto"]; if allof (address :contains "from" "odhiambo") { fileinto "INBOX/Odhiambo"; } However, the test mail I sent

Hello list I currently have an issue with an imapsieve script on my dovecot server CentOS Linux release 7.3.1611 (Core) Dovecot 2.2.26.0 (23d1de6) Pigeonhole 2.2.26.0 The goal is to "fire" an imapsieve script upon mailclient saves message to sent folder I setup the following in 90-plugin.conf: plugin { sieve_plugins = sieve_imapsieve sieve_extprograms sieve_extensions =

On Friday 17 August 2018 01:41:39 CEST Stephan Bosch wrote: > dovecot -n Hi, here it is (I don't know why I get the SSLv2 warning because it is disabled in ssl_protocols, any ideas about that too?). BTW, even when storing the message in a different folder with fileinto, the original message is still saved in the original mailbox. I also tried using `discard;` and makes no difference, I

You might consider adding "stop;" after the fileinto, otherwise a second match might process the message again, moving it elsewhere, etc. Tom. On 10/30/2020 5:47 AM, Odhiambo Washington wrote: > > Answering to myself, > > The issue was as a result of a config parameter for SOGo: > > Changed > NGImap4ConnectionStringSeparator = "/"; > > to >

Cribbing from the dovecot site I recently added the following lines to my dovecot.conf: managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext imapsieve

Hello, I'm trying to do a simple thing using imapsieve, I want messages to be marked as read when moved to certain folders (Trash, Archive, Spam). All the set up to run the imapsieve script works perfectly, but I'm having trouble to make changes effective. As the RFC says, IMAP messages are immutable, but it's not clear to me reading the specs if this applies to IMAP flags too, as one

Hi Stephan yes the imap_sieve plugin is added to the mail_plugins for imap. Thanks for the hint with mail_debug. After enabling it I can see that the program seems to be called, so filter should not be the problem. But the result is that the message appears unencrypted in my sent folder > Apr 6 08:20:26 mbox2 dovecot: imap(tobster at brain-force.ch): Debug: imapsieve: mailbox Sent: APPEND

> On 21 Oct 2020, at 15:45, PGNet Dev <pgnet.dev at gmail.com> wrote: > > On 10/21/20 2:12 PM, @lbutlr wrote: >> Do I HAVE to have a default.sieve, that's the only thing that I can think the has changed in that folder. > RE: compile, fyi note @ > > https://wiki2.dovecot.org/Pigeonhole/Sieve/Usage#Manually_Compiling_Sieve_Scripts >

I have the following in my default.sieve file: require "fileinto"; if header :contains "X-spam-flag" "YES" { require ["vnd.dovecot.pipe", "copy", "imapsieve", "environment", "variables", "imap4flags"]; setflag "\\Seen"; fileinto "Junk"; } This is largely unchanged, except that I

Dear dovecot developers, I have an issue with the Pigeonhole IMAPSieve Plugin and the order in which administrator scripts are executed. Although I cannot find anything about the order in which the scripts are executed, I would expect they are executed in the order they are defined: the one defined by imapsieve_mailbox1_* before the one defined by imapsieve_mailbox2_* in case both match. I

I am getting the following in my /var/log/dovecot: Error: sieve: Execution of script /usr/lib/dovecot/sieve/report-spam.sieve failed Error: plugin: failed to parse plugin (from @INC): Can't locate Mail/SpamAssassin/Plugin/Razor.pm in @INC (you may need to install the Mail::SpamAssassin::Plugin::Razor module) (@INC contains: /usr/local/lib/perl5/site_perl

Hello List, first thanks for previous hints, you helped me a lot. Unfortunately i have new problem with sieve and executing multiple scripts sequentially. This is current conf which is complete working : #CONF1 plugin { sieve = ~/sieve/.dovecot.sieve sieve_plugins = sieve_extprograms sieve_extensions = +vnd.dovecot.pipe +vnd.dovecot.filter +vnd.dovecot.execute +editheader