Re: faild to rename deleted mailbox, or how conversation db sucks again

"Bron Gondwana" <[email protected]>
Newsgroups gmane.mail.imap.cyrus
Message-ID <[email protected]>
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 [email protected] [email protected]
. NO Invalid mailbox name
. SELECT [email protected]
* OK [CLOSED] Ok
* 2 EXISTS
[...]
. CREATE [email protected]
. OK [MAILBOXID (648d3c90-6c68-49cf-ac2b-49c2cfb9ee8b)] Completed
. COPY 1:* [email protected]
. OK [COPYUID 1551666806 1:2 1:2] Completed
. SELECT [email protected]
* 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
 [email protected]

----
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.