[MlMt] Database.noindex

[Benny Kjær Nielsen]

On 8 Feb 2017, at 15:21, Jasper Knockaert wrote:

> On 11 Oct 2016, at 10:31, Benny wrote:
>
>> It is correct that MailMate fails to detect this type of corrupt 
>> database. If you don't backup `Database.noindex` (which I actually 
>> agree is a good idea) then you might also want to leave out 
>> `Messages(.noindex)` since that's the other part of the database. The 
>> IMAP server is kind of the backup, but I can see why you might want a 
>> local backup too.
>
>> I guess MailMate should try to automatically detect this kind of 
>> state. I'll give that some thought since I would like to recommend 
>> leaving out `Database.noindex` from backups. Hmm, maybe even do that 
>> by default. A general problem is that Time Machine will some times 
>> back up files in an order which leaves the backed up database in a 
>> corrupted state.
>
> What is the current state of this issue? Would it make a difference if 
> I leave out only the `Headers` subfolder of `Database.noindex` when 
> backing up?

No, that's almost everything the folder contains. I have not yet 
improved the behavior of MailMate, but my advise still stands: It's fine 
to not backup `Database.noindex` as long as you consider the IMAP server 
to be the main backup of your emails. You'll still have a local backup 
of your emails in `Messages(.noindex)` if something goes wrong with the 
server.

-- 
Benny
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freron.com/pipermail/mailmate/attachments/20170210/d6a49c07/attachment-0001.html>