On 6/4/20 7:45 AM, Brian J. Murrell wrote:
On Wed, 2020-06-03 at 19:35 -0400, Ken Murchison wrote:Brian, Trying running 'unexpunge -l' on the mailbox in question.This avenue has already been explored earlier in this thread: https://lists.andrew.cmu.edu/pipermail/info-cyrus/2020-May/041258.html To save the effort of re-reading the message: # sudo -u cyrus bash -c "/usr/lib/cyrus-imapd/unexpunge -l user.brian" [nothing returned] So this is looking more like a "bad accounting" problem than something typically operational. But how to reconcile it? It seems to me that a process of comparing what's in the index to what's on disk to account for the orphans is needed. I just don't know what that process is. I probably just don't know the toolset well enough to know which tools to apply and how. mbexamine seems a candidate but I'm not sure how to interpret it's output to this task. Or maybe there other/better tools? Any suggestions?
Have you looked in some of the orphaned messages to see if they are emails you have deleted before? My thought would be to move these orphaned messages out of /var/spool/imap/b/user/brian . Then delete and expunge a few messages using your mail client and see if they are also removed from /var/spool/imap/b/user/brian
Cheers, b. ---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
<<attachment: boutilpj.vcf>>
---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
