Freron MailMate

Comments and changes to this ticket

• You flagged this item as spam.
  

  ac (at topstory) June 18th, 2022 @ 03:12 AM

  I've finally solved this. Here's what happened.

  I used YemuZip to compress a small .mp4 file (6mb) for Windows/PC.

  When I tried to attach the zipped file to an email, MailMate crashed, it was 'non-responsive', and I had to Force Quit.

  Every time I relaunched MailMate, I met a dialog asking whether I wanted to remove/recover the zipped file. The buttons on this were unresponsive, as they were on ignore/report to Apple. I must have tried this 5-6 times.

  I tried rebuilding mailboxes and reinstalling MailMate. Nothing worked. I ran OnyX maintenance. That didn't help.

  Here's what I tried next.

  I booted in RECOVERY MODE and used Disk Utility/First Aid on both my base system and the full drive.

  I used Terminal to rebuild mailboxes again, ran OnyX again.

  Then I tried to DELETE the zipped file, and that would not happen -- I kept getting a message that I did not have permission.

  I went back to a high level view and noticed my Documents folder was locked - that should not have made a difference if I had permission. I went to security settings, undid the padlock, flipped my permissions back and forth a few times, relocked the setting.

  When I went back, I was able to delete the zipped file.

  I launched MailMate again, and it looked normal except all the accounts were offline. I brought them online one by one, and everything loaded OK and worked like normal.

  A very strange behaviour was that when I tried to dismiss those discard/recover and ignore/report alerts, they were unresponsive. But if I dragged them to the side of my screen, waited a few seconds and then did control-click, they disappeared. Control-click would not work unless I moved the alerts over to the side of the screen first.

  I'm uninstalling YemuZip in case it was the culprit. There could be something about how it formats a zipped file for Windows/PC that confuses Monterey.

  So I tried a bunch of stuff, and something eventually worked.

  The issue was not MailMate. This was a permissions issue that wouldn't let MailMate do anything.

• 

  benny July 15th, 2022 @ 06:49 AM

  • State changed from “new” to “cantreproduce”

  I'm sorry for all the steps you had to go through here. Even if MailMate wasn't the cause of the issue, it's still a bug that MailMate crashed instead of reporting the issue. It must somehow not have handled the file error gracefully. Let me know if you find a way to reproduce it, e.g., by changing permissions on a file or folder before adding an attachment to MailMate.

  (I did try simply removing read permission on a file, but MailMate simply beeps when trying to attach it. That could be improved, but it didn't crash/hang.)