> On 6 Aug 2019, at 21.08, Mark Moseley via dovecot wrote:
>
>>
>> I've bisected this down to this commit:
>>
>> git diff
>> 7620195ceeea805137cbd1bae104e385eee474a9..97473a513feb2bbd763051869c8b7b83e24b37fa
>>
>> Prior to this commit, anything updating the quota would do the right thing
On Tue, Apr 9, 2019 at 9:52 PM Aki Tuomi wrote:
>
> On 10 April 2019 05:00 Mark Moseley via dovecot
> wrote:
>
>
> On Wed, Apr 3, 2019 at 9:37 PM Mark Moseley < moseleym...@gmail.com>
> wrote:
>
>
> On Wed, Mar 20, 2019 at 2:13 PM Mark Moseley < moseleym...@gmail.com>
> wrote:
>
> Just hoping
On 10 April 2019 05:00 Mark Moseley via dovecot wrote:
On Wed, Apr 3, 2019 at 9:37 PM Mark Moseley <
moseleym...@gmail.com> wrote:
On Wed, Apr 3, 2019 at 9:37 PM Mark Moseley wrote:
>
> On Wed, Mar 20, 2019 at 2:13 PM Mark Moseley
> wrote:
>
>> Just hoping to get some dev eyes on this. I'm incredibly reluctant to
>> throw the word 'bug' around
>> (since 99 times out of 100, it's not -- it's almost always the config),
>>
On Wed, Mar 20, 2019 at 2:13 PM Mark Moseley wrote:
> Just hoping to get some dev eyes on this. I'm incredibly reluctant to
> throw the word 'bug' around
> (since 99 times out of 100, it's not -- it's almost always the config),
> but I can't think of any way
> that this could be a config issue,
Just hoping to get some dev eyes on this. I'm incredibly reluctant to throw
the word 'bug' around
(since 99 times out of 100, it's not -- it's almost always the config), but
I can't think of any way
that this could be a config issue, esp when the pre-2.2.34 version works as
expected.
I noticed
