RE: read state not propagated

2020-12-30 Thread aki.tuomi
> On 30/12/2020 12:19 Marc Roos wrote: > > > >Can you somehow confirm that the "read" status is not available > >for the 2nd user in dovecot indexes? Maybe use mail_log plugin to > > see when the flag changes occur? > > Is it possible to configure this logging for only one users, maybe via

RE: read state not propagated

2020-12-30 Thread Marc Roos
>Can you somehow confirm that the "read" status is not available >for the 2nd user in dovecot indexes? Maybe use mail_log plugin to > see when the flag changes occur? Is it possible to configure this logging for only one users, maybe via this special-userdb? This would be sufficient not?

RE: read state not propagated

2020-12-29 Thread aki.tuomi
> On 29/12/2020 13:27 Marc Roos wrote: > > > > > > > >> > >> I have migrated the inbox namespace from mbox to mdbox by doing a > >> doveadm backup to the new server. Both servers are having CentOS7 + > >> dovecot-2.2.36-6.el7_8.1.x86_64, both servers have identical > >> configurations (n

RE: read state not propagated

2020-12-29 Thread Marc Roos
> > >> >> I have migrated the inbox namespace from mbox to mdbox by doing a >> doveadm backup to the new server. Both servers are having CentOS7 + >> dovecot-2.2.36-6.el7_8.1.x86_64, both servers have identical >> configurations (new server has some different vsz_limits and stats >> enabled) >

Re: read state not propagated

2020-12-29 Thread Aki Tuomi
> On 29/12/2020 13:22 Marc Roos wrote: > > > I have migrated the inbox namespace from mbox to mdbox by doing a > doveadm backup to the new server. Both servers are having CentOS7 + > dovecot-2.2.36-6.el7_8.1.x86_64, both servers have identical > configurations (new server has some differen