savannah-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Amin Bandali
Subject: Re: [sr #110479] Two different archives for the same mailing list
Date: Tue, 11 May 2021 23:46:49 -0400
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)

Hello Emre,

T. E. Kalayci writes:

> 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.

Thanks for further context around the issue.

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

That's beyond Savannah hackers' jurisdiction, and to my knowledge only
something FSF sysadmins (like Ian, Cc'd) can do.  I hope they can help.

If you don't hear from Ian, please email sysadmin@gnu.org with your
request.

> Sorry for any inconvenience.
>
> Best regards,
> Emre

Cheers,
amin



reply via email to

[Prev in Thread] Current Thread [Next in Thread]