So, this won't work anymore with GoDaddy domains?
Microsoft is killing custom domain names in Outlook.com
111–120 of 145 posts
Re: Microsoft is killing custom domain names in Outlook.com
#112Earlier quoted context omitted.
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 experienced the same thing. I switched a couple of domains over to iCloud and within a week moved them elsewhere. I went from pracically no spam to hundreds of blatently obvious and easy to catch spam emails hitting the inboxes every day. I dont know what Apple uses for spam protection, but its total junk. I could roll a better spam protection myself!
Hmm. Maybe there’s a learning element or a bug with custom domains? I’ve used iCloud for years and rarely see spam in my inbox.
Re: Microsoft is killing custom domain names in Outlook.com
#113Umm...
"appears current subscribers have around 4 weeks" MS: "as of Nov 2023"
I'm thinking someone mathed wrong, but by my calculation this is over a year from now, not around a month.
Re: Microsoft is killing custom domain names in Outlook.com
#114I’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 only found out about this benefit of iCloud+ a few days ago, thankfully a few days before my prior solution was due to renew for another 2 years at a vastly more expensive rate.
Certainly easy to set up. DNS with CloudFlare and it was able to do it all with just a login confirmation from my side of things.
Re: Microsoft is killing custom domain names in Outlook.com
#115It was done poorly, you had to have Godaddy as your registrar and nameserver. If they'd just include this in a cheap O365 package with the same O365 setup it would be better.
You can use something other than Godaddy, though the process is a little complicated: https://www.reddit.com/r/Office365/comments/ft15pk/use_perso...
Re: Microsoft is killing custom domain names in Outlook.com
#116Earlier quoted context omitted.
Well, that's one very opinionated take. Yes, it's still web-based, but the parent's point is that it uses the WebView2 that comes with Windows instead of maintaining and shipping a separate Electron instance. That ought to be a net positive in any case.
OK, so Microsoft copy pasted the Chromium codebase, made some minor changes, built it, then include that build with Windows. How is that any better than the current situation? Its actually worse, since now that version will get old quite fast, unless Microsoft decides to also do forced updates like Google does.
WebView2 updates on the same cadence as Edge. Major updates every four weeks, security updates as needed.
Re: Microsoft is killing custom domain names in Outlook.com
#117Earlier quoted context omitted.
Are they different products?
Yes, very. outlook.com (formerly known as Hotmail) is an email provider. Outlook is an email client which can be used with any email provider.
I fucking hate MS branding, every fucking name confused into multiple services (remember Skype vs Skype for business ? That was different tech stack?) I thought he was talking about outlook.office365.com.
Also, outlook.com redirects to outlook.live.com/owa ....
Re: Microsoft is killing custom domain names in Outlook.com
#118Earlier quoted context omitted.
As always Microsoft prioritizes the wrong things: for example with Microsoft Teams (they're not addressing the performance issues). Same goes with Outlook. See what they introduced recently: https://twitter.com/DenysVitali/status/1587752974062944256 Wtf?
> 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.
Web version is also shit and we have other non-shit chat programs so it clearly can be better.
Re: Microsoft is killing custom domain names in Outlook.com
#119TL;DR is: If you're interested in inexpensive email hosting for custom domains, consider OpenSRS . Recently Google stopped support for custom domains for free*, so I moved my domains recently for a similar reason. I have a couple domains and they all point back to a few mailboxes. Many of the services I looked at were going to charge me per domain per mailbox not just per mailbox so the prices were artificially high.…
I set up a gmail adress, and routed all my domains through CloudFlares new Email product. It's free, and lets you route email to as many addresses as you want (? I think...) to other adresses, in this case my Gmail account. I then set up my GMail account with one profile per incoming address, and to automatically use the corresponding address when replying.
How does replying work? Specifically, if you're sending email from MyCoolDomain.com and you don't have DKIM/SPF/etc., aren't you going to face potential deliverability issues? Or is Google sending the message as `nso@MyCoolDomain.com via nso@gmail.com` (and exposing your Gmail address in replies)?
I guess you could specify Google's servers for SPF purposes without any coordination on Google's part, but Google would need to sign the message for things like DKIM. Do they do that for domains that you aren't actually connecting?
Re: Microsoft is killing custom domain names in Outlook.com
#120Earlier quoted context omitted.
If you're looking for a new provider I'd vouch for Fastmail. I switched from Google's free plan back when they killed Inbox, and I've been pretty happy with it.
Tutanota is not bad either. Still a small provider but growing. They have also E2EE calendar.
Did not care for Tutanota, mostly because I don't want to have yet another Electron app running. I just wanted to use Tutanota as an email host, with E2EE enabled where available/feasible. Instead, I couldn't use Thunderbird to access my email, which kind of killed it for me.