GPG Mail: Error while composing messages: "MCMailErrorDomain error 1030"

rjh2805's Avatar


14 Jul, 2018 08:33 AM

Which of our tools is giving you problems?

GPGMail v3.0b7

Attach a screenshot of the version info for all installed components (how to:


Describe your problem. Add as much detail as possible.

While composing new messages with GPGMail activated and message signing enabled by default, I receive the following error every now and then (screenshot attached):

The operation couldn't be completed.
(MCMailErrorDomain error 1030.)

The attempt to read data from the server "" failed.

Besides this error, everything appears to be working fine though. So this bug is more annoying than that it is causing real issues. If I disable GPGMail, the error is not shown anymore.

What did you expect instead

No error to be shown at all, since it doesn't look like there is a real error.

Describe steps leading to the problem.

Although this error pops up consistently on all my Macs, I don't know exactly what is triggering this error. The error window pops up periodically though, so it appears to be tight to a recurring (background) process.

Are you using any other plugins?


  1. Support Staff 1 Posted by Steve on 23 Jul, 2018 08:50 AM

    Steve's Avatar

    Hi rjh2805,

    thanks for taking the time to file this report.

    We've had some rare reports about this exact error the past few years but were unable to determine what exactly is triggering the error. The error itself can mean all sorts of things and when you search the web you'll find there's quite a few users seeing it, most of which are not using GPG Suite. In the cases where our users have sent in reports, the behavior was consistent with your own report as to once GPGMail is disabled, the error is no longer shown.

    In which frequency are you seeing the error?

    Do you have Xcode installed by any chance and would a remote debug session be an option for you?

    We have a ticket for this problem. I connected this discussion with the existing ticket. That means, should this discussion get closed, it will be re-opened as soon as the ticket is closed. That way you'll stay in the loop and get notified as soon as we have news. Feel free to open a new discussions should you run into further problems or need assistance.


  2. 2 Posted by rjh2805 on 23 Jul, 2018 08:56 AM

    rjh2805's Avatar

    Hi steve,

    Thanks for your reply. I do receive the described error in most composed e-mail messages, but I haven't found a reliable reproduction scenario yet.

    Yes, I do have Xcode installed, and yes, a remote debug session is certainly possible.

  3. 3 Posted by rjh2805 on 25 Sep, 2018 01:48 PM

    rjh2805's Avatar


    The latest GPG Tools version, v2018.4, does not resolve this issue. Combined with the fact that v2018.4 is a 'paid upgrade', I'd like to see this issue resolved before acquiring a license. Don't get me wrong; I'm more than happy to acquire a support license, but this issue is really a showstopper for me.

    -- Rick

  4. Support Staff 4 Posted by Steve on 25 Sep, 2018 06:56 PM

    Steve's Avatar

    That is more than understandable.

    In case you want to disable GPG Mail:

    • shut down
    • open finder
    • navigate to /Library/Mail/Bundles or ~/Library/Mail/Bundles and copy GPGMail.mailbundle to your desktop
    • now delete GPGMail.mailbundle from the original folder

    Restart Mail and check the Preferences - GPG Mail should be gone.

    To re-enable mail, close and move the bundle file back to the Bundles folder.

    This is not a trivial problem to fix. So what you are saying is completely understandable.

    We'll keep you posted on how this evolves in any case. But if you want to remove GPG Mail we can understand that of course.

  5. 5 Posted by rjh2805 on 25 Sep, 2018 07:37 PM

    rjh2805's Avatar


    If I can be of any help in finding the root cause of this issue, please let me know.

    -- Rick

  6. 6 Posted by Vladimir Mikhel... on 09 Nov, 2018 09:45 PM

    Vladimir Mikhelson's Avatar


    The issue was caused by the Exchange server certificate replacement in my case.

    As Steve mentioned earlier the message could mean multiple things, so I cannot be sure your case is similar or not..

    To summarize, all I needed to do was remove and re-add the e-mail account in Mac Mail. Application restart was not necessary. The issue was not GPG related.


  7. Support Staff 7 Posted by Steve on 14 Nov, 2018 02:16 PM

    Steve's Avatar

    Rick, are you using an exchange server?

    Thanks for the hint, Vladimir. I took a note to sk about this for future incoming cases of this error message.

  8. 8 Posted by rjh2805 on 14 Nov, 2018 03:26 PM

    rjh2805's Avatar

    @Vladimir -- Thanks for your suggestion!

    @Steve -- Yes, we're using Office365 ('Exchange Online'). Interesting enough, our company moved to a new Office365 environment last week (new domain, new account, etc.), and the issue persists.

  9. Support Staff 9 Posted by Steve on 14 Nov, 2018 03:28 PM

    Steve's Avatar

    Does that mean that switching to the new Office 365 environment meant you had to re-create the account in mail as suggested by Vladimir?

  10. 10 Posted by rjh2805 on 14 Nov, 2018 03:54 PM

    rjh2805's Avatar

    That's right. To be more precise: I had to add a new account, in parallel to the existing account, such that I could migrate some data. Then, I deleted the old account and the issue persists.

    In case you do have a debug build for me test, for example, feel free to reach out. I'm more than happy to provide you with feedback.

  11. 11 Posted by dieter on 19 Nov, 2018 09:53 AM

    dieter's Avatar

    I'm seeing the same here. Still.

  12. 12 Posted by dieter on 19 Nov, 2018 09:57 AM

    dieter's Avatar

    sorry... forgot to mention:

    1) no Office365 involved

    2) GPG Suite 2018.5 2368 ( 807c323e)

  13. 13 Posted by Merlijn on 17 Jan, 2019 02:37 PM

    Merlijn's Avatar

    This comment was split into a new discussion: GPG Mail: Error while composing messages: "MCMailErrorDomain error 1030"

    I am having the same error. No office 365 involved. It happens with an imap server. It is really annoying, but kind of used to it already as well. Would be great if it could be solved. Please let me know if there is something I could do (debugging, logs) etc.

  14. 14 Posted by stb on 04 Mar, 2019 11:18 AM

    stb's Avatar

    i have the same problem (and had it forever in the past) - what i find interesting is, that the message is triggered for one of the IMAP mail servers (incoming), but not for the account i am currently composing a message for

    if i can help with logs/debugging etc. please contact me directly

  15. Support Staff 15 Posted by Steve on 05 Apr, 2019 03:02 PM

    Steve's Avatar

    Thank you all for your updates and feedback for this problem.

    Is there anybody affected by this that is able to somehow reproduce the problem or trigger that error message?

    It would even be helpful if someone was seeing the problem with a high frequency. I am not seeing this problem at all. And a team member saw it twice over the course of several months which makes debugging the issue very difficult.

  16. 16 Posted by Vladimir Mikhel... on 05 Apr, 2019 03:25 PM

    Vladimir Mikhelson's Avatar


    The problem has never come back here after the server side was fixed.

    Thank you,

  17. 17 Posted by rjh2805 on 05 Apr, 2019 05:21 PM

    rjh2805's Avatar


    I can reproduce this issue (quite) reliably. Please let me know what I can do to provide you with debug information.


  18. 18 Posted by Piliatedwp on 14 May, 2019 04:39 PM

    Piliatedwp's Avatar

    Attempting to o delete file I get same error message
    Can’t figure out how to navigate to library/bundles.

  19. 19 Posted by Vladimir Mikhel... on 14 May, 2019 05:07 PM

    Vladimir Mikhelson's Avatar

    Just open Finder, then Go / Go to folder / type "/Library/Mail/Bundles"
    with no quotes and hit Enter.

  20. 20 Posted by Piliatedwp on 14 May, 2019 07:22 PM

    Piliatedwp's Avatar

    This comment was split into a new discussion: GPG Mail: Error while composing messages: "MCMailErrorDomain error 1030"

    Thank you very much for replying.
    I followed path you outlined, hit enter and nothing happened.
    Repeated X3 with same result.
    What am I overlooking?

  21. 21 Posted by Vladimir Mikhel... on 14 May, 2019 09:06 PM

    Vladimir Mikhelson's Avatar

    It sounds like a rights issue to me. Can you view /Library for example? 
    If not you need to provision the user you are signed in as with proper
    rights to the root directory.

  22. Support Staff 22 Posted by Steve on 15 May, 2019 03:20 PM

    Steve's Avatar

    Split Piliatedwp's request to a separate discussion. Let's continue there:

  23. Support Staff 23 Posted by Steve on 07 Jun, 2019 11:14 PM

    Steve's Avatar

    Hi rjh2805, dieter and everybody else who joined this discussion.

    We believe this issue has been fixed. If you want to test the fix, please download our latest hotfix GPG Suite. That page also has Signature file and SHA1 to verify the download.

    It would be great if you could closely observe if the problem is indeed gone. Don't hesitate to get in touch if problems persist. Thanks for helping us test this fix.


    Disclaimer: This is a development version which has not been thoroughly tested yet, so bugs or crashes are to be expected.

  24. Steve closed this discussion on 07 Jun, 2019 11:14 PM.

  25. Steve re-opened this discussion on 07 Jun, 2019 11:14 PM

  26. 24 Posted by rjh2805 on 11 Jun, 2019 06:53 AM

    rjh2805's Avatar

    Hi Steve,

    Thanks a lot. I'm running the latest nightly for a couple of days now, and I haven't seen the reported error message anymore. Before, the error message would be reported at least every minute or so while composing a message.

    What I noticed though is that the reported version number of the latest nightly is 2018.5, which seems to be incorrect when compared to the nightly's download page.



  27. 25 Posted by dieter on 11 Jun, 2019 07:11 AM

    dieter's Avatar

    hotfix installed.. will keep an eye on it

  28. Support Staff 26 Posted by Steve on 11 Jun, 2019 07:19 AM

    Steve's Avatar

    rjh2805 & dieter: Thanks for testing. The version number is expected. The build number after that is the main indicator. I use 2454n which is the latest nightly. It shows 2018.5 until as it is the nightly build release as 2018.5 is stable release. We should probably raise that version info, but then again, we don't know what the next stable will be called. Will it be 2018.6 or 2019.6. So that's why we stick with the current stable.

    Hope this makes sense.

  29. Support Staff 27 Posted by Steve on 14 Aug, 2019 07:48 AM

    Steve's Avatar

    Hi all,

    thanks for your patience. This issue should finnally be fixed for once and all. If you want to test the fix, please download our latest hotfix GPG Suite. That page also has Signature file and SHA1 to verify the download.

    We are in the midst of preparing the next release so feedback would be highly appreciated. If you have a few minutes please take the latest nightly (currently 2502n) for a spin.


    Disclaimer: This is a development version which has not been thoroughly tested yet, so bugs or crashes are to be expected.

  30. 28 Posted by rjh2805 on 15 Aug, 2019 05:26 PM

    rjh2805's Avatar


    I've been running your latest nightly (2502n) for two days on multiple machines now, and everything appears to be working fine so far.

    Could you perhaps share some light on the source of the error?


  31. Support Staff 29 Posted by Luke Le on 15 Aug, 2019 07:59 PM

    Luke Le's Avatar

    The error occurred internally when there was any problem with intermittent problem with connecting to an imap server. GPG Mail only mistakenly assumed it was an error related to the encryption or signing process and thus displayed the error.

  32. Steve closed this discussion on 09 Oct, 2019 09:33 AM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac