| 1 |
Why does reconstruct -m not work? |
| 2 |
--------------------------------- |
| 3 |
|
| 4 |
From the :cyrusman:`reconstruct(8)` man page:: |
| 5 |
|
| 6 |
−m NOTE: CURRENTLY UNAVAILABLE |
| 7 |
Rebuild the mailboxes file. Use whatever data in the existing |
| 8 |
mailboxes file it can scavenge, then scans all partitions listed |
| 9 |
in the imapd.conf(5) file for additional mailboxes. |
| 10 |
|
| 11 |
Reconstruct is currently unable to rebuild the mailboxes db, and |
| 12 |
comments on the mailing list indicate this ability will not be added; at |
| 13 |
least, not any time soon. |
| 14 |
|
| 15 |
The solution here is to make sure that you back up your mailboxes db, |
| 16 |
preferably including a plain-text copy of it. Please see Backups for |
| 17 |
more information. |
| 18 |
|
| 19 |
If you do find yourself with a corrupted mailboxes.db, there are a few |
| 20 |
things you can try. The first is to see if ``db_recover`` can recover |
| 21 |
your database. If that doesnt' work, there should be backups in |
| 22 |
``$CONFIGDIRECTORY/db.backup1`` and ``$CONFIGDIRECTORY/db.backup2`` that |
| 23 |
may be OK. |
| 24 |
|
| 25 |
If you're using Simon Matter's RPMs, plain-text copies of the mailboxes |
| 26 |
database should be being generated and saved in |
| 27 |
``/var/lib/imap/backup``. Try rebuilding the db from one of those using |
| 28 |
:cyrusman:`ctl_mboxlist(8)`. Alternately, try asking the mailing list |
| 29 |
for help. |
| 30 |
|