HNHacker News
TopNewBestAskShowJobs

willbrowning

184 karma · joined November 3, 2018

Building things with Laravel, Vue and Tailwind!

Working on anonaddy.com

submissionscomments
willbrowning··on Show HN: I made an open-source anonymous email forwarding service
That's an interesting story and has some good points.

My main concern would be the fact that complete email solutions such as Tutanota, Posteo are very cheap at 1 euro a month or so.

So I'm not sure users who aren't as concerned about their privacy would think it was worth it for $4.99 per month+

I mean I could be completely wrong, just my thoughts from some of the feedback I've received so far.

willbrowning··on Show HN: I made an open-source anonymous email forwarding service
Amazing, thank you! I use it myself alongside Tutanota, great combination!
willbrowning··on Show HN: I made an open-source anonymous email forwarding service
Haha, awesome!
willbrowning··on Show HN: I made an open-source anonymous email forwarding service
Cheers! Nginx access and error logs are kept which do record IP addresses. Default log settings are used for Postfix. The logs are rotated daily using logrotate and retained for 7 days, old log files are deleted.

Log files are only ever used to diagnose any errors/bugs.

Emails received are not e2e encrypted unless they have already been encrypted before arriving to the server.

Users can add their own PGP key to the site for each of their recipients and then the server will encrypt all forwarded emails with it.

Emails received are immediately piped through to the Laravel application by Postfix.

willbrowning··on Show HN: I made an open-source anonymous email forwarding service
Thank you! The help centre is still a real work in progress, I have a load more help articles I need to add there.

I based the help centre on Mullvad's as I really love how simple and easy to navigate their website is!

willbrowning··on Show HN: I made an open-source anonymous email forwarding service
Thanks, to be honest the expenses for the service are quite low. It is just the server and domain costs at the moment and of course my time.

You're right as it scales I may need to upgrade the server etc. but I think it will cover its expenses quite easily.

willbrowning··on Show HN: I made an open-source anonymous email forwarding service
Awesome, thanks!

I did start the service with just the Pro plan at $36 per year or $4 per month.

I received quite a lot of feedback from users asking for a cheaper plan that would allow 1 custom domain etc. which is why I eventually added the Lite plan.

As long as it makes enough to pay for itself I'll be happy as I made it to solve a problem for myself initially.

willbrowning··on Show HN: I made an open-source anonymous email forwarding service
Thanks a lot! I've tried to be as transparent as possible along the way.

That would be great, it is valid until midnight this Friday PST. The coupon code is BLACKFRIDAY50

willbrowning··on Show HN: I made an open-source anonymous email forwarding service
Thank you very much.

When you create an account there is a page called domains, it provides instructions on how to add the correct MX record to your custom domain in order to allow the server to handle inbound emails.

willbrowning··on Show HN: I made an open-source anonymous email forwarding service
Each time a new email is received Postfix calculates its size in bytes. A column in the database is then simply incremented by that size when the email is forwarded or a reply is sent. At the start of each month your bandwidth is reset to 0.

Yes the size does include images and attachments.

willbrowning··on Show HN: I made an open-source anonymous email forwarding service
Thank you! I've got a long to do list with more to come.
willbrowning··on Show HN: I made an open-source anonymous email forwarding service
That's a fair point. I've already added an additional domain to the site and will add more that look "generic" soon too.
willbrowning··on Show HN: I made an open-source anonymous email forwarding service
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

[2] https://gitlab.com/anonaddy

[3] https://github.com/spatie/laravel-cors

← PreviousPage 2 of 2