Re: Corrupted mailboxes.db
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
To
: Info <info@xxxxxxxxxxxxxxxxxx>
Subject
: Re: Corrupted mailboxes.db
From
: phil@xxxxxxxx
Date
: Mon, 3 Jul 2023 18:36:46 -0400
In-reply-to
: <
16874879080.9Cf4Ea59.7508@composer.cyrus.topicbox.com
>
Reply-to
: Info <info@xxxxxxxxxxxxxxxxxx>
Topicbox-delivery-id
: 2:cyrus:02f406ce-0e39-11eb-9ac9-159c9134e1fa:5a2fd7b8-0eef-11eb-b1da-c982292d11b0:M3365a29059d40649db374e17:1:BVJ8gdN92NMM4yfbviMofJe7ZAt2hXJiWj1EUmdjU7E
Topicbox-message-uuid
: 17ba70c6-19f2-11ee-af40-137d2a2d11b0
Topicbox-policy-reasoning
: allow: sender is a member
In case anyone else runs into this, I've now got a repo with a script and docs on how to recover your email:
https://github.com/jaymzh/recover-cyrus
Hope that helps.
Follow-Ups
:
Re: Corrupted mailboxes.db
From:
gijs . hillenius
References
:
Corrupted mailboxes.db
From:
phil
Re: Corrupted mailboxes.db
From:
phil
Prev by Date:
Re: Authentication and authorization with OpenLDAP; hashed passwords
Next by Date:
After upgrade to 3.6.1, getting header CRC mismatches
Previous by thread:
Re: Corrupted mailboxes.db
Next by thread:
Re: Corrupted mailboxes.db
Index(es):
Date
Thread
[Index of Archives]
[Cyrus SASL]
[Squirrel Mail]
[Asterisk PBX]
[Video For Linux]
[Photo]
[Yosemite News]
[gtk]
[KDE]
[Gimp on Windows]
[Steve's Art]
