Freron MailMate

Comments and changes to this ticket

• 

  benny December 18th, 2013 @ 08:04 AM

  It appears you have found a bug in the code that decodes base64 encoded body parts. This also means that it is likely triggered by a particular message. When you add the account then you can “Edit Subscriptions” to add fewer mailboxes initially (alternatively, take all mailboxes offline if you can do it before the crash). The goal is to find the mailbox that makes MailMate crash. If this is successful then you can enable the following debug variable:

  defaults write com.freron.MailMate MmDebugFetchCrash -bool YES
  

  Then relaunch MailMate and then take the mailbox online to trigger the crash. After that, you should be able to find the message in this folder:

  /tmp/*.eml
  

  The name is based on mailbox name, server name, and a unique id. It's the one most recently written to disk. Hopefully it's a message you can share with me (“Help ▸ Send Feedback”).

  I hope that wasn't too confusing.

• You flagged this item as spam.
  

  Bob Arasmith December 18th, 2013 @ 04:46 PM

  I have narrowed it down to a the "Sent Items" mailbox. But when I enable MmDebugFetchCrash I do not get the .eml files you expected. I see one directory /tmp/mailmate_logs and inside it is a zero length file, mail mate_parser_problems.log.

  My sent items mailbox is quite large, 8300 messages, so I am going to try and prune it back to find the problematic message. When I hunt it down I will send it to you.

• You flagged this item as spam.
  

  Bob Arasmith December 18th, 2013 @ 10:23 PM

  I narrowed it down to the mail message that causes the problem. It has two attachments, a zip file that is 231MB and a PDF that is 735KB. I have no problem forwarding the message to you if you mail server will accept that large of an attachment.

  If I move that mail message in and out of a subscribed folder I can reliably crash the client.

  bob

• 

  benny December 19th, 2013 @ 09:28 AM

  • State changed from “new” to “reproduced”

  That makes it likely that the size of the attachment is the problem (and not this particular attachment) although I would have thought it would have required an even larger attachment.

  (I had no idea anyone had such large email attachments :-) ).

  I'll mark this ticket as a reproducible problem (although I haven't tried it yet), but don't expect it to be fixed soon. I hope you can work around the issue.

• You flagged this item as spam.
  

  Bob Arasmith December 19th, 2013 @ 04:44 PM

  no problem at all, in my 10 years or so of back mail that is the only occurrence of an attachment that large. I am sure I can work around it. Thanks for the help tracking down the problem.

• 

  benny April 8th, 2018 @ 07:12 PM

  • State changed from “reproduced” to “fixreleased”

  This was most likely (implicitly) fixed when MailMate became a 64 bit application a long time ago.