[jira] Issue Comment Edited: (INFRA-1280) Provide email masking in public archives

["Paul Querna (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/INFRA-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558831#action_12558831 ] 

pquerna edited comment on INFRA-1280 at 1/14/08 3:07 PM:
-------------------------------------------------------------

We have changed slightly, we now mask addresses in the html archives, but display them in the raw mbox files and raw views of the messages.  This is all we are going to do, imo.

      was (Author: pquerna):
    We have changed slightly, we not mask addresses in the html archives, but display them in the raw mbox files and raw views of the messages.  This is all we are going to do, imo.
  
> Provide email masking in public archives
> ----------------------------------------
>
>                 Key: INFRA-1280
>                 URL: https://issues.apache.org/jira/browse/INFRA-1280
>             Project: Infrastructure
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: Mail Archives
>            Reporter: Ted Husted
>
> (From a discussion on the infrastructure mailing list)  
> Currently, we do not provide email masking through our mod_mbox archives for two reasons 
> 1. Email masking would substantially reduce the value of our archives. It would decrease our openness, which is a characteristic we guard.
> 2. Email masking is very hard to do properly. mod_mbox already does it some degree, but not for emails contained in the message text, nor for the "original version" links. We also have publicly accessible mbox files containing unmasked emails. Getting rid of all that (or masking it) would require substantial changes to our procedures and to mod_mbox.
> This issue has been much debated, and http://www.apache.org/foundation/public-archives.html details the current consensus. I believe that we should be moving in one of two directions. Either:
> 1. Trying to solve all the problems listed in 2 above, including captcha-protected access to original emails; or
> 2. Making sure that every place where we collect emails, there is a clear link to our archive policy. That would include email list subscription messages and bug database signups, at least.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.