thr3ads.net - dovecot - sieve file backend: invalid option `active=~/.dovecot.sieve' [Feb 2017]

If this information is useful, please help other people find it:
Share via:

Ben

2017-Feb-13 17:15 UTC

sieve file backend: invalid option `active=~/.dovecot.sieve'

Hi,

I am seeing the followin error in my logs (doveconf -n at the bottom of 
this mail):

Feb 13 16:59:59 mxf dovecot: lmtp(45560, bp at example.com): Error: 
cs3NOQ7moVj4sQXXXXX: sieve: sieve file backend: invalid option 
`active=~/.dovecot.sieve'
Feb 13 16:59:59 mxf dovecot: lmtp(45560, bp at example.com): Error: 
cs3NOQ7moVj4sQXXXXX: sieve: failed to access user's Sieve script 
file:~/sieve;active=~/.dovecot.sieve (temporary failure)


Looking at http://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration, the 
syntax "sieve = file:~/sieve;active=~/.dovecot.sieve" in my config is 
correct ?

Is this a false error that is only appearing because this is a newly 
created user with no sieve file ?  If this is the case, how do I tell 
dovecot not to error out and allow the mail ?

Thanks !



# 2.2.10: /etc/dovecot/dovecot.conf
# OS: Linux 3.10.0-514.6.1.el7.x86_64 x86_64 CentOS Linux release 
7.3.1611 (Core)
auth_mechanisms = plain login
auth_verbose = yes
auth_verbose_passwords = sha1
first_valid_uid = 1000
mail_location = maildir:~/Maildir
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 environment 
mailbox date ihave enotify
mbox_write_locks = fcntl
namespace inbox {
   inbox = yes
   location    mailbox Drafts {
     special_use = \Drafts
   }
   mailbox Junk {
     special_use = \Junk
   }
   mailbox Sent {
     special_use = \Sent
   }
   mailbox "Sent Messages" {
     special_use = \Sent
   }
   mailbox Trash {
     special_use = \Trash
   }
   prefix }
passdb {
   driver = pam
}
passdb {
   driver = pam
}
passdb {
   args = scheme=CRYPT username_format=%u /etc/dovecot/users
   driver = passwd-file
}
plugin {
   sieve = file:~/sieve;active=~/.dovecot.sieve
   sieve_dir = ~/sieve
}
protocols = imap lmtp
service auth {
   unix_listener /var/spool/postfix/private/dovecot-auth {
     group = postfix
     mode = 0660
     user = postfix
   }
   unix_listener auth-userdb {
     group = its_virtmail
     mode = 0660
     user = its_virtmail
   }
}
service imap-login {
   process_min_avail = 3
}
service lmtp {
   process_min_avail = 5
   unix_listener /var/spool/postfix/private/dovecot-lmtp {
     group = postfix
     mode = 0600
     user = postfix
   }
   user = its_virtmail
}
service managesieve-login {
   inet_listener sieve {
     port = 4190
   }
   inet_listener sieves {
     address      port = 5190
     ssl = yes
   }
}
ssl = required
ssl_cert = <REMOVED
ssl_cipher_list = REMOVED
ssl_dh_parameters_length = 2048
ssl_key = </REMOVED
ssl_prefer_server_ciphers = yes
ssl_protocols = !SSlv2 !SSLv3
userdb {
   driver = passwd
}
userdb {
   args = username_format=%u /etc/dovecot/users
   driver = passwd-file
}
protocol lmtp {
   mail_plugins = sieve
   postmaster_address = me at example.com
}
protocol lda {
   deliver_log_format = msgid=%m: %$
   mail_plugins = sieve
   postmaster_address = postmaster
   quota_full_tempfail = yes
   rejection_reason = Your message to <%t> was automatically rejected:%n%r
}
protocol imap {
   imap_client_workarounds = delay-newmail
   mail_max_userip_connections = 20
}

Stephan Bosch

2017-Feb-14 14:44 UTC

head link

sieve file backend: invalid option `active=~/.dovecot.sieve'

Op 13-2-2017 om 18:15 schreef Ben:> Hi,
>
> I am seeing the followin error in my logs (doveconf -n at the bottom 
> of this mail):
>
> Feb 13 16:59:59 mxf dovecot: lmtp(45560, bp at example.com): Error: 
> cs3NOQ7moVj4sQXXXXX: sieve: sieve file backend: invalid option 
> `active=~/.dovecot.sieve'
> Feb 13 16:59:59 mxf dovecot: lmtp(45560, bp at example.com): Error: 
> cs3NOQ7moVj4sQXXXXX: sieve: failed to access user's Sieve script 
> file:~/sieve;active=~/.dovecot.sieve (temporary failure)
>
>
> Looking at http://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration, 
> the syntax "sieve = file:~/sieve;active=~/.dovecot.sieve" in my
config
> is correct ?
>
> Is this a false error that is only appearing because this is a newly 
> created user with no sieve file ?  If this is the case, how do I tell 
> dovecot not to error out and allow the mail ?
Don't specify the "sieve_dir" setting when you're using the
new location
syntax for the "sieve" setting. That setting is deprecated and causes 
the "sieve" setting to be interpreted differently for backwards 
compatibility.



>
> Thanks !
>
>
>
> # 2.2.10: /etc/dovecot/dovecot.conf
> # OS: Linux 3.10.0-514.6.1.el7.x86_64 x86_64 CentOS Linux release 
> 7.3.1611 (Core)
> auth_mechanisms = plain login
> auth_verbose = yes
> auth_verbose_passwords = sha1
> first_valid_uid = 1000
> mail_location = maildir:~/Maildir
> 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 environment 
> mailbox date ihave enotify
> mbox_write_locks = fcntl
> namespace inbox {
>   inbox = yes
>   location >   mailbox Drafts {
>     special_use = \Drafts
>   }
>   mailbox Junk {
>     special_use = \Junk
>   }
>   mailbox Sent {
>     special_use = \Sent
>   }
>   mailbox "Sent Messages" {
>     special_use = \Sent
>   }
>   mailbox Trash {
>     special_use = \Trash
>   }
>   prefix > }
> passdb {
>   driver = pam
> }
> passdb {
>   driver = pam
> }
> passdb {
>   args = scheme=CRYPT username_format=%u /etc/dovecot/users
>   driver = passwd-file
> }
> plugin {
>   sieve = file:~/sieve;active=~/.dovecot.sieve
>   sieve_dir = ~/sieve
> }
> protocols = imap lmtp
> service auth {
>   unix_listener /var/spool/postfix/private/dovecot-auth {
>     group = postfix
>     mode = 0660
>     user = postfix
>   }
>   unix_listener auth-userdb {
>     group = its_virtmail
>     mode = 0660
>     user = its_virtmail
>   }
> }
> service imap-login {
>   process_min_avail = 3
> }
> service lmtp {
>   process_min_avail = 5
>   unix_listener /var/spool/postfix/private/dovecot-lmtp {
>     group = postfix
>     mode = 0600
>     user = postfix
>   }
>   user = its_virtmail
> }
> service managesieve-login {
>   inet_listener sieve {
>     port = 4190
>   }
>   inet_listener sieves {
>     address >     port = 5190
>     ssl = yes
>   }
> }
> ssl = required
> ssl_cert = <REMOVED
> ssl_cipher_list = REMOVED
> ssl_dh_parameters_length = 2048
> ssl_key = </REMOVED
> ssl_prefer_server_ciphers = yes
> ssl_protocols = !SSlv2 !SSLv3
> userdb {
>   driver = passwd
> }
> userdb {
>   args = username_format=%u /etc/dovecot/users
>   driver = passwd-file
> }
> protocol lmtp {
>   mail_plugins = sieve
>   postmaster_address = me at example.com
> }
> protocol lda {
>   deliver_log_format = msgid=%m: %$
>   mail_plugins = sieve
>   postmaster_address = postmaster
>   quota_full_tempfail = yes
>   rejection_reason = Your message to <%t> was automatically
rejected:%n%r
> }
> protocol imap {
>   imap_client_workarounds = delay-newmail
>   mail_max_userip_connections = 20
> }

Ben

2017-Feb-14 17:46 UTC

head link

sieve file backend: invalid option `active=~/.dovecot.sieve'

On 14/02/2017 14:44, Stephan Bosch wrote:
> Don't specify the "sieve_dir" setting when you're using
the new location
> syntax for the "sieve" setting. That setting is deprecated and
causes
> the "sieve" setting to be interpreted differently for backwards
> compatibility.
>
Thanks for the pointer, although I don't think I am explicitly setting 
it (any changes I'm making to the default install I'm puting in
local.conf)

Guess I'll just have to track down which default file sieve_dir is being 
set in and comment it out...

Ben

2017-Feb-14 19:45 UTC

head link

sieve file backend: invalid option `active=~/.dovecot.sieve'

On 14/02/2017 14:44, Stephan Bosch wrote:>
>
> Op 13-2-2017 om 18:15 schreef Ben:
>> Hi,
>>
>> I am seeing the followin error in my logs (doveconf -n at the bottom
>> of this mail):
>>
>> Feb 13 16:59:59 mxf dovecot: lmtp(45560, bp at example.com): Error:
>> cs3NOQ7moVj4sQXXXXX: sieve: sieve file backend: invalid option
>> `active=~/.dovecot.sieve'
>> Feb 13 16:59:59 mxf dovecot: lmtp(45560, bp at example.com): Error:
>> cs3NOQ7moVj4sQXXXXX: sieve: failed to access user's Sieve script
>> file:~/sieve;active=~/.dovecot.sieve (temporary failure)
>>
>>
>> Looking at http://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration,
>> the syntax "sieve = file:~/sieve;active=~/.dovecot.sieve" in
my config
>> is correct ?
>>
>> Is this a false error that is only appearing because this is a newly
>> created user with no sieve file ?  If this is the case, how do I tell
>> dovecot not to error out and allow the mail ?
>
> Don't specify the "sieve_dir" setting when you're using
the new location
> syntax for the "sieve" setting. That setting is deprecated and
causes
> the "sieve" setting to be interpreted differently for backwards
> compatibility.
>
>
I've now commented out sieve_dir and its no longer appearing in doveconf 
-n, however the problem originally described still exists.

Any other ideas ?

Maybe Matching Threads

Search for more maybe matching threads

dovecot - Feb 2017 - sieve file backend: invalid option `active=~/.dovecot.sieve'

sieve file backend: invalid option `active=~/.dovecot.sieve'

sieve file backend: invalid option `active=~/.dovecot.sieve'

sieve file backend: invalid option `active=~/.dovecot.sieve'

sieve file backend: invalid option `active=~/.dovecot.sieve'

Maybe Matching Threads