Freron MailMate

Comments and changes to this ticket

• 

  benny June 14th, 2011 @ 07:06 AM

  • Assigned user set to “benny”
  • State changed from “new” to “accepted”

  Update: Before following any of the instructions below then see the latest comment on this issue.

  Did you by any chance notice if two instances of MailMate were running after the update? This would be very bad for the database indexes and I have had a report of this happening once before.

  I'm afraid the best thing you can do is start over. You can either do it a by dragging the following folder to the trash:

  ~/Library/Application Support/MailMate
  

  Or if you want to keep account, mailbox, and signature settings, you can trash these folders instead:

  ~/Library/Application Support/MailMate/Database.noindex
  ~/Library/Application Support/MailMate/Messages
  ~/Library/Application Support/MailMate/Attachments
  

  I'm very sorry about the inconvenience! I'll look into possible problems with relaunching MailMate after an update and I'll keep this ticket open to track any progress.

  For everybody reading this ticket, I'm interested in any reports on multiple instances of MailMate running and any special circumstances you may think could be relevant. If it happens then it is important to close both instances as quickly as possible. And even better to force quit them.

• You flagged this item as spam.
  

  Justin Bauer June 14th, 2011 @ 01:43 PM

  Benny,

  Thanks for the quick response, just wanted to update that I have since restarted my machine and tried to launch mailmate with the same issue, so it's not a double instance issue. I also am not able to find the MailMate folder in the Application Support folder, but I'm assuming it's because its hidden. Going to try reinstalling and see if that helps.

  Keep up the good work team.

• 

  benny June 14th, 2011 @ 02:33 PM

  The problem is likely going to be persistent based on the look of the
  crash log (database corruption). Running with two instances of MailMate
  after the update (due to some bug in the update system) would be a very
  likely cause for this database corruption. Therefore I am very
  interested in knowing if you think that happened after updating?

  The folder is not hidden. You should look here:

  /Users/(your username)/Library/Application Support/MailMate
  

  The use of ~ in my previous description is shorthand for /Users/(your username)/ if that is why you couldn't find it.

  Reinstalling won't help.

• 

  benny November 14th, 2011 @ 11:51 AM

  • State changed from “accepted” to “fixcommitted”

  The next version of MailMate includes code to automatically detect problems like the one described in this ticket. The user is then offered some options to rebuild the database including an option to base the rebuild on already downloaded messages if possible. This also includes the information saved about usage of signatures.

• 

  benny December 22nd, 2011 @ 01:10 PM

  • State changed from “fixcommitted” to “fixreleased”

  [bulk edit]