#741 new
Mike Forret

Mailmate will not run

Reported by Mike Forret | May 1st, 2014 @ 04:13 AM

Mailmate v1.7.2
Macbook Pro running 10.6.8
Have been using Mailmate for several months but today I am unable to run Mailmate at all. On trying to start the program, after a few seconds I get the standard Apple 'Mailmate quit unexpectedly' error panel and am unable to open the program at all.
Tried restarting the Mac and a new download of the program but still unable to start the program.
Not sure if this is relevant but have experienced accounts becoming unavailable and having to restart Mailmate to make them available again. Unable to provide any other feedback on current problem as cannot run the program.

Comments and changes to this ticket

  • benny

    benny May 1st, 2014 @ 06:56 AM

    Sorry to hear that. First try updating to the latest test version: http://updates.mailmate-app.com/archives/MailMate_r4199.tbz

    If it still crashes then launch it from the Terminal like this:

    /Applications/MailMate.app/Contents/MacOS/MailMate
    

    Hopefully there is some output before the crash. You are also welcome to send a crash report.

    The “unavailable” problem should be improved in the test version. Please provide feedback if you still have this issue when the crashes have been resolved.

  • Epitaxial

    Epitaxial May 4th, 2014 @ 04:23 PM

    Same problem here, regardless of whether latest test version, or shipping version is used.

    Attached file contains crash report of launch from Terminal, and launch from icon.

    Mac mini running OS X 10.9.2.

  • benny

    benny May 5th, 2014 @ 01:51 PM

    @Epitaxial: Sorry about the late response. Your problem is new to me and MailMate is actually supposed to ask you to rebuild the database, but it crashes when trying to output some data for debugging the problem. I would like to make a debug version for you with a fix for this (such that I can obtain more information about the problem), but since I don't have time for that right now then it's also fine if you try fixing the problem by following the instructions provided here. Sorry about the inconvenience.

  • Epitaxial

    Epitaxial May 5th, 2014 @ 10:35 PM

    Benny I am trying to understand what occurred. After I posted to the ticket I found that my Mac was in fact having problems with other applications, namely: various user prefs and settings were absent.

    What might have triggered such problems is that I recently deleted an application from my Mac, using CleanApp. This application locates all the files associated with the app to be deleted and has always been satisfactory.

    I was very careful about examining the exact files to be deleted, but I may have deleted important plists or something that went beyond what was desired.

    I have ordered new RAID storage for my Mac and intended to rebuild the entire system very soon, so rather than try to fix MailMate I will simply reinstall it at that time. If the issue persists I will report. Thank you for your thoughtful help.

  • Barry MacKichan

    Barry MacKichan May 29th, 2014 @ 03:09 PM

    I had the same problem. The instructions at the above link worked for me.

    The problem originally started when ClamXav notified me that it had quarantined a message. MailMate immediately crashed and then crashed every time I tried to restart. I hope this helps you track down this problem.

  • benny

    benny June 8th, 2014 @ 02:58 PM

    • State changed from “new” to “accepted”

    @Barry: Well, the problem is that ClamXav removes a file in the private file area of MailMate. That's hard to handle gracefully. The obvious approach would be if MailMate re-fetched the missing message, but then it would just be removed again -- resulting in an infinite loop.

    It would of course be better if warned about the problem (although the antivirus software already does that), but a database rebuild would just be another infinite loop. So, that leaves some kind of weird warning: “Message x cannot be found on the disk. It could be a bug in MailMate, it could be a mistake by the user, or it could be antivirus software. In case of antivirus software, do you want to delete the message on the server or do you just want to stop try fetching it?”

    With respect to crashing instead of offering to rebuild, I think that problem is fixed, but I'm not 100% sure. Which revision of MailMate crashed for you? (If you know.)

    The accepted state of this ticket is to track progress on handling this issue more gracefully.

  • benny

    benny March 11th, 2015 @ 01:34 PM

    • State changed from “accepted” to “fixcommitted”

    I've now attempted a different workaround for this issue. Whenever saving an email (.eml) then MailMate immediately checks that it exists on disk. If not, then it is replaced by a dummy file with body text explaining the (assumed) issue.

    If anyone wants to test it then it's available in r5070+. Right now it can be fetched by holding down ⌥ when clicking “Check Now” in the Software Update preferences pane.

    (I haven't tested it myself using antivirus software and I cannot be sure that the file disappearance is correctly detected.)

  • benny

    benny March 24th, 2015 @ 12:16 PM

    • State changed from “fixcommitted” to “fixreleased”

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.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Mac OS X email client.

Shared Ticket Bins

People watching this ticket

Attachments

Referenced by

Pages