#reversealiases — Public Fediverse posts

A #privacy question about @simplelogin ... if I use #aliases and #ReverseAliases, the service is great but domains (even premium) are sometimes rejected because detected as "disposable".

So I use my own domain (let's call it dom.be) and I register it on #simplelogin. By doing that, I can enjoy #simplelogin service and not be seen as using a disposable mail service.

But then, my domain is "exposed": a malicious counterpart might decide to expose dom.be everywhere and start spamming stuff like "[email protected]", "[email protected]", etc?

Domain is registered under my name, so anonymity is lost too?

Am I going too far? Is there a best way to do this?

A #privacy question about @simplelogin ... if I use #aliases and #ReverseAliases, the service is great but domains (even premium) are sometimes rejected because detected as "disposable".

So I use my own domain (let's call it dom.be) and I register it on #simplelogin. By doing that, I can enjoy #simplelogin service and not be seen as using a disposable mail service.

But then, my domain is "exposed": a malicious counterpart might decide to expose dom.be everywhere and start spamming stuff like "[email protected]", "[email protected]", etc?

Domain is registered under my name, so anonymity is lost too?

Am I going too far? Is there a best way to do this?

A #privacy question about @simplelogin ... if I use #aliases and #ReverseAliases, the service is great but domains (even premium) are sometimes rejected because detected as "disposable".

So I use my own domain (let's call it dom.be) and I register it on #simplelogin. By doing that, I can enjoy #simplelogin service and not be seen as using a disposable mail service.

But then, my domain is "exposed": a malicious counterpart might decide to expose dom.be everywhere and start spamming stuff like "[email protected]", "[email protected]", etc?

Domain is registered under my name, so anonymity is lost too?

Am I going too far? Is there a best way to do this?

A #privacy question about @simplelogin ... if I use #aliases and #ReverseAliases, the service is great but domains (even premium) are sometimes rejected because detected as "disposable".

So I use my own domain (let's call it dom.be) and I register it on #simplelogin. By doing that, I can enjoy #simplelogin service and not be seen as using a disposable mail service.

But then, my domain is "exposed": a malicious counterpart might decide to expose dom.be everywhere and start spamming stuff like "[email protected]", "[email protected]", etc?

Domain is registered under my name, so anonymity is lost too?

Am I going too far? Is there a best way to do this?

A #privacy question about @simplelogin ... if I use #aliases and #ReverseAliases, the service is great but domains (even premium) are sometimes rejected because detected as "disposable".

So I use my own domain (let's call it dom.be) and I register it on #simplelogin. By doing that, I can enjoy #simplelogin service and not be seen as using a disposable mail service.

But then, my domain is "exposed": a malicious counterpart might decide to expose dom.be everywhere and start spamming stuff like "[email protected]", "[email protected]", etc?

Domain is registered under my name, so anonymity is lost too?

Am I going too far? Is there a best way to do this?