When I woke up this morning, I had a handful of emails waiting for me in my iCloud inbox, and alongside those was a series of delivery error notifications. There was one for every new email I had, and among all the mumbo-jumbo, they all said the same thing: “recipient is not a valid address.”
It’s the error you usually receive when you try to send an email to an address that doesn’t exist, and I know I’m not the only one who’s receiving them; over the course of the morning we’ve had a number of emails from readers who are seeing the same thing, and there are plenty of forum posts detailing the issue all over the web.
So what’s going on with the iCloud mail service?
Well, according to Apple, there’s nothing wrong. I’ve been keeping an eye on its service status page all morning, and everything is “normal.” There appear to be no known issues concerning any of the iCloud services — as you can see from the screenshot below.
But clearly that’s not the case. I, and many other iCloud users, are receiving errors for every email they receive. One forum thread on the Apple Support Communities pages now has over 50 replies from iCloud users seeing the same issue, and it’s been viewed nearly 800 times.
The reason for the error, according to the email, is “error in sieve filter.” It’s unclear what that means — at least to me — but as far as we can tell, iCloud emails are still being sent and received as normal. There’s not too much to worry about at the moment, then, if you can cope with these annoying errors for every email you receive.
Some of the users on the Apple forum say that they’ve contacted the Cupertino company and that they’ve been assured it’s looking into it — despite no acknowledgment of it on its service status page.
I just called Apple support to let them know that many people were experiencing the same issue and they told me they would inform their main tech department. At least now they’re working on the problem.
All we can do for now is wait for Apple to fix the problem, but at least you can take comfort in the fact you’re not the only one seeing the issue.
We’re hoping for an update from Apple soon, and as soon as we hear anything, we’ll let you know.