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

91–100 of 145 posts

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

#91

Post by kazinator »

AceJohnny2 wrote: post #85

Tangentially, 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. Ho…

> This breaks SPF

The way to do this forwarding would be to remail it in the same way that mailing lists do, rather than a SMTP forward.

The sender (SMTP envelope sender) gets rewritten, and so SPF is good. The From: header stays the same. SPF doesn't care about the From: header, only the SMTP envelope sender.

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

#92

Post by Scharkenberg »

svnpenn wrote: post #88
Destitute wrote: post #67

Earlier quoted context omitted.

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

> WebView2 you realize thats just another Chrome shit-client right?

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.

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

#94

Post by myle »

kazinator wrote: post #91
AceJohnny2 wrote: post #85

Tangentially, 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. Ho…

> This breaks SPF The way to do this forwarding would be to remail it in the same way that mailing lists do, rather than a SMTP forward. The sender (SMTP envelope sender) gets rewritten, and so SPF is good. The From: header stays the same. SPF doesn't care about the From: header, only the SMTP envelope sender.

How do I do that in Gmail?

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

#95

Post by inanutshellus »

TL;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 signed up as a domain reseller at OpenSRS and pointed my domain's MX entries over to them and... that was it. Super easy.

This gets me a mailbox for $0.50 per 5gb per month. I have two real mailboxes, dozens of aliases spanning multiple domains, and an email forwarder (sending to certain addresses emails to both my wife and myself) for $1.10/mo.

The negatives:

  * I've been spoiled by gmail's search capabilities.
  * I'm not a domain expert and not a mail admin, so I worried I was going to mess it up. I didn't, it wasn't terribly painful, you can do it.
  * I was told they didn't support plus addresses (jane+homedepot@example.com) so I purged my plus-address logins, only to find they really do support plus logins later.
On desktop I use a normal imap client (their web email is decidedly spartan) and on my phone I still use the GMail App.

The price beat the socks off of anyone else I had looked at and finally encouraged me to get off of GMail.

  * I'd been a "legacy" customer, and yes, they backtracked but by the time they *officially* agreed to keep supporting me I'd already needed to make a decision

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

#96

Post by AceJohnny2 »

myle wrote: post #94
kazinator wrote: post #91

Earlier quoted context omitted.

> This breaks SPF The way to do this forwarding would be to remail it in the same way that mailing lists do, rather than a SMTP forward. The sender (SMTP envelope sender) gets rewritten, and so SPF is good. The From: header stays the same. SPF doesn't care about the From: header, only the SMTP envelope sender.

How do I do that in Gmail?

not possible in gmail. It'd have to be done on the intermediary forwarding server.

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

#97

Post by throwawaaarrgh »

I've mostly stopped using free services wherever feasible. You get what you pay for.

The only free thing I really don't wanna give up is Google Photos. It's really convenient to just search "health insurance card" and the picture of my card pops up. Likewise for "apple pie", "sunset", "statue", etc.

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

#98

Post by tcbyrd »

Neil44 wrote: post #15

He says in 4 weeks but it's actually 1 year and 4 weeks. It was a PITA feature anyway for the family plans, requiring the domain be hosted on GoDaddy. I can't imagine it was a super popular feature.

There’s actually a trick where you don’t have to use Godaddy. I don’t know why they don’t open this up to users who want it. All you have to do is find the DNS challenge in the query param that’s passed to Godaddy. After that there’s no real persistent connection. Have been using a custom domain on the family plan for over a year this way, with my domain on Namecheap.

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

#99

Post by svnpenn »

Scharkenberg wrote: post #92
svnpenn wrote: post #88

Earlier quoted context omitted.

> WebView2 you realize thats just another Chrome shit-client right?

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.

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

#100

Post by drwl »

inanutshellus wrote: post #95

TL;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.…

Have you tried this? https://news.ycombinator.com/item?id=32793838#32797052
Post reply on HN