-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Comments
Ah, I see. Forgot that bit. Now it makes sense, thanks! |
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 :) |
From discussions within the Telegram group:
|
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. |
Is there any update on this yet? |
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 :) |
I support this proposal. |
it has been 4 years, still no progress lol |
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.
The text was updated successfully, but these errors were encountered: