Nice! I also plan to add random word aliases soon e.g. yellow.biker57@anonaddy.me 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.

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?

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.

Do you support sending to email address with raw IP address or .onion domain as the domain part? Eg:

  test@192.0.2.4
  test@[2001:0DB8::0004] # or possibly
  test@2001.0DB8..0004
  test@l5satjgud6gucryazcyvyvhuxhr74u6ygigiuyixe3a6ysis67ororad.onion

Not at the moment I'm afraid. It would be cool to set up an .onion address, I'll have to look into this.

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 mymail@gmail.com. So in this case, spammer@spam.com goes to mymail@gmail.com.

- You then would have another email, realmail@mail.com that would receive email from mymail@gmail.com (you would set up the forward in Google).

- However, mymail@gmail.com would actually send to mailproxy@proxy.com, which would decrypt and forward to realmail@mail.com

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

Surely against MailGun TOS?

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.