News for hackers. Stuff that matters.
Re:Show HN: I made an open-source anonymous email forwarding... by Fabricio20 on Wednesday November 27, 2019 @11:37AM (#21649355)
Awesome idea!

I've been doing this exact same thing since march this year with my own domain using MailGun (Free) and custom forwarding rules.

Really amazing to see someone turn it into a product that can easily be set-up by the general folk. (And for a nice price!). Loved your UUID-alias idea.

May I ask however, how do you expect to handle a blacklist of your domains? I've had trouble in the past signing up to some websites that block any sort of custom domains (really bad) in an effort to block throw-away email, what happens if your domain gets blacklisted/categorized as a throwaway email? (Also forwarding to Google and such ends up in "email limbo").

Re:Show HN: I made an open-source anonymous email forwarding... by willbrowning on Wednesday November 27, 2019 @11:53AM (#21649515)
Nice! I also plan to add random word aliases soon e.g. [email protected] etc. just because some people think UUID aliases stick out a bit and look odd.

To be honest the only true solution to that problem is to use your own domain. I will be adding more generic domains to use in the future so hopefully will be able to evade the majority of these blacklists.

Re:Show HN: I made an open-source anonymous email forwarding... by johnkarahalis on Wednesday November 27, 2019 @03:48PM (#21651947)
A friend of mine was considering building an anonymous forwarding service and ran into this same question. He also considered allowing custom domains, but if a custom domain is used, is it really anonymous? Couldn't services coordinate to realize that all email addresses under whatever.com are owned by the same person?
Re:Show HN: I made an open-source anonymous email forwarding... by willbrowning on Wednesday November 27, 2019 @04:05PM (#21652137)
Yes that's true you could be linked if using a custom domain and someone can determine that nobody else is sharing that domain with you.

That's why I added the additional username feature to compartmentalise aliases and also the UUID aliases.

The UUID aliases all share the same domain e.g anonaddy.me so it is not possible to link ownership of these to any particular user.

Re:Show HN: I made an open-source anonymous email forwarding... by a1369209993 on Wednesday November 27, 2019 @09:04PM (#21654065)
Do you support sending to email address with raw IP address or .onion domain as the domain part? Eg:

  [email protected]
  test@[2001:0DB8::0004] # or possibly
  [email protected]
  test@l5satjgud6gucryazcyvyvhuxhr74u6ygigiuyixe3a6ysis67ororad.onion
Re:Show HN: I made an open-source anonymous email forwarding... by willbrowning on Thursday November 28, 2019 @03:13AM (#21655505)
Not at the moment I'm afraid. It would be cool to set up an .onion address, I'll have to look into this.
Re:Show HN: I made an open-source anonymous email forwarding... by newfeatureok on Wednesday November 27, 2019 @11:43AM (#21649414)
It's pretty much impossible to avoid the issue you described.

When I did an MVP of something similar to this, I encountered the same solution. The only solution really is the following:

- Use a reliable email, e.g. mymail@gmail.

- Encrypt forwarded email and send to [email protected]. So in this case, [email protected] goes to [email protected].

- You then would have another email, [email protected] that would receive email from [email protected] (you would set up the forward in Google).

- However, [email protected] would actually send to [email protected], which would decrypt and forward to [email protected]

TLDR: You need to encrypt the emails, pass through a service that won't be blocked, forward and decrypt to target destination.

Re:Show HN: I made an open-source anonymous email forwarding... by dboreham on Wednesday November 27, 2019 @01:37PM (#21650604)
Surely against MailGun TOS?
Re:Show HN: I made an open-source anonymous email forwarding... by Fabricio20 on Thursday November 28, 2019 @05:57AM (#21656214)
Please explain me why? They got a permanently free plan, and they allow you to do a catch-all rule (it's an option in the dropdown!) for receiving emails.

You can then catch all for your domain and redirect to your inbox (or blacklist as needed and such).

It's literally a feature they provide.