Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

Local messages can't be found, crash on trying

#47

[newest version 1902]

I'm not sure it's a proper bug or due to my deleting the messages a month ago manually (which I did as far as I remember. Mh, still a bug I guess). In the latter case the database can/could be corrupted by manually deleting messages.

I also sent a crash report on that some minutes ago.
Just found out how to crash can be reproduced.

So, I get "Local messages no longer supported" every launch.
'Copy messages' does not work: 'Failed', 'no such file' [ok, if the files are non-existent] The crash happens when I click 'delete the files'.
Ignoring by 'remind me later' works okay.

Just tell me what I should delete or check, and I'll do it. Obviously, I prefer some solution which does not involve downloading all messages again.

Reported by Thomas Hanke · February 17th, 2011 @ 11:52 AM

State: new
Milestone: none
Assigned to: benny benny

Activity

  1. benny
    benny
    • State changed from new to accepted

    I'll do what I can to help you via private email.

    For the record: MailMate does not like when messages are removed behind
    its back. It could be more forgiving in this regard, but it is a tricky
    problem. When MailMate receives a message it keeps a copy of it and puts
    all the headers in a separate custom “database” for fast searching.
    When the message is deleted, it needs the message again in order to know
    which headers need to be deleted. The only alternative is to scan
    through (and thus loading) all headers in the database. This would be
    very inefficient, but this is of course what MailMate could offer to do
    when this situation arises. But the problem could arise in other cases
    than when deleting a message, e.g., if trying to view a message which
    has been deleted on disk (leads to a crash as well).

    Maybe the best solution would be for MailMate to do the slow scanning of
    the database (after warning about the problem) and then create a fake
    message on disk which can then be deleted, viewed, or whatever triggered
    the request for the message. I'll put that on the todo.

    I'll keep this ticket open until the above has been implemented.

    [state:accepted]

    February 17th, 2011 @ 02:16 PM

  2. Thomas Hanke
    Thomas Hanke

    Hi Benny,

    sorry: for my problem at hand, Time Machine's the solution, of course.

    I just took a guess when I deleted the folder 'Local' (only two days off), copied it back, and voilà!
    Now there's only 1 message left in the 'Local/imported' sub-folder. I guess I'm save to delete it.

    I understand the database issue - well, well enough, at least.
    It's just never occurred to me since I haven't got any feedback on missing files in the last 4 weeks. I guess that means that MM never checks for the presence of 'Local' files. Anyway, they're gone now.

    I don't use it - TM - very often, so it took some time to remember it. +1 point for separate small email files, of course.

    Kind of related personal insight: I learned, well realized (again?), today that .noindex can be used to exclude Spotlight.

    Thomas

    February 17th, 2011 @ 08:17 PM

  3. benny
    benny
    • State changed from accepted to closed

    (Cleaning up old tickets.)

    Situations like these should now trigger MailMate to ask to rebuild the database. (It is still not allowed to remove messages behind MailMate's back, but I think that is a fair requirement.)

    October 9th, 2013 @ 07:02 AM

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.