=?UTF-8?Q?Re:_faild_to_rename_deleted_mailbox, __or_how__conversation_db_?= sucks again

Bron Gondwana brong at fastmailteam.com
Sun Mar 3 21:35:58 EST 2019


This isn't quite renaming the folder, and you'll lose per-user seen state, but you can create a new folder and, using the admin login, copy the messages:

. RENAME DELETED.user.brongfoo.xx.5C7C8E80 at fastmailtest.com user.brongfoo.xx at fastmailtest.com
. NO Invalid mailbox name
. SELECT DELETED.user.brongfoo.xx.5C7C8E80 at fastmailtest.com
* OK [CLOSED] Ok
* 2 EXISTS
[...]
. CREATE user.brongfoo.xx at fastmailtest.com
. OK [MAILBOXID (648d3c90-6c68-49cf-ac2b-49c2cfb9ee8b)] Completed
. COPY 1:* user.brongfoo.xx at fastmailtest.com
. OK [COPYUID 1551666806 1:2 1:2] Completed
. SELECT user.brongfoo.xx at fastmailtest.com
* OK [CLOSED] Ok
* 2 EXISTS
* 2 RECENT


On Mon, Mar 4, 2019, at 13:25, ellie timoney wrote:
> On Sat, Mar 2, 2019, at 2:54 AM, Michael Menge wrote: 
> > Is there an other way than disabling
> > - conversation db,
> > - restoring the folder,
> > - enabeling conversation db again (so that squat files are used for 
> > header searches),
> > - rebuilding conversation db for all users (because there will be some 
> > new mails between
> > disabling and re-enabling conversation db).
> 
> If you can arrange for your MX to hold the incoming mail during the period where conversations is disabled, that would at least avoid needing to rebuild conversationsdb for everyone again afterwards? You might be able to do this by temporarily disabling the lmtpd service, but I'm not sure (it would depend on how your MX handles that)
> 
> Cheers,
> 
> ellie
> ----
> 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
> 

--
 Bron Gondwana, CEO, FastMail Pty Ltd
 brong at fastmailteam.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.andrew.cmu.edu/pipermail/info-cyrus/attachments/20190303/658b9027/attachment.html>


More information about the Info-cyrus mailing list