Just a reminder to everyone: Do not rely on the sender's address to verify the validity of an e-mail. The sender's address is much to easy to spoof and there is almost* no checking at all by mail servers and none by mail clients. Yes, if the senders address looks bogus then the e-mail is probably bogus. Unfortunately the reverse is not true.
I too received an e-mail from <no-reply@insideicloud.com>. While this is probably a legit address the body of the e-mail smelled phishy. The subject line was: "You can't sign in because your account was disabled for security reason". The message consisted of an image from a server using a raw IP address rather than a domain name, and an attachment with the file name: "Apple-form-document.html". My mail client blocked the download of the image file.
I saved the attachment then opened it in a true text editor (not Apple's TextEdit). It was HTML, but with a lot of JavaScript files to download from that same IP address where the image is hosted. I looked it up: The IP address belongs to an ISP in Houston, Texas. Why would Apple use an unnamed sever connected through an ISP, and not one of their own servers?
So it is a phishing e-mail. No telling what would have happened if I'd opened the attachment in a web browser. Perhaps the JavaScript is malicious, or maybe they only want to steal my Apple ID. Oh well, that Houston ISP has an e-mail address for IP management. Perhaps I'll drop them a message telling them that whoever is at "192.185.2.110/~dsecure" is running a phishing scam.
Take care and be safe.
* In theory SPF can prevent this sort of problem, but it requires Apple to have an SPF record in their DNS with an aggressive setting, and our receiving e-mail server to check SPF records and have an aggressive response for mail that fails the test. Thus I say "almost" because few companies use SPF in this way, if at all.