HI,
The issue stems from how you create an iCloud ID.
This can be done from scratch and by using an existing Apple ID.
In my own case I used an email that did not come from Apple as my Apple ID
I then used this to create my iCloud ID.
It then turns out I can access everywhere with either the Original email ID or the iCloud (@me.com) ID using the same Password.
This works for logging here at Discussions, iTunes, The App Store, The On-line Store and even the ID support site: Manage Page
The iCloud ID never appears in any of these Apple site logins, only the Original ID does.
In the case of MobileMe names it seems that it creates a two Name set up the same way but in fact both can have the same Name as in joemith@me.comjust that the iCloud one is hidden all the time.
Some people are finding that they are being asked to discontinue their MobileMe account at this point.
This then stops access to the MobileMe account stuff such as the iDisk, any web site or galleries created as the iCloud part cannot access those either.
It also stops the name working with AIM leaving only the iCloud method which needs iChat 6 or Messages Beta.
All MobileMe accounts will come to an end by the end of June 1012 anyways.
http://www.apple.com/mobileme/transition.html
On the other front, about the why these Names don't work, I did already say:-
...the issue is related to a dual login that iChat 6 and Messages apps do to both the AIM servers and to me.com.
The Login to me.com allows the AIM servers to "See" the password and to allow Login.
For this reason an iCloud name will not work in iChat 5 and Earlier - nor can you use it on the AIM settings pageas you can with earlier Apple IDs.
To be clear:-
iChat 1 through 5 login to AIM (later versions may also login to a Jabber server).
This AIM login was essentially on port 5190.
With the long standing agreement between Apple and AIM meant that the AIM servers can verify the passwords against the Apple Servers.
iChat 6 and more recently the Messages Beta (that will replace iChat) do a second Login to a server called me.com
Without this login (to me.com) the AIM servers cannot verify the Password of any iCloud issued @me.com name.
Until other Apps reverse engineer this (if it can be done) then they will not be able to log that iCloud name in.
As Apple IDs (@mac.com and @me.com types) are valid AIM names and for the most part are single Login accounts you used to be able to access the AIM Settings page.
The argument is that the account is then more secure at the loss of some functionality.
7:39 PM Sunday; April 29, 2012
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
iMac 2.5Ghz 5i 2011 (Lion 10.7.3)
G4/1GhzDual MDD (Leopard 10.5.8)
MacBookPro 2Gb (Snow Leopard 10.6.8)
Mac OS X (10.6.8),
"Limit the Logs to the Bits above Binary Images." No, Seriously