AnonAddy VS Mailpile

With providers like Addy and SimpleLogin it is possible to use your own domain.

> https://addy.io/

This is one of a few reasons I have started to use email forwarders such as AnonAddy.

https://github.com/anonaddy/anonaddy

Not all of my emails have been moved over yet, but over time I plan on depreciating almost if not all of my main emails from logins.

For receive-only e-mails, take a look at addy.io as a free alternative to DDG. It's easier to manage with an account page listing every alias you create, with the option to block if required.

I use https://anonaddy.com/

My only complaint: 90% of the emails coming from AnonAddy, which is the alias service I use for all of my accounts, end up in the spam folder.

AnonAddy - https://github.com/anonaddy/anonaddy/blob/master/SELF-HOSTING.md OR SimpleLogin.io The real issue you are going to face is being able to receive emails on your server. If you are trying to do this at home, most home ISPs block incoming port 25. Even on most cloud providers you will face the same problem.

Anonaddy, basically the exact same product made by different people, can also be selfhosted. https://anonaddy.com/

Have a look at mailpile if you are after a web interface; or, the ever-dependable Thunderbird if you are fine with a desktop application.

mailpile seems good, but I would encripted things and besides this it is well mantained? The dockerfile here is old https://github.com/mailpile/Mailpile. By the way I tested a container, this rroemhild/mailpile, and it seems easy and with a good interface.

Mailpile supports theming. https://github.com/mailpile/Mailpile/wiki/Themes

Take a look at Mailpile.

Mailpile.is comes to mind. Their Twitter account is inactive since 2018, but they did fix some things on Github in November of 2020: https://github.com/mailpile/Mailpile/

> Email is not decentralized. It relies on the central authority of domain registries.

By that definition, almost every chat app is centralized, especially if you include the step of downloading it over HTTPS. In any case, it would be possible to further enhance email using something like SMTorP so that .onion addresses are used instead.[0]

> And then if you do decide that whatever encryption scheme you've chosen is right for you, there's no guarantee any significant mass of people supports it.

The same is true of any system which is proposed as an alternative to email. Admittedly it will be difficult for a UI to convey the security properties of messages when you are interacting with users whose email clients don't support the recommended extensions, but there is always the risk that a recipient will copy-paste the plaintext of your securely sent message into an unsecured channel.

[0] https://github.com/mailpile/Mailpile/wiki/SMTorP

For PC : Thunderbird or Mailpile