similar to: Strange permissions error - Failed to stat sieve storage path

Am 09.02.19 um 19:56 schrieb Aki Tuomi via dovecot: > I'll review the settings when we manage to upgrade to mailman3 Hello Aki, before updating to mailman3 consider an simpler update to latest mailman2. you're using 2.1.15, current mailman2 is 2.1.29 Your missing an /significant amount/ of DMARC fixes! and: more off-topic: while my messages *to* the dovecot list are sent using

Hi all, According to the docs at https://wiki.dovecot.org/Pigeonhole/Sieve, some extensions are not available by default. The docs tell me the sieve_plugins, sieve_extensions and/or sieve_global_extensions configs are involved, but I can find no authoritative documentation as to what the values should be. What values must I use to make ?vnd.dovecot.environment? available? Adding

On 10/02/2019 07:38, Ralph Seichter via dovecot wrote: > * Juri Haberland via dovecot: > >> Blindly enabling DMARC checks without thinking about the consequences >> for themselves should not be the problem of other well behaving >> participants. > > Can you judge if DMARC is enabled "blindly"? No, I thought not. Also, > the issue was not on the

On 24 Sep 2020, at 20:45, Sami Ketola <sami.ketola at dovecot.fi> wrote: > can you link your doveconf -n and the sieve script? The user?s detail are: [root at gatekeeper ~]# doveadm user minfrin at example.com field value uid vmail gid vmail home /home/vmail/minfrin at example.com/ mail maildir:~/mail mail_auto_reply_mode reply mail_auto_reply_text I am truly away... The sieve script

Noel Butler via dovecot skrev den 2019-02-10 01:51: > ... and surely he does not expect those with a million plus users sit > here and whitelist the million plus mailing lists that exist around > the world, heh, like thats going to happen :) fixing mailman will be the fail, solve it by letting opendkim and opendmarc not reject detected maillist will be solution, even if openarc comes

Am 30.05.2018 um 18:08 schrieb SATOH Fumiyasu: > Hi! > > On Thu, 31 May 2018 00:44:58 +0900, > A. Schulze wrote: >> When running multiple instances of dovecot on the same host (or running multiple docker container), >> it is hard to distinguish logs from different processes: the syslog entries are all prefixed with the same identifier "dovecot" >> It is

Looking at https://dovecot.org/mailman/options/dovecot I see that the option "Set Reply-To header to list?" does not accept any changes from me. I assume this might be related to DMARC related header mangling that was discussed at length before. While I do not want to open that particular can of worms again, I would like to force Reply-To: dovecot at dovecot.org for my own (!)

On 23 Sep 2020, at 14:29, Marc Roos <M.Roos at f1-outsourcing.eu> wrote: > You can do whatever you like, as long as the result is this 'text' file. > I have also bash file that modifies this file for users. You can make a > 5 min cron job that detects changes in ldap and then creates the sieve > rule. I've tried the cronjob approach before, and people didn?t like

Hi again everyone, So I've finally got sieve integration happening on my? REHL Postfix/Dovecot server, with private user scripts happily running when users create them. (we user SquirrelMail, so the avelsieve plugin runs the sieve integration). Now I'd like to utilise additional per-user scripts (probably via sieve_before), but I've not been able to get my additional scripts to

On Jan 1, 2015, at 8:10 AM, Stephan Bosch <stephan at rename-it.nl> wrote: > > Could you enable mail_debug? That should show why it is trying to > recompile the Sieve script. Well, that it does! And it's saying the script is "not up to date" and tries to recompile it. However, I'm not sure why it would say it's NOT up to date, it most certainly was

Hello, I'm running dovecot in a classical vmail.vmail setup with pigeonhole and LMTP. Permission worked well in the initial setup but currently (maybe after Fedora 22 update) I'm having the following permission issue: lmtp(root): Error: 7fPZFOL9wFXePQAABcdabc: sieve: binary open: failed to open: open(/etc/dovecot/sieve_after.svbin) failed: Permission denied (euid=9999(vmail)

Hello the list, I am trying to achieve filter processing using sieve, but i am not sure I can do what I want. I want to let the user decide to use my filtering script (sieve_after) or not.According to the documentation, i am trying to stop processing in user sieve script, but processing continue. I am using dovecot 2.2 (CentOS). My sieve configuration is:plugin { ? sieve =

It has been running flawlessly for quite some time until the update. Global scripts were compiled: /usr/local/etc/dovecot/sieve # ls 10-move-spam.sieve 10-move-spam.svbin However, I ran sievec again and tried saving a modified script and got the same: shiofuki dovecot: lda(gessel at blackrosetech.com): Error: sieve: binary save: failed to create temporary file:

I have some global scripts that were running nicely. Then I opened one in an editor and (probably, but not 100% sure) mindlessly saved the file, even though I hadn't made any changes. Shortly after, Sieve errors started showing in the log: Error: 4k5JA74R/1TlIwABG/SpMA: sieve: binary save: failed to create temporary file: open(/usr/local/var/dovecot/sieve/script2.svbin.example.com.4139.)

my local.conf has: # 90-sieve.conf plugin { sieve_before = /home/sieve/globalfilter.sieve } and cat /home/sieve/globalfilter.sieve require ["fileinto","mailbox"]; if anyof ( header :contains "X-Spam-Flag" "YES", header :contains "subject" "***SPAM***" ) { fileinto :create "Spam"; } There IS a

On 05.08.2015 13:06, Steffen Kaiser wrote: > On Tue, 4 Aug 2015, Gerhard Wiesinger wrote: > >> >> I'm running dovecot in a classical vmail.vmail setup with pigeonhole >> and LMTP. Permission worked well in the initial setup but currently >> (maybe after Fedora 22 update) I'm having the following permission >> issue: >> >> lmtp(root):

> > I have some global scripts that were running nicely. > > > > Then I opened one in an editor and (probably, but not 100% sure) > > mindlessly saved the file, even though I hadn't made any changes. > > > > Shortly after, Sieve errors started showing in the log: > > > > Error: 4k5JA74R/1TlIwABG/SpMA: sieve: binary save: failed to create

On 10/02/2019 12:49, Benny Pedersen via dovecot wrote: > fixing mailman will be the fail, solve it by letting opendkim and opendmarc not reject detected maillist will be solution, A general broad mailing list whitelist will be problematic, do work it needs to look for specific list type hidden headers, spammers and nasties will incorporate those headers into their trash that impersonates

Hi, After upgrading from dovecot 1.1 to dovecot 1.2.2 and the new sieve implementation (0.1.9), I'm having some strange problems. I'm including some general purpose scripts into my user script from sieve_global_dir. After some tests it seems that ths scripts get executed at random: sometimes the mail gets stored in the correct dir, and sometimes it goes to inbox. This also happens while

On Jan 1, 2015, at 9:50 AM, Stephan Bosch <stephan at rename-it.nl> wrote: > > Hmm. This smells like a bug. I notice that your modification times of > the .sieve and .svbin file are exactly the same (that is somewhat > unusual). I'm looking at a potential bug that would explain your problem. > > To confirm, could you try running sievec again, so that the .svbin is