Q: When will Apple address the following email issue: The operation couldn’t be completed. (MCMailErrorDomain error 1030. ... When will Apple address the following email issue: The operation couldn’t be completed. (MCMailErrorDomain error 1030.) Select a different outgoing mail server from the list below or click Try Later to leave the message in your Outbox.... more
-
All replies
-
Helpful answers
-
Feb 16, 2015 9:10 AM in response to J2Bikerby Barry Hemphill,Contact your ISP.......IMHO, the issue you have is not an OS X 10.10 issue.
Barry
-
Feb 16, 2015 10:42 AM in response to J2Bikerby cmdelrioc,The same is happening to me from time to time. I don't think it has to do with with the ISP because it doesn't always happen and it only started after I upgraded to Yosemite. One more of the many problems I'm having with this version of OS X.
-
-
Jun 24, 2015 2:10 AM in response to J2Bikerby Ian Eiloart,I'm seeing that same error on an Gmail hosted IMAP server. Not sending, but fetching mail.
1. I've been using the same settings for several years.
2. I have two Gmail accounts, and the other one is working just fine.
3. Connection doctor doesn't show any issues.
4. After a few minutes, the error fixed itself.
This could be a transient DNS error, since the message is about the domain. If that's the case, it will fix itself (my problem did). Alternatively, you'll see lots of people posting different fixes, which don't actually do anything, but which might seem to work for you.
It's annoying that Apple don't have any documentation about the meaning of the error messages. At least, not that I could find: even on the developer site.
-
Jan 29, 2016 4:27 AM in response to Ian Eiloartby Gerben Wierda,I think it might have to do with the DNS cache. I suddenly got this problem too and I have many types of network connections (public wifi, USB-tethering and every time the DNS setup changes). Sometimes I setup a VPN and then the company mail server gets an internal IP address (split DNS setup). I had this problem and turned on the VPN. The mail went out perfectly in that case so password and so forth are OK. Then I turned VPN off again and it worked again with an outside connection to the company mail server.
My conclusion: somehow a caches was kept and a cached IP-address for the mail server was used that wasn't correct anymore. Hence the 'domain' error. It seems a network change might not always perfectly clear the right caches (mail keeps its own cache somehow and it isn't always cleared when it should?). Switching network settings (e.g. turning a VPN on and off) again, fixed it for me.
I think this is a bug in OS X. I've noticed more often that Apple's optimisations are not always perfectly robust. This might be another example.
I should report this in bugreporter, but I'm too busy.