Fastmail is the best full-featured provider I could find although I wish they didn’t have a limit on aliases.
Microsoft is killing custom domain names in Outlook.com
81–90 of 145 posts
Re: Microsoft is killing custom domain names in Outlook.com
#82That's a bit of shrinkflation. I always wanted to use it, but for some reason they only supported GoDaddy domains which I definitely do not want. I guess it is Apple for me now.
I use the Zoho free plan for up to five email addresses (not counting group aliases) on several domains for maybe four years now. works great for basic email!
Re: Microsoft is killing custom domain names in Outlook.com
#83Does this mean my GoDaddy Office 365 e-mail is going away?
Re: Microsoft is killing custom domain names in Outlook.com
#84That's a bit of shrinkflation. I always wanted to use it, but for some reason they only supported GoDaddy domains which I definitely do not want. I guess it is Apple for me now.
I decided I wanted to use M365 and the domain to use it with simultaneously, so GoDaddy was the path of least resistance. I'd have avoided them if I realized it could be avoided.
Later I found out that the URL they used to forward you to GoDaddy's website happened to include the content of the records needed in DNS. Others were successful with other DNS providers. You just clicked the link, added the DNS records from the link manually, and eventually it'd validate.
Glad to see this won't affect current users.
Re: Microsoft is killing custom domain names in Outlook.com
#85Tangentially, I've been using my own domain with Gmail for years, but as of ~1y ago, it's been causing me problems. Emails sent from such custom addresses to my domain (which forwards back to my gmail) get a "This might be phishing" banner.
See, Gmail lets you configure it so that you can send emails as another address. This required a bit of verification via a DNS check, but trivial if you controlled your domain.
However, with the advent of SPF/DKIM/DMARC enforcing, this doesn't work well anymore. My main problem is that my domain is configured to forward select emails back to gmail. This breaks SPF, and I haven't yet found a way to fix this with Gmail.
I guess I need to wade through some SPF/DKIM/DMARC documentation. Google's own has not been useful.
Re: Microsoft is killing custom domain names in Outlook.com
#86I’ve been using the custom email domain feature that comes with iCloud+ for some time now, and have had zero issues with it. I imagine many of us here already pay the measly 99¢ fee for additional storage, but I was unaware of that addition until recently. Awfully easy to do, even if you’re wary of DNS. https://support.apple.com/en-us/HT212514
I host about a half dozen on Office 365. When Apple came out, I switched my wife over to iCloud, since we were paying for apple anyways. Big mistake. Spam filtering on Apple is absolutely horrific. The volume of crap she started to receive was amazing. Flipped back.
I just moved to iCloud and have the opposite problem. I forward my gmail emails to it, and most of them end up in the spam folder.
Re: Microsoft is killing custom domain names in Outlook.com
#87I’ve been using the custom email domain feature that comes with iCloud+ for some time now, and have had zero issues with it. I imagine many of us here already pay the measly 99¢ fee for additional storage, but I was unaware of that addition until recently. Awfully easy to do, even if you’re wary of DNS. https://support.apple.com/en-us/HT212514
Yup. I was already paying for iCloud and already had my custom domain email on Google.
Happily switched and never went back.
Perhaps I get an extra one more junk every other three day or week, but I can definitely live with that without giving a single penny to Google.
Re: Microsoft is killing custom domain names in Outlook.com
#88Earlier quoted context omitted.
> Microsoft Teams Teams is just a an Electron (AKA Chrome shit-client) program. So nothing can be done, unless they want to re-write the program from scratch. I'm not saying the current situation is acceptable, its not. But when you choose Electron, you more or less doom your product to having awful performance forever.
Teams is already very close to switching off of Electron to WebView2.
> WebView2
you realize thats just another Chrome shit-client right?
Re: Microsoft is killing custom domain names in Outlook.com
#89Anyone on that who also is on Apple ecosystem:
Switch to iCloud's custom domain mail (free if you already have iCloud storage plan), never look back.
Re: Microsoft is killing custom domain names in Outlook.com
#90Earlier quoted context omitted.
> Microsoft Teams Teams is just a an Electron (AKA Chrome shit-client) program. So nothing can be done, unless they want to re-write the program from scratch. I'm not saying the current situation is acceptable, its not. But when you choose Electron, you more or less doom your product to having awful performance forever.
I don't believe that nothing can be done just because it's electron. VS Code gets perfectly fine performance.
> VS Code gets perfectly fine performance
did you forget a "/s" or something?