Hi all, creator here. I've been working on AnonAddy (short for anonymous email address) for the past few months with the vision of creating a privacy friendly,

Hi all, creator here. I've been working on AnonAddy (short for anonymous email address) for the past few months with the vision of creating a privacy friendly, transparent and easy to use email forwarding service. The web app is built using Laravel, Vue.js and Tailwind CSS. Source code is available on GitHub[1], also mirrored on Gitlab[2]. The server is running Postfix, MariaDB, Nginx and Redis. I know that there are already a number of other services available that do a similar thing, but I wanted to address a few issues with them, such as: - Proprietary source code - Adverts, analytics and trackers used on the sites - No option to encrypt emails using a GPG/OpenPGP key - No option for multiple recipients - No API AnonAddy protects your real email address from spam and allows you to identify who has sold your data by using a different unique email address for every website. Here's a highlight of some of the features so far: - Add your own GPG/OpenPGP key per recipient to encrypt all forwarded emails - Custom domains - Anonymous email replies - UUID aliases that look like - 94960540-f914-42e0-9c50-6faa7a385384@anonaddy.me - Add multiple recipients per alias - Add additional usernames to compartmentalise your aliases - Browser extension for Firefox and Chrome - API New features are added regularly, here are some potential future features: - Tags/folders to help organise aliases - Random word aliases e.g. yellow.biker54@anonaddy.me - More brower extension functionality to manage existing aliases etc. - Send from aliases e.g. initiate email conversation - Send replies from custom domains as opposed to from an AnonAddy domain One of the most frustrating challenges was sorting out CORS issues with the API whilst building the browser extension. I noticed that only Firefox seemed to be enforcing the policy and not Chrome (Brave) which caused some confusion. In the end I looked at this awesome package by Spatie - laravel-cors[3] and was able to solve the issue. An important thing to note is that the Cors middleware needs to be included in Laravel's global middleware stack for it to work. I've learnt a lot about Postfix, DAME, DNSSEC etc. whilst building this but I'm always looking to improve things so I'd love to hear if you have any suggestions or feedback at all. Thanks, Will [1] https://github.com/anonaddy https://github.com/anonaddy [2] https://gitlab.com/anonaddy https://gitlab.com/anonaddy [3] https://github.com/spatie/laravel-cors https://github.com/spatie/laravel-cors