Harald Leithner
2017-Sep-04 11:52 UTC
lazy_expunge doesn't work since upgrade 2.2.30 to 2.2.32
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
Harald Leithner
2017-Sep-06 09:01 UTC
lazy_expunge doesn't work since upgrade 2.2.30 to 2.2.32
Any idea why this doesn't setup work anymore in 2.2.32? thx Harald Am 04.09.2017 um 13:52 schrieb Harald Leithner:> 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
Mark Moseley
2017-Sep-15 19:25 UTC
lazy_expunge doesn't work since upgrade 2.2.30 to 2.2.32
On Wed, Sep 6, 2017 at 2:01 AM, Harald Leithner <leithner at itronic.at> wrote:> Any idea why this doesn't setup work anymore in 2.2.32? > > thx > > Harald > >I just ran into the same thing myself. For me, when I added this to the "location" in the expunged namespace, it started working again: ...:LISTINDEX=expunged.list.index I can't tell you why exactly (presumably has something to do with "mailbox_list_index = yes"). Perhaps the devs might know?