Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Microsoft is killing custom domain names in Outlook.com

bigtechwire.com

Post reply on HN
Print view View original

61–70 of 145 posts

Re: Microsoft is killing custom domain names in Outlook.com

#61

Post by thiht »

bluesign wrote: post #44
boston_clone wrote: post #22

I’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

Lack of catch all there seems to be a blocker for many including me

It supports it since iOS 15 if I’m not mistaken (last year release)

This is probably the best dollar I spend every month

Re: Microsoft is killing custom domain names in Outlook.com

#62

Post by InTheArena »

boston_clone wrote: post #22

I’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.

Re: Microsoft is killing custom domain names in Outlook.com

#63

Post by cmeacham98 »

smileybarry wrote: post #51
cmeacham98 wrote: post #29

Earlier quoted context omitted.

I'm not sure why this can't work with basically any email provider? Setup you domain like normal, and configure gmail to forward all incoming mail to your address on your domain. What is the feature you're missing here?

It can, but then pricing bothers me. I just got so used to G Suite free that I don't want to tack on a $10/month subscription for forwarding. (It's silly given the myriad of other subscriptions I'm fine with, though)

You're not paying for forwarding, you're paying for someone to host a whole email stack for you (and the associated dev work such as on clients).

You can choose to use a "free" provider like Gmail if you're ok with paying with your data and a lack of features (such as not being able to use a custom domain).

Also by the way, Fastmail is half the price you list at $5/month (might have to prepay a year to get that price).

Re: Microsoft is killing custom domain names in Outlook.com

#64

Post by D13Fd »

svnpenn wrote: post #59
denysvitali wrote: post #48

Earlier 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.

I don't believe that nothing can be done just because it's electron. VS Code gets perfectly fine performance.

Re: Microsoft is killing custom domain names in Outlook.com

#65

Post by georgyo »

UberFly wrote: post #19
kosik wrote: post #6

Looks like they are giving 1 year before actually introducing that change. It's either the quote or the article wrong saying users will have only 4 weeks remaining.

I wonder for how many it's more like 1 year to migrate to some other service.

They are not removing the functionality for people who already have domains added

Re: Microsoft is killing custom domain names in Outlook.com

#66

Post by annoyingnoob »

smileybarry wrote: post #50
annoyingnoob wrote: post #20

Earlier quoted context omitted.

I get plenty of custom domain name spam that comes through outlook.com (I'm not even talking about M365/O365). Free or not, Outlook.com is abused for spam constantly.

Outlook.com custom domain is M365/O365, it's one of the paid features in those plans.

Fair enough. For $7.00 you can add up to 900 domains to one account and spam away for a month. As long as you setup SPF, DMARC, and DKIM then your messages are likely to be delivered. Switch accounts and domains as often as you like. It is not much of a cost and almost all of it can be automated.

Re: Microsoft is killing custom domain names in Outlook.com

#67

Post by Destitute »

svnpenn wrote: post #59
denysvitali wrote: post #48

Earlier 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.

Teams is already very close to switching off of Electron to WebView2.

Re: Microsoft is killing custom domain names in Outlook.com

#68

Post by Destitute »

smileybarry wrote: post #60
denysvitali wrote: post #48

Earlier 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?

We had the first rollout of that feature, where it was just "" and only on the web. It was weird, being able to "like" email messages but no one saw it unless they opened the web client. But that's nothing compared to "the new Outlook"[1] being a webview around the Outlook.com UI library . It looks really nice in concepts but once installed it just feels like a browser in a frame: there's a window-sized splash screen…

I would be shocked if the new Outlook was Electron and not WebView2. Is there any confirmation on that or is Electron the new "Rollerblade" and "Band-aid" for wrappers?

Re: Microsoft is killing custom domain names in Outlook.com

#69

Post by system2 »

orev wrote: post #32
system2 wrote: post #23

Almost sounds like MS Exchange is being shut down. What is it exactly they are talking about?

Outlook.com webmail. But separately, MS is definitely killing on-prem Exchange as well. Maybe not today, but they have been very clear that they want everyone in their cloud.

To be honest I like MS Exchange without on-premise. Email depends on the internet anyway so there is no reason not to use a well maintained cloud service. Makes life easier for IT departments.

Re: Microsoft is killing custom domain names in Outlook.com

#70

Post by skinnymuch »

thiht wrote: post #61
bluesign wrote: post #44

Earlier quoted context omitted.

Lack of catch all there seems to be a blocker for many including me

It supports it since iOS 15 if I’m not mistaken (last year release) This is probably the best dollar I spend every month

Email isn’t done on the OS though. A server is doing it. Is there a reason Apple hides this behind an iOS version?
Post reply on HN