top | item 43511464

iCloud Mail has DNS misconfigured?

180 points| wildekek | 11 months ago |mail-tester.com

87 comments

order

Avamander|11 months ago

They also started using new IPs without PTR records to send out mail. Though so has Microsoft just recently. Both heavily frown upon that when receiving mail themselves. Do as we say...

kemotep|11 months ago

I hate getting a report telling me my work domain is blocked because it is missing a PTR record and we use Exchange Online. I can’t do anything about that!

wildekek|11 months ago

Not only does Apple frown upon that, they just silently drop emails that are sent from a server without PTR records. Yes, that includes their own servers. Yes, sending email from iCloud to iCloud is silently dropped if they decide you get assigned an outgoing server without PTR. The absolute amateurism just blows my mind.

walrus01|11 months ago

It's incredibly entitled of some big cloud based operator to send mail from an SMTP source that doesn't have proper reverse DNS. Any normal independent small operator sending mail without proper reverse DNS will increase its likelihood of spam rank by a thousand percent. Or get flat out rejected at the SMTP negotiation process or relay attempt.

But things like icloud, office365, google workspace and similar are "too big to fail", right? They don't have to play by the same rules as the rest of us peons.

as referenced here, from the post on the 'mailop' mailing list

https://news.ycombinator.com/item?id=43512353

This is either an astonishing level of technical fuck-up from what has to be an entire work group of people with six figure salaries whose jobs are nothing but running email server infrastructure, so they must clearly know better, or a lack of regard for the internet community and accepted standards. I really cannot think of a third possible explanation for it.

To be clear for those people who don't run their own email servers: Having proper reverse DNS for the IP of your outbound SMTP sending server is one of the absolute bare minimum requirements for accepted mail flow, and is a standard that's probably 25 years old or older now. It significantly pre-dates SPF, DKIM, DMARC and all the rest. Proper RDNS is literally one of the first things you verify before you set up everything else.

wildekek|11 months ago

So, Apple sends the wrong EHLO domain when trying to send emails out. This results in them dropping emails to their own users. Can't get past Apple's level 1 support. How can I get to someone that maintains their SMTP k8s cluster?

nikanj|11 months ago

> How can I get to someone that maintains their SMTP k8s cluster?

By posting on Hacker News and making it to the front page. The same support strategy also works for all the other major providers

rreichel03|11 months ago

A few years ago, when iCloud custom domains first launched, I found a bug where Apple would permanently cache the MX record. If an iCloud user had ever used a custom domain, future emails from iCloud to that domain would still get routed to their iCloud inbox—even if the domain’s MX record no longer pointed to Apple. They eventually fixed it, but didn’t think it deserved a bounty, which was a bit surprising.

I'm sure there's a ton of interesting surface area here.

djhworld|11 months ago

I lost faith in iCloud custom domains a few months ago, I was receiving the usual marketing emails etc fine, but actual person to person emails? Sometimes replies would come through, other times nothing.

I thought at first people were just ignoring me, but when a company reached out to me over SMS to respond to a complaint I had, they said their email reply had bounced so was contacting me on SMS instead

Switched to fastmail at that point.

9dev|11 months ago

You’re really scaring me—I also had the impression people are ignoring me, and didn’t even consider their mail simply bounces… I’m so over migrating email again.

MisterBiggs|11 months ago

Is this new? I've been using icloud with a custom domain for about a year and just had my first failure today with an address that I've actively been talking to all week.

DrBenCarson|11 months ago

Yes, I’ve been on iCloud 2y+ and saw my first failure today

zeagle|11 months ago

I switched from migadu to iCloud to increase my bus factor for the family. It's been interesting and a bit painful. For example I have a filter to forward emails from an 'bothofus' alias to my spouse's iCloud account at the same domain because there is no way to have a true alias --> mailbox1, mailbox2. Sometimes iCloud bounces these emails from sent from itself.

JumpCrisscross|11 months ago

> to increase my bus factor for the family

?

jeffbee|11 months ago

p00-icloudmta-asmtp-us-central-1k-100-percent-10.p00-icloudmta-asmtp-vip.icloud-mail-production.svc.kube.us-central-1k.k8s.cloud.apple.com is one hell of a name, though.

Did you try postmaster@apple.com, hostmaster@apple.com, or icloudadmin@apple.com (not traditional, but given in their docs)?

ndegruchy|11 months ago

I paid for that domain, I'm gonna use all of the characters in that domain!

jasonjayr|11 months ago

Interesting insight into how they organize their compute resources!

cchance|11 months ago

i mean if if your never typing it which... i mean they never are its all automated most likely, why not have all the details they could ever need probably makes tracking issues and traceroutes etc much easier to deal with

Galaco|11 months ago

iCloud Custom Domains & Mail are filled with bugs. My favourite one is that if my custom email I want to register has EVER been associated with an Apple account, it can never be used as a custom domain, unless that domain is set to catch all; it is impossible to add that specific address; it just errors without any specific message. The original account was fully deleted; going to the arduous process they set up that takes weeks to actually delete the account.

Customer support is worthless for actual technical problems as usual for Apple. Fun extra regarding customer support; if you arrange a support call in a language not native to your region, they honor that, but that information is lost if they escalate the call; the callback is always in the national language, despite explicit requests over the phone during the callback schedule

CraigRood|11 months ago

For what it's worth, I was able to add my custom domain to iCloud under this exact scenario without any issues. This was 3 years ago, so I don't know if anything has changed, and I didn't have the 'catch all' limitation either.

ctippett|11 months ago

I had to give up trying to use iCloud for email. So many inbound emails would be silently dropped. I've also sent emails to @icloud.com addresses that the recipient never received.

The deliverability issues also apply to their Hide My Email feature. I frequently miss confirmation or verification emails after signing up with a @privaterelay.appleid.com address, so much so that I don't even bother with it anymore.

iancarroll|11 months ago

We send OTP codes for our login flow and iCloud is definitely a big source of delayed email complaints. Codes eventually arrive, but not before a support ticket is created. Instant on every other ISP.

jlund-molfese|11 months ago

I'm seeing 10/10 though, with a custom iCloud domain ("Your hostname outbound.mr.icloud.com is assigned to a server.").

What's different?

wildekek|11 months ago

You got assigned a different outgoing server/PoP.

alfiedotwtf|11 months ago

This shows that email should die in a tyre fire and we all need to collectively move to something else… but we should have done this more than 10 years ago.

Email has SO many technical issues that if someone would have come out with email today, nobody would use it!

The ONLY thing going for it really is that it’s decentralised and has the network effect that almost everyone uses it. Bzzzt, I kid I kid!

Anyone under 25 will tell you they do NOT use emails and instead prefer instant message, and is email really decentralised? NO!! Try setting up your own relay and you’ll be dropped by any big service. Gmail+Outlook is basically a cartel with zero recourse!

Hmmm… could there even be a case of anti-trust given Gmail’s behaviour

tonyedgecombe|11 months ago

Yes, we should move to a proprietary service where the provider can extort us for the rest of our lives.

diegoholiveira|11 months ago

The only issue that I have with iCloud+ with my custom domain is about two gmail accounts which I don’t get mail from. It’s super weird.

chrisweekly|11 months ago

My bizarre email issue is about gmail, not iCloud, but I'm hoping someone clueful can weigh in.

In my gmail inbox I periodically get very strange emails from mailer-daemon@googlemail.com, addressed to username+caf_=username=example.com@gmail.com

(where "username" is my gmail user, and "example.com" is the domain of a consulting client from a decade ago that gave me username@example.com)

The body of these weird messages says

Address not found Your message wasn't delivered to username@example.com because the address couldn't be found, or is unable to receive mail.

550 5.1.1 The email account that you tried to reach does not exist. Please try double-checking the recipient's email address for typos or unnecessary spaces. For more information, go to https://support.google.com/mail/?p=NoSuchUser 6a1803df08f44-6ac070f1538sor47269616d6.5 - gsmtp

above an arbitrary supposedly-forwarded message like

---------- Forwarded message ---------- From: The New Yorker Daily <newyorker@newsletter.newyorker.com> To: username@gmail.com Cc: Bcc: Date: Tue, 28 May 2024 16:31:02 -0400 (EDT) Subject: The Secrets of the Stasi ----- Message truncated -----

aequitas|11 months ago

@wildekek, hi Willem. Nice seeing you here. Still in the mail business?

wildekek|11 months ago

@aequitas, Hi Johan, nice surpise! After wondering why I couldn't get enough of the movie Office Space, I quit the tech industry completely. Never felt better.

johnklos|11 months ago

The biggest problem with huge corporations is that sometimes it's next to impossible to actually communicate with them. Does anyone have any good contacts at Apple?

I sent this more than two weeks ago:

  Date: Wed, 12 Mar 2025 22:56:55 +0000 (UTC)
  From: John Klos <*******@klos.com>
  To: apple.com-Admin@anonymised.email, apple.com-Tech@anonymised.email, Apple-NOC@apple.com, d*******@apple.com
  Subject: Issue with Apple's SMTP delivery
  
  Hello,
  
  I've had several issues reported about email delivery from Apple. The error they have in common is this:
  
  Mar 12 21:38:17 daisy sm-mta[28249]: 52CLcCoi028249: ruleset=check_mail, arg1=<*******@me.com>, relay=p-west1-cluster6-host7-snip6-8.eps.apple.com [IPv6:2a01:b747:3003:204:0:0:0:47], reject=550 4.1.8 <*******@me.com>... Access denied. HELO does not resolve. (HELO p00-icloudmta-asmtp-us-west-1a-1.p00-icloudmta-asmtp-vip.icloud-mail-carry.svc.kube.us-west-1a.k8s.cloud.apple.com)

  Looking in to this, the resolution of "p00-icloudmta-asmtp-us-west-1a-1.p00-icloudmta-asmtp-vip.icloud-mail-carry.svc.kube.us-west-1a.k8s.cloud.apple.com" results in this list of MX:

  mx-in.g.apple.com
  mx-in-mdn.apple.com
  mx-in-hfd.apple.com
  mx-in-ma.apple.com
  mx-in-rn.apple.com
  mx-in-vib.apple.com
  mx-in-rno.apple.com
  mx-in-sg.apple.com
  
  All but two of these resolve to A records.
  
  Two of those, though, resolve to more MX:
  
  host mx-in-rno.apple.com
  mx-in-rno.apple.com mail is handled by 10 mx-in.g.apple.com.
  mx-in-rno.apple.com mail is handled by 20 mx-in-vib.apple.com.
  mx-in-rno.apple.com mail is handled by 20 mx-in-rno.apple.com.
  mx-in-rno.apple.com mail is handled by 20 mx-in-rn.apple.com.
  mx-in-rno.apple.com mail is handled by 20 mx-in-hfd.apple.com.
  mx-in-rno.apple.com mail is handled by 20 mx-in-sg.apple.com.
  mx-in-rno.apple.com mail is handled by 20 mx-in-mdn.apple.com.
  mx-in-rno.apple.com mail is handled by 20 mx-in-ma.apple.com.
  
  host mx-in-mdn.apple.com
  mx-in-mdn.apple.com mail is handled by 20 mx-in-mdn.apple.com.
  mx-in-mdn.apple.com mail is handled by 20 mx-in-sg.apple.com.
  mx-in-mdn.apple.com mail is handled by 10 mx-in.g.apple.com.
  mx-in-mdn.apple.com mail is handled by 20 mx-in-vib.apple.com.
  mx-in-mdn.apple.com mail is handled by 20 mx-in-rn.apple.com.
  mx-in-mdn.apple.com mail is handled by 20 mx-in-hfd.apple.com.
  mx-in-mdn.apple.com mail is handled by 20 mx-in-ma.apple.com.
  mx-in-mdn.apple.com mail is handled by 20 mx-in-rno.apple.com.
  
  This loop is a mistake and should be fixed.
  
  Additionally, RFC 5321 section 2.3.5 says that the name given in an EHLO / HELO greeting should be an IP literal or a primary host name ("a domain name that resolves to an address RR"). The name given in the EHLO / HELO exchange does not resolve to an address RR; it only resolves to an MX. While this is technically incorrect, the looping MX is the real issue. However, if you're fixing the looping issue, you may want to consider fixing this issue at the same time.
  
  Please look in to this, and please let me know if you have any questions or need any additional information.
  
  Thank you,
  John Klos

eddythompson80|11 months ago

So you created a proxy to an endpoint to an email from iCloud and something in the chain had a misconfigured DNS with the domain “p00-icloudmta-asmtp-us-central-1k-100-percent-10.p00-icloudmta-asmtp-vip.icloud-mail-production.svc.kube.us-central-1k”. It might as well be an issue with mail-testers.com or icloud.com

It’s impossible to tell from the shared page because both services are about DNS caching.

wildekek|11 months ago

Update @12:16UTC: This seems fixed now! The 57.103.74.0/24 block now had PTR records.

herghost|11 months ago

Mr Jenkinson will be here any minute now, chasing ambulances.

psaux|11 months ago

When you own a 17 net or 12 net, I think it comes as a given on extra txt records not needed. Totally not fair, but reality, and someone’s allowing it on the filtering side.