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

Hide full email addresses in archives #621

Closed
SansPseudoFix opened this issue May 20, 2019 · 0 comments · Fixed by #627
Closed

Hide full email addresses in archives #621

SansPseudoFix opened this issue May 20, 2019 · 0 comments · Fixed by #627
Assignees
Labels
enhancement ready A PR is waiting to be merged. Close to be solved
Milestone

Comments

@SansPseudoFix
Copy link

Expected Behavior

Add possibility to hide email addresses in order to make archive public without exposing these sensitive informations.

Current Behavior

Currently, email addresses (and gecos) are displayed.

Possible Solution

Add possibility to only display gecos?

Context

You want to make discussion public but don't want to expose addresses.

ldidry added a commit to ldidry/sympa that referenced this issue May 24, 2019
…otection

This allows to make web archives public without fearing to leak users
email addresses.
@ldidry ldidry self-assigned this May 24, 2019
ldidry added a commit to ldidry/sympa that referenced this issue May 24, 2019
…otection

This allows to make web archives public without fearing to leak users
email addresses.
@ldidry ldidry added the ready A PR is waiting to be merged. Close to be solved label May 24, 2019
@ikedas ikedas added this to the 6.2.44 milestone May 27, 2019
ldidry added a commit to ldidry/sympa that referenced this issue May 27, 2019
ikedas added a commit that referenced this issue Jun 3, 2019
Fix #621 — Add a 'gecos' option to web_archive_spam_protection
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement ready A PR is waiting to be merged. Close to be solved
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants