new iCloud email account not working - duplicate/ambiguous directory match error

Hello,

Well, apparently once creating the new me.com account; it takes a bit for iCloud to create the new email. At first it was not connecting but now it has allowed access and has also allowed me to send and receive emails. iCloud is working now and connected.

It was just waiting for the system to activate the email which is understandable will millions running to set it all up.

I hope this helped as it took care of itself. Thank God Apple resolves things quickly!

Is anyone still with issues?

Yes - still having the same issue here.... iCloud is trying to use my old @mac and not my new @me address... with no way (that I can see) for me to manually change it.

Umm well I can now log into the mail app on iCloud, and see my emails

And my iPhone as just recieved some of those emails, but my Mac's are still not connecting and getting mail pushed to them

So maybe I will have to wait and see, all was ok last night and none of my settings have changed,

I may just forward them to Gmail that way I know I will get them, but that's not what I wanted to do, I may just as well stayed with Gmail in the first place Hay Ho

Mine is working now. Here is what I did. I am not sure if I fixed it or Apple just started working, but it works now.

I deleted the account from Mail.

I went to "System Preferences" and signed out of iCloud.

Then I signed back into iCloud and added the account back in Mail. It took a long time to download all the mail but it works now. I hope this helps someone.

I created a new me.com email becuase i was using an apple ID with a gmail email. it promted me to create a new me.com email...so i did and have not been able to access the email account. when i visit icloud, i can access everything but the email. i send a report to apple, but nothing.

genius bar stated it's all server related. Horrible! They told me to use the apple care chat line or call them. Great, I'll probally have to pay to talk to them. Unbelieveable that Apple is blowing it again -- you would think they would have learned from MM.

well I am having the same issues too. this is bloody rediculous.

I am also having similar problems. I am unable to send form my iPhone, but I am able ot receive. When I logon to the iCloud site I can send and receive. I guess on my lunch break I'll go with the suggestion of deleting it and then adding it back in. I don't have many emails in it at the moment so it should not take to long to do that.

Im having this EXACT same problem and its infuriating me to no end. Its happened ever since itunes made me change my password last night. I now cant use the @me.com email, and just as you say, the password mask has less characters than it should (it has the same amount of characters as my OLD password). Entering the new password does verify, but then it just loads the old password again for some reason.

So god **** annoying.

THANKS FOR THAT. Words are easier to understand when you shout them at people. Proper grammar would dictate that you use italics to emphasise words and phrases, not bold type.

Regardless of that enlightenment you bestowed upon me, iCloud mail still wasnt working. The mail client kept telling me the password was wrong and I could not log into the mail portion of icloud.com

That being said i've fixed it. I just changed my password ... again. So if anyone else is experiencing this problem, simply change your password again and all is better with the world.

Any luck with this? Im still having the same issue on my iphone, I cant send emails.

Just delete the icloud account in settings -> iCloud -> Delete Account. Now add it again with your @me as apple ID instead of @mac, it will automatically detect your @mac id and now your mail is configure with correct @me address. Try and let me know you have doubts.

Same problem here. I used my Apple ID that I've been using for years as the password so I'm reluctant to change it to soemthing I won't remember. I'll wait and see what happens.

Thanks. That worked perfectly. Had to dig around for hrs to resolve this issue. Not immediately obvious.