MFMessageErrorDomain error 1035 sending mail

Question

MFMessageErrorDomain error 1035 sending mail

I've just upgraded my second tiger box to leopard.

Now I can't send mail - it just gives:

Operation could not be completed. (MFMessageErrorDomain error 1035.)

Now. The server runs courier imap(s)/pop(s) with a self-cert certificate and smtp (exim4) again with a self-cert certificate (different certificates).

Under tiger - I had both certificates in the X509Anchors keychain.

So - to leopard. Note - this is working just fine on the first box I upgraded (mac mini).

When first browsing the imap server mail says "untrusted certificate". I say always trust, and give an admin user/pass combo. This inserts the certificate into the System keychain.

But sending via SMTP (start TLS) just gives the 1035 MFMessageErrorDomain error.

I've tried grabbing the SMTP certificate file instead from my mac mini system keychain (also leopard and happily able to send mail) and importing it to the system keychain. No dice. Mail.app just throws this same error.

I'm a little lost as to why - and I can't figure out what I have to do to get mail working again.

MB Pro 17" (2.16/2Gb), Mac OS X (10.5.1)

Posted on Dec 1, 2007 3:13 PM

Reply

Answer 1

Dec 1, 2007 3:21 PM in response to Chris D Searle

Just spotted the following in the console log

Dec 2 00:02:03 slippen Keychain Access[2720]: Exception raised during start of kcproxy: Couldn't register server "com.apple.KeychainProxyServer" on this host.
Dec 2 00:02:03 slippen Keychain Access[2720]: Couldn't register server "com.apple.KeychainProxyServer" on this host.

Again and again.

Googling isn't showing me much on that one.

Reply

Answer 2

Dec 2, 2007 10:59 AM in response to Chris D Searle

I gave up. Completely trashed my keychain (rm -rf) and logged in with a blank one.

Now it works as expected.

I have no idea what was wrong with the keychain - and why Keychain first aid couldn't help.

Reply

Answer 3

Dec 10, 2007 10:25 AM in response to Chris D Searle

I'm experiencing the same error. I'm glad you found a work around, but this is at least the 5th time Leopard has corrupted my keychain and I'm getting sick of it.

Reply

Answer 4

Dec 11, 2007 12:43 AM in response to The D Man

I recall from way back that Keychain .mac syncing did corrupt the keychain several times under Tiger. In the end I gave up on it - and I have to say (fingers crossed) that I've not had keychain issues since.

Reply

Answer 5

Ascinto

Level 1

4 points

Dec 15, 2007 12:32 PM in response to Chris D Searle

The easy way to fix this;

1. Search keychain for the outgoing mail server name producing the error
2. deleted the records that come up
3. re-enter the password for the outgoing mail server in Apple Mail

Then it works, it looks like this comes up with Leopard mail if the keychain record was created in Tiger.

Reply

Answer 6

divokz

Level 1

0 points

Feb 3, 2008 6:13 PM in response to Ascinto

This worked for me as well, even though I created my mail account in Leopard. I just recently started using a digital signature -- the problem occurred with that.

Reply

Answer 7

SunSparc

Level 1

45 points

Feb 11, 2008 3:05 PM in response to Ascinto

I have the same problem, however, it is only with one account. I have 5 different email accounts in Apple Mail and they each attach to a different mail server. Digitally signing works with the two others that I have tried, it is only one account that is having issues.

I did try deleting the certs for the account in question but the problem came back when I re-accepted those certs.

Reply

Answer 8

SunSparc

Level 1

45 points

Feb 11, 2008 5:36 PM in response to SunSparc

Well then. I deleted everything (certificates and passwords) for the particular domain and then when they were re-added I made sure to set them to "Trust Always". So now things are working. Thanks for the help.

Reply