similar to: Sieve tempoary script folder

I tried to set a quota setting. I installed dovecot with newest version, patched it and started it. dovecot -n: # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.3 ext4 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s ssl_listen: 143 ssl_cipher_list: ALL:!LOW:!SSLv2 disable_plaintext_auth: no login_dir: /var/run/dovecot/login

Hi all, Wishing you and your families a Happy New Year 2019. I am currently struggling with an odd sieve issue after upgrading dovecot from 2.2.32 to the latest 2.3.4 version. OS is Ubuntu 18.04. For one of our users I have a sieve rule in place which should copy (keep + fileinto) incoming mails from the INBOX to a public namespace folder. Unfortunately this does not work anymore. In the sieve

Well I changed the line to ????????? if header :contains "X-Spam-Status: YES" { Then I got: # sievec spam_to_junk.sieve spam_to_junk: line 3: error: the header test requires 2 positional argument(s), but 1 is/are specified. spam_to_junk: error: validation failed. sievec(root): Fatal: failed to compile sieve script 'spam_to_junk.sieve' Should it be: ????????? if header

On 11 Jun 2020, at 05:24, Voytek Eymont <voytek at sbt.net.au> wrote: > > looking at wiki2, 'Pigeonhole Sieve Extprograms Plugin', is this what > would allow to execute my script on new mail arrival? Yes. This is what I have to auto=mark spam when it is moved too the Spam folder and to mark messages as seen when they are archived: plugin { sieve_plugins =

On 16/04/2020 23:38, Marc Roos wrote: > It is a 'special use' folder, so it only appears to exist in mail > clients. > > # spam folders merging > mailbox Junk { > special_use = \Junk > auto = create > } > mailbox Spam { > special_use = \Junk > auto = no > } > mailbox "Junk E-mail" { > special_use

On 16/04/2020 23:19, Marc Roos wrote: > I do not have the log file anymore from the home dir. It just complains > that the folder Spam does not exist. > > dovecot: lmtp(xxxx): oG8YI6enmF7FIAAAI7dPvA: sieve: Execution of script > /xxxx/.dovecot.sieve failed, but implicit keep was successful (user > logfile /xxx/.dovecot.sieve.log may reveal additional details) So, does that

Hi all, ok, so I've implemented an after sieve script with the following line in the plugins area : sieve_after = /home/mailboxes/sieve/to_spam_folder.sieve It seems to work ok on some accounts, but then I'm getting the following error in the deliver error log for many accounts : Error: sieve: script /home/mailboxes/sieve/to_spam_folder.sieve failed with unsuccessful implicit keep

I do not have the log file anymore from the home dir. It just complains that the folder Spam does not exist. dovecot: lmtp(xxxx): oG8YI6enmF7FIAAAI7dPvA: sieve: Execution of script /xxxx/.dovecot.sieve failed, but implicit keep was successful (user logfile /xxx/.dovecot.sieve.log may reveal additional details) -----Original Message----- From: Stephan Bosch [mailto:stephan at rename-it.nl]

Hmmm, confusing, clients should then display the mailbox name redirected by the server. If a user in a front end just sees the 'Junk E-mail', that is the name he is going to be using in his mailbox rules. If he does not know that this is actually the Junk folder on the server, he will make an incorrect message rule. So I guess you have to correct this server side, before storing

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

Am 2019-08-06 15:04, schrieb Nagy Tibor via dovecot: > I have an *Ubuntu 16.04* mail server with > postfix/spamassassin/*dovecot-2.2.2**2* with virtual mailboxes in > maildir format. The whole process is working excellently since a year. > Spams are marked with "*****SPAM*****" in subject and with > "X-Spam-Flag: YES" in email header. > > I tried now to

Hi guys, is there any way to configure Dovecot to process the default sieve script and, after that, a user specific script? I have a default script to sort spam into a spam folder but if a user specific script is present, the default script is ignored. sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_global_path = /usr/local/etc/dovecot/sieve/default.sieve Regards Patrick

And the Sieve script: ------- start sieve script --------- require ["vnd.dovecot.execute", "fileinto", "mailbox", "vnd.dovecot.debug"]; debug_log "about to execute"; if not execute :pipe "foofilter" { debug_log "if condition fulfilled"; fileinto :create "test-spam"; debug_log "about to stop"; stop;

It is a 'special use' folder, so it only appears to exist in mail clients. # spam folders merging mailbox Junk { special_use = \Junk auto = create } mailbox Spam { special_use = \Junk auto = no } mailbox "Junk E-mail" { special_use = \Junk auto = no } On 16/04/2020 23:19, Marc Roos wrote: > I do not have the log file anymore from the

I cutover to a new server which uses Postfix & Dovecot to handle emails as opposed to Postfix & Courier in the old server. Below is the contents of my global sieve script and dovecot config info. The dovecot-deliver.log does show that the email is being delivered to INBOX.spam but it ends up in the INBOX instead. If I put the exact same rule in the user script, the emails are delivered

This is what I use.? Notice the comma: require "fileinto"; if header :contains "X-Spam-Status" "Yes," { ? fileinto "SystemFolders.SuspectedSpam"; ? stop; } Bill On 12/14/2017 1:02 PM, Richard wrote: > >> Date: Thursday, December 14, 2017 09:47:44 -0800 >> From: Gao <gao at pztop.com> >> >> I use a sieve filter to move

Hello, In my current setup, I have a spam filter upstream that adds a specific header - X-Spam-Level on every incoming mail. Based on this level, the mail will be moved to the user spam folder using sieve by doing "fileinto :create 'spam';" Unfortunately, some legitimate email may end up in this spam folder, so I have kind of a whitelist that performs an explicit keep over

Am 14.12.2017 um 18:47 schrieb Gao: > I use a sieve filter to move spam email to user's Junk folder: > # cat spam_to_junk.sieve > require "fileinto"; > ? if exists "X-Spam-Status" { > ????????? if header :contains "X-Spam-Status" "YES" { > ????????? fileinto "Junk"; > ????????? stop; > ????????? } else { > ?????

Did you look at the server logs as suggested by the logfile? Aki > On 13 November 2018 at 18:52 Lionel Elie Mamane <lionel at mamane.lu> wrote: > > > And the Sieve script: > > ------- start sieve script --------- > require ["vnd.dovecot.execute", "fileinto", "mailbox", "vnd.dovecot.debug"]; > > debug_log "about to

In my installation "deliver" die if global sieve script turn on. Is there anything I have missed? Thanks.. Flex 2.5.33 Dovecot 1.0.rc29 postfix 2.3.8 In maillog: Apr 3 13:29:58 minigrass postfix/pipe[24691]: CA194121BC5: to=<xxx at yyy.com>, relay=dovecot, delay=0.24, delays=0.14/0.01/0/0.09 , dsn=5.3.0, status=bounced (Command died with status 2: