1) 

With 2.4.1, when a non-root user runs sievec on their own sieve scripts
it fails to run due to permission denied on the dovecot certificate key
(which is only readable by root).

Specifically:

sievec active.sieve 
doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-
ssl.conf line 10: cert_file: open(/etc/.../fullchain.pem) failed:
Permission denied

What is recommended way to deal with this?

2)

Separate question: Might this explain why users sieve scripts are not
running?  I assume not as there are no 'sieve' items reported by lmtp
in the logs.

Config has:

protocol lmtp {
  postmaster_address = postmaster@<domain>.com
  mail_plugins {
    sieve = yes
  }
  hostname = imap.<domain>.com
}



sieve_script before {
    driver = file
    path = /etc/dovecot/sieve/global
    active_path = remove_dup.sieve
}

sieve_script personal {
    driver = file
    path = ~/sieve
    active_path = ~/.dovecot.sieve
}

sieve_script after {
    driver = file
    path = /etc/dovecot/sieve
    active_path = default.sieve
}


thanks.

-- 
Gene

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
dovecot mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to