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

[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, 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 ?