Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Anonymous Email Forwarding #2338

Open
sarahspock opened this issue Dec 1, 2023 · 3 comments
Open

Feature Request: Anonymous Email Forwarding #2338

sarahspock opened this issue Dec 1, 2023 · 3 comments

Comments

@sarahspock
Copy link

Hello,

There are some services (i.e. ProtonMail and Apple iCloud), that allow you to anonymize your real email address by creating a custom forwarder for each service. This is also helpful for spam purposes because you can turn off the email address receiving the spam. I would like to request the ability to add a bunch of your own domains easily to the system, and the creation of custom forwarders, so that data brokers cannot relate all of your services together using your email address.

Example:

  1. Service a:
    randomly_generated@yourcustomdomain.com -> realemail@yourmainemaildomain.com

  2. Service b:
    randomly_generated_2@anothercustomdomain.com -> realemail@yourmainemaildomain.com

I hope this makes sense.

@kiekerjan
Copy link
Contributor

I know this is not exactly what you describe, but technically mail in a box is already able to do this. You can create aliases on domain one which forwards to a mailbox on domain two.
What you might want to add is some automation to generate a random alias and manage those multiple randomized aliases.

@nomandera
Copy link
Contributor

I really like this idea. As @kiekerjan points out all of the framework for this already exists, it is really a matter of the front end.

However given that any MIAB domain can have a catchall address there is no actual reason the front end needs to be in MIAB itself unless the intention is to reject mail that does not match any account.

@myfirstnameispaul
Copy link
Contributor

myfirstnameispaul commented Feb 9, 2024

It seems all you are describing is aliasing, which is different from forwarding.

MiaB already supports aliasing including catchall and APIs, which are all explained on the Aliases page of the MiaB dashboard.

What MiaB does not support but seems reasonable to me is adding more than one email address in the Alias field of the Aliases page. That would be (I think) a relatively easy way to resolve this issue as users can easily create for themselves a list and paste it into the field.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants