I have Outlook Premium (in a family plan) with a custom domain and didn’t receive any such e-mail, either.
Microsoft is killing custom domain names in Outlook.com
131–140 of 145 posts
Re: Microsoft is killing custom domain names in Outlook.com
#132Earlier 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!
Re: Microsoft is killing custom domain names in Outlook.com
#133Earlier quoted context omitted.
I found Migadu through a HN post like this and can't recommend them enough. It feels like having my own mail server without the headaches. The pricing model works for me and I find the control panel really well laid out. I don't think I could return to an email provider that leases emails at my own domain back to me.
Wow, this is exactly what I'm looking for. How often do emails you send go to other people's spam? Do you know people with an outlook email?
Re: Microsoft is killing custom domain names in Outlook.com
#134Tangentially, 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…
@
v=spf1 a mx include:_spf.google.com include:_spf.mx.cloudflare.net ~all
_dmarc
v=DMARC1; p=none; rua=mailto:my@emai.com; aspf=r;
The way I have it set up is that cloudflare catches all my email and then routes it to my gmail account. My gmail then uses my email as a "send as" address. No DKIM record is needed because google is the one sending the emails with smtp, but dmarc and spf are needed either way.
Re: Microsoft is killing custom domain names in Outlook.com
#135Earlier quoted context omitted.
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.
There are around 15 people working in Tutanota, and without Electron they really can’t provide it for every platform.
Re: Microsoft is killing custom domain names in Outlook.com
#136Re: Microsoft is killing custom domain names in Outlook.com
#137TL;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
They also obfuscated the path to acknowledge you were a personal-domain user.
Obviously, they wanted everyone to just switch over to being a paying customer (which is shocking, I know, given that they're a business and all ;D).
I figured if I was going to pay, I may as well do some research.
I decided that, for my needs, the OpenSRS solution was a good fit and was a fraction of the price (~$1/mo vs ...$12ish/mo?).
IIRC, about two weeks before the cutoff they finally and made it official and you could sign up for the personal-use domain. By that time I'd already gone to the effort of finding a new solution and was annoyed at the obfuscation tactics, so I went ahead and moved.
... but I also clicked that box, so all I have to do is point my MX records back to google and I'd be back on the juice.
Re: Microsoft is killing custom domain names in Outlook.com
#138That'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
#139Earlier 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.
The main benefits are that the apps should be faster, smaller, and use less resources as they don't include the whole of Electron (Chrome) with each one. So ideally massively less resource usage as so much is shared.
Running VS Code and Teams at the same time, for instance, would ideally use around half of the resources (a naive guess but you see the point).
As you allude to, though, it relies on MS keeping it updated but I would hope they take that seriously as if it takes off then one late update leaves multiple apps vulnerable. It remains to be seen.