#1723 new
Matt

Export commands do not work for me?

Reported by Matt | 2017-03-27 16:03:12 UTC

I'm sick of crappy clients and webmail interfaces, so found MM! So far so good, but now I think I found a bug?

Both menu items under "Command" do not work for me, ie, click them and nothing happens: no popup box, etc. This affects both the "copy to mbox" and the "select export folder"

I dug around for some info and found that if no options are passed to it, it should create a folder called "export messages" on my Desktop. No such folder was created.

Very puzzled and any help appreciated.

I am running macOS Sierra v10.12.3 and MailMate v1.9.6 r5347

Comments and changes to this ticket

  • benny

    benny 2017-03-29 05:22:36 UTC

    A quick test did not reveal any problems. I also get a window asking for a disk location when using “Select Export Folder”.

    Try launching MailMate from a Terminal window to see if any errors are output when it fails. Quit MailMate and then paste the following line in a Terminal window (/Applications/Utilities/Terminal.app):

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

    Let me know what happens.

    Thanks for trying out MailMate.

  • Matt

    Matt 2017-04-03 15:36:25 UTC

    I got a weird email saying that I couldn't send to the email list, so I'm copying and pasting here!

    Yesterday:
    First, I launched normally from Applications icon to confirm no popup box when selecting the commands. Yes, confirmed. Then I quit and relaunched from the Terminal. Now it works!
    Hm, decided to check if launching like regular way. Works too!
    So that was weird...

    Today:
    Normal launch, tried again, nope no popup box. Weird. Quit and relaunched. Worked. So it seems intermittent? Also today, before the popup box came up, I saw the "wheel of color" spin for a good few seconds so I guess it was thinking about something. But when it doesn't work, I don't see the wheel of color. There's never any feedback.

    Anyway, it's not a function that I'll use frequently, but at least now I know it works! Thanks!

    Let me know if you want to investigate further!

  • Guillaume Daudin

    Guillaume Daudin 2017-10-12 08:51:23 UTC

    Hi,

    I have the same issue. The menu item under command do not work for me.
    I have relaunched from the Terminal with no luck.

    I am on MacOS High Sierra 10.13 and Mailmate 1.9.7.

    Best,

    Guillaume

  • benny

    benny 2017-10-21 15:12:05 UTC

    @Matt: Do you still have the problem when not launching from the Terminal? (Sorry about the late follow-up.)

    @Guillaume: Does “Select Export Folder” also fail for you?

  • Guillaume Daudin

    Guillaume Daudin 2017-10-21 15:47:15 UTC

    Yes, "Select Export Folder" fails as well : it has no effect.

  • benny

    benny 2017-11-13 09:32:25 UTC

    @Guillaume: Sorry about the late reply (again). I've now tried the export commands on High Sierra and I don't have any issues.

    Try launching MailMate from a Terminal window (/Applications/Utilities/Terminal):

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

    Then try “Select Export Folder” and see if you get any error messages.

    Thanks in advance.

  • Guillaume Daudin

    Guillaume Daudin 2017-11-13 17:57:54 UTC

    After launching from terminal, Select Export Folder launches a "Open" window where I can select a folder.

    After choosing one, the other menue choice have no effect. And the Select Export Folder does not work anymore.

  • benny

    benny 2017-11-14 09:31:41 UTC

    Do you get any error messages in the Terminal window when trying the other options? (I assume you have selected 1 or more emails before trying.)

  • Guillaume Daudin

    Guillaume Daudin 2017-11-14 12:14:44 UTC

    I tried again and it works.

    I believe I was trying to export folders rather than messages. Sorry for the bother.

  • benny

    benny 2017-11-14 14:42:47 UTC

    • State changed from “new” to “resolved”

    No problem. I should have realized what the problem was.

  • Robert Booth

    Robert Booth 2018-05-16 19:04:04 UTC

    The following commands do not work on my machine. MacOS High Sierra Version 10.13.4

    Non of the commands work.

    Command -> Export Copy to Folder
    Command -> Export to mBox

    When running MailMate from a terminal window as suggested the following errors are reported once MailMate is terminated.

    CoreData: error: API Misuse: Attempt to serialize store access on non-owning coordinator (PSC = 0x7ff90d451ec0, store PSC = 0x0)
    CoreData: error: API Misuse: Attempt to serialize store access on non-owning coordinator (PSC = 0x7ff90d451ec0, store PSC = 0x0)

  • benny

    benny 2018-06-03 07:48:17 UTC

    @Robert: Sorry about the late response. Just to make sure: Did you select any emails before trying these?

    The error output is not related. I'm actually not quite sure where that output comes from, but I suspect it might be triggered by Apple's (old) address book framework which MailMate uses.

  • Anonymous

    Anonymous 2018-12-28 19:56:35 UTC

    This may help someone.

    Command | Export didn't work for me either. I'm on Mojave 10.14.2, Mailmate Version 1.12.3 (5579).

    If I start MailMate from the command line, Command | Export | Select export folder gives the following output on terminal:

    Warning: Failed to run command (64:196: execution error: System Events got an error: Can’t make file "SSD:Users:avs:Desktop:MailMate Export" into type alias. (-1700)
    ):
    

    ...followed by a Bash script. Now, the path above (~/Desktop/MailMate Export) did not exist, and after creating it manually, both the export folder selection and mbox export started working.

  • Bigbalagan

    Bigbalagan 2019-01-03 18:12:51 UTC

    • Assigned user cleared.

    FWIW, make sure you check on via Command | Export | Select Export Folder to ensure you're looking in the right place for output. Also, which was not obvious to me, select the emails you want to export!

  • benny

    benny 2019-01-14 10:05:43 UTC

    • Assigned user set to “benny”

    I'm not quite sure if this was a Mojave issue only, but I've fixed the issue reported by Antti in the next update.

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

Pages