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

Extend random alias generation for permanent alias #3892

Open
schemen opened this issue Dec 8, 2020 · 10 comments
Open

Extend random alias generation for permanent alias #3892

schemen opened this issue Dec 8, 2020 · 10 comments

Comments

@schemen
Copy link

schemen commented Dec 8, 2020

Summary

For privacy concerns it random aliases are great. "Sign in with Apple" already uses this system. Once a service is no longer needed and/or abuses the email you can delete the alias.

Currently, you can only create a time constrained alias. I would like the ability for a user to create permanent aliases (maybe also per domain or per user restrictions?) with a comment field to note what service this alias is being used for.

Motivation

This will improve privacy for a enduser and make it harder for data kraken like websites to milk email addresses.

@patschi
Copy link
Member

patschi commented Dec 8, 2020

Why not using Aliases in Mail Setup?
image

@schemen
Copy link
Author

schemen commented Dec 8, 2020

Endusers can't do them, so I thought why not expand the available enduser interface.
image

@patschi
Copy link
Member

patschi commented Dec 8, 2020

Ah, I see. Forgot that bit. Now it makes sense, thanks!

@schemen
Copy link
Author

schemen commented Apr 6, 2021

A push for visibility \o/ would still be great feature! I already deleted a forwarding email of a very spamy service that I created by hand :)

@schemen
Copy link
Author

schemen commented Jun 2, 2021

From discussions within the Telegram group:

  • The database entry for permanent aliases is already here as well as the infrastructure to serve them
  • It's mostly UI that needs to be done for them
  • Each user should be able to create a random alias (automatically generated) and add a optional comment to describe for what service it's being used
  • Optionally, a via admin defined and select privacy domain (for example @protect.mymail.io) where users can create the alias with. The options for a user can be a privacy alias with their standard domain or the privacy domain

@schemen
Copy link
Author

schemen commented Jun 8, 2021

Created https://github.com/schemen/privacycow as a CLI tool to cover the requirements here. Serving me as long as this is not implemented in the UI :)

Uses the Mailcow API.

@Gandalf1783
Copy link

Is there any update on this yet?
Bumping :)

@Handrail9
Copy link

I would also like this feature, a CLI tool is handy for myself but I'm actually extending my Email service to my family and would like them to utilize private emails as well :)

@andrebnc
Copy link

andrebnc commented Dec 9, 2023

I support this proposal.

@TruncatedDinoSour
Copy link
Contributor

it has been 4 years, still no progress lol

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

No branches or pull requests

6 participants