Re: Cyrus 2.5.12 - 'reconstruct' - doesn't? - resolved.

2019-03-13 Thread Karl Pielorz
Ok, I've finally twigged / resolved this... It looks like the actual directory in question was indeed orphaned from mailboxes.db - due to an issue with names and spaces. If you miss-spell the name of the mailbox - 'reconstruct' / 'mbexamine' et'al just return without doing anything. This

Re: Cyrus 2.5.12 - 'reconstruct' - doesn't?

2019-03-13 Thread Karl Pielorz
--On 13 March 2019 at 13:03:03 -0400 Dave McMurtrie wrote: Are the files on disk owned by user 'cyrus' or are they owned by root? All owned by cyrus:cyrus - if I pick "any other mailbox" (which looks identical disk wise) - reconstruct runs, and outputs the name of the mailbox it just

Re: Cyrus 2.5.12 - 'reconstruct' - doesn't?

2019-03-13 Thread Giles Malet
but the full 'path' to the specific mailbox. Hopefully you're not giving a filesystem path. Reconstruct takes the mailbox "name", not a path on disk. So something like "user.fred" or whatever. Maybe that's why it's not finding anything. I often use the -rfGR flags, with maybe O. Someone

Re: Cyrus 2.5.12 - 'reconstruct' - doesn't?

2019-03-13 Thread Sebastian Hagedorn
Hi, I have a Cyrus 2.5.12 server running under FreeBSD. The other day I found thousands of files in an old mailbox. The client can't see any of them - so I thought "Ok, I'll reconstruct the mailbox" Reconstruct runs, and returns instantly - but the client still can't see the files. As a last

Cyrus 2.5.12 - 'reconstruct' - doesn't?

2019-03-13 Thread Karl Pielorz
Hi, I have a Cyrus 2.5.12 server running under FreeBSD. The other day I found thousands of files in an old mailbox. The client can't see any of them - so I thought "Ok, I'll reconstruct the mailbox" Reconstruct runs, and returns instantly - but the client still can't see the files. As