Freron MailMate

Comments and changes to this ticket

• You flagged this item as spam.
  

  Muhamad Martoprawiro May 22nd, 2013 @ 10:00 PM

  I am trying to do the following steps:

  Type these in the terminal:
  cd ~/Library/Application Support/
  printf MailMate MailMate/.rebuild.tmp

  Then, I start again MailMate. The message "MailMate quit unexpectedly." disappeared, and a window with title "Messages import" is shown instead. It is still importing messages now. I hope the problem solved.

• You flagged this item as spam.
  

  Muhamad Martoprawiro May 22nd, 2013 @ 10:07 PM

  The steps above make the MailMate created a new directory "MailMate" in the folder ~/Library/Application Support/MailMate/
  Please tell me if I made mistakes.

• You flagged this item as spam.
  

  Muhamad Martoprawiro May 22nd, 2013 @ 11:04 PM

  Something strange happened. The number of messages imported is still increasing (around 32000), but the size reported in the "Messages import" window was changes from around 4 GB to 32 MB now.

• You flagged this item as spam.
  

  Muhamad Martoprawiro May 23rd, 2013 @ 03:29 AM

  Then, after several hours, the message "Mailmate quit unexpectedly." reappeared. When I click "Reopen", the "Messages import" restarted from 0 message. It seems that MailMate ignored the thousands of emails that have been indexed in the previous import.

• You flagged this item as spam.
  

  Muhamad Martoprawiro May 23rd, 2013 @ 06:08 AM

  After the 2nd "Messages import" window, the import process finished, and I just click OK. After that, voila, my MailMate is working again. Great!
  Just one question: after all the processes, the new folder ~/Library/Application Support/MailMate/MailMate/ was disappeared. Is the folder only temporary folder for rebuilding the databases?

• 

  benny May 23rd, 2013 @ 06:27 AM

  • State changed from “new” to “closed”

  Sorry about the late response. I'm glad you managed to resolve the issue.

  The folder you implicitly created in the rebuild process disappears if all of the messages in the old database can be mapped to the new database. It is a good sign that it is empty, but the problem you had was also not related to database corruption.

  Your problem is a bug in MailMate which apparently causes a crash on startup. It was related to a message scheduled to be sent. I'm not 100% sure, but I think this bug might have been fixed in more recent test releases of MailMate although in that case I was not aware that it could trigger the crash-on-startup behavior you have seen.

  The size count in the import window is a bug. I'll look into that.

  The second import window starts from 0, but it actually continues the previous import. It should be quite safe to crash/stop MailMate during the import process, but the message count is misleading.

  Let me know if it happens again and hopefully I'll be online at the time to help out before you do the rebuilding.

• 

  benny May 23rd, 2013 @ 09:20 AM

  Fixed the import size count.