lazy_expunge doesn't work since upgrade 2.2.30 to 2.2.32

Harald Leithner leithner at itronic.at
Mon Sep 4 14:52:03 EEST 2017


Ok thx for the info, anyway there are no mail copied to #EXPUNGED/ 
namespace.



Am 04.09.2017 um 13:40 schrieb Aki Tuomi:
> Hi!
> 
> On 04.09.2017 14:38, Harald Leithner wrote:
>> Hi,
>>
>> it seams that the lazy_expunge plugin doesn't work for me after the
>> upgrade...
>>
>> 2.2.32 cry's about
>>
>> plugin { lazy_expunge_only_last_instance=no } is most likely handled
>> as 'yes' - remove the setting completely to disable it. If this is
>> intentional, add quotes around the value:
>> lazy_expunge_only_last_instance="no"
>>
>> I changed it to lazy_expunge_only_last_instance="no" and tried to
>> remove it but doesn't change the problem.
>>
> 
> This is a warning that you should just ignore. This warning will go away
> in v2.3 once we are properly parsing the values.
> 
> Aki
> 

-- 
Harald Leithner

ITronic
Wiedner Hauptstraße 120/5.1, 1050 Wien, Austria
Tel: +43-1-545 0 604
Mobil: +43-699-123 78 4 78
Mail: leithner at itronic.at | itronic.at


More information about the dovecot mailing list