3 ms·

Does anyone actually know why it is blocked? Because the article doesn't say.

ev1 4y ago
The error in Tutanota's screenshot implies that someone has added this domain as some form of AD or organisation instead of a personal email. It's not a "your domain is banned" message, it's a "contact your tutanota.com organisation's admin to have them create an enterprise 365 account for you"
Brian_K_White 4y ago
It's been described in some other articles. A random, unknown, probably unwitting customer of tutanota some time years ago used their tutanota email to sign up for azureAD, and MS basically granted ownership of the tutanota domain (for MS purposes) to that unknown rando who does not work for tutanota and does not own their dns domain or anything like that, they just had an email address that ended in tutanota.com or .io or whatever it was. It means that ever since then, no one else can sign up for teams (and presumably at least some other MS services) using any tutanota email address, because MS treats them all as "you have to see your company's IT dept for that" they're treating the domain like a private corporate domain like mycompany.com that only mycompany.com employees are allowed to use, instead of like aol.com that any rando can use. By rights, this should be trivial to fix. Tutanota should be able to go to MS and simply prove to someone at MS that they own tutanota.com (or whatever domain) and maybe show their business incorporation paperwork etc, and remove the bogus "account" as it was never a valid account in the first place. MS is simply not doing it, for no explicable reason. Basically it's MS's fault at both places, both the initial error having whatever swiss cheese vetting process to even allow a rando to register a domain they don't own, and now not having any way to correct that initial error either. Basically, can you imagine that this would all play out the same way if the initial bogus registrant had happened to use a hotmail address instead of some other? Cool I own hotmail.com now as far as MS is concerned, and if anyone wants to make an account for o365 or teams using a hotmail address, they all have to come see me! And if I'm no longer using my hotmail address and don't even know any of this is going on, oh well the entire world of hotmail users can just f-off I guess! Somehow, I just bet that could never happen in the first place because of course hotmail would already have been getting special handling since day one and could never be accidentally handed to anyone like that, and even if it ever did by some chance, I just somehow predict that MS would somehow be able to accomplish what they say is impossible to tutanota, and fix that shit, in about 8 seconds.

ev1 4y ago

The error in Tutanota's screenshot implies that someone has added this domain as some form of AD or organisation instead of a personal email. It's not a "your domain is banned" message, it's a "contact your tutanota.com organisation's admin to have them create an enterprise 365 account for you"

Brian_K_White 4y ago

It's been described in some other articles. A random, unknown, probably unwitting customer of tutanota some time years ago used their tutanota email to sign up for azureAD, and MS basically granted ownership of the tutanota domain (for MS purposes) to that unknown rando who does not work for tutanota and does not own their dns domain or anything like that, they just had an email address that ended in tutanota.com or .io or whatever it was. It means that ever since then, no one else can sign up for teams (and presumably at least some other MS services) using any tutanota email address, because MS treats them all as "you have to see your company's IT dept for that" they're treating the domain like a private corporate domain like mycompany.com that only mycompany.com employees are allowed to use, instead of like aol.com that any rando can use. By rights, this should be trivial to fix. Tutanota should be able to go to MS and simply prove to someone at MS that they own tutanota.com (or whatever domain) and maybe show their business incorporation paperwork etc, and remove the bogus "account" as it was never a valid account in the first place. MS is simply not doing it, for no explicable reason. Basically it's MS's fault at both places, both the initial error having whatever swiss cheese vetting process to even allow a rando to register a domain they don't own, and now not having any way to correct that initial error either. Basically, can you imagine that this would all play out the same way if the initial bogus registrant had happened to use a hotmail address instead of some other? Cool I own hotmail.com now as far as MS is concerned, and if anyone wants to make an account for o365 or teams using a hotmail address, they all have to come see me! And if I'm no longer using my hotmail address and don't even know any of this is going on, oh well the entire world of hotmail users can just f-off I guess! Somehow, I just bet that could never happen in the first place because of course hotmail would already have been getting special handling since day one and could never be accidentally handed to anyone like that, and even if it ever did by some chance, I just somehow predict that MS would somehow be able to accomplish what they say is impossible to tutanota, and fix that shit, in about 8 seconds.