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

2017-02-25 Thread Stephan Bosch
Op 2/14/2017 om 8:45 PM schreef Ben: > > > 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, b...@example.com)

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

2017-02-14 Thread Ben
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, b...@example.com): Error: cs3NOQ7moVj4sQX: sieve: sieve file backend: invalid op

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

2017-02-14 Thread Ben
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, alt

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

2017-02-14 Thread Stephan Bosch
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, b...@example.com): Error: cs3NOQ7moVj4sQX: sieve: sieve file backend: invalid option `active=~/.dovecot.sieve' Feb 13 16: