Re: [sr #110479] Two different archives for the same mailing list

[T. E. Kalayci]

Hello Amin,

Problem was the following:


> At 30 April 2021, a member at www-tr communication list [1] had an incident, 
> they forwarded a welcome mail to the list itself [2]. And unfortunately 
> password is visible in this email. I asked the following questions to the 
> mailman@gnu.org regarding this incident:
>
> - Is it possible to delete this email [2] from list archive? (I currently 
> made the archive private)
>
> - Is it possible to hide such information in case of replied/forwarded? (I 
> put a warning to the beginning of e-mails containing passwords in the 
> templates)
>
> [1] > https://lists.gnu.org/mailman/listinfo/www-tr-comm
> [2] > https://lists.gnu.org/archive/html/www-tr-comm/2021-04/msg00012.html
>
I received a response suggesting that "just changing the password for that user 
and then the
mail being in the archive wouldn't hurt anything" (but without mentioning the 
possibility of deleting message). So, making the archive private was a 
temporary solution to give some time to the user in case that they are using 
the same password in other services. 

Now I changed the settings back to the public, is it possible merge private 
archive to the public archive?

Sorry for any inconvenience.

Best regards,
Emre


May 3, 2021, 21:17 by bandali@gnu.org:

> [ Cc'ing T. E. Kalayci ]
>
> Ian Kelling writes:
>
>> Ali Servet Donmez <INVALID.NOREPLY@gnu.org> writes:
>>
>>> Follow-up Comment #1, sr #110479 (project administration):
>>>
>>> Hmm, I believe this might be due to `archive_private` setting for that 
>>> mailing
>>> list… What do you think?
>>>
>>> _______________________________________________________
>>>
>>> Reply to this item at:
>>>
>>> <https://savannah.nongnu.org/support/?110479>
>>>
>>> _______________________________________________
>>> Message sent via Savannah
>>> https://savannah.nongnu.org/
>>>
>>
>> That makes sense to me. I would turn that setting off.
>>
>
> Context:
>
> https://lists.gnu.org/archive/html/mailman/2021-04/msg00009.html
>