Re: SOLVED: IDLE not working for one account only

Ah, well done! Sorry I didn't get back to the attached, been a busy few days of conference here On Fri, Jun 8, 2018, at 01:06, Neil Price wrote: > cyrus.index needed to be updated to latest version. This affected > accounts upgraded from 2.2.4 > > reconstruct -rf -V max user/badaccount > >

SOLVED: IDLE not working for one account only

cyrus.index needed to be updated to latest version. This affected accounts upgraded from 2.2.4 reconstruct -rf -V max user/badaccount HIGHESTMODSEQ now looks more reasonable on telnet 143 login On 05/06/2018 09:17, Neil Price wrote: I'm using 2.5.10-3 (the one that comes with debian

Re: IDLE not working for one account only

What implications does HIGHESTMODSEQ have for idle? I now have 2 accounts with borken idle and I notice they both return HIGHESTMODEQ 1 on select inbox but the good accounts return a much larger number. On 05/06/2018 09:17, Neil Price wrote: I'm using 2.5.10-3 (the one that comes with