llvm dev - Mar 2021 - IMPORTANT NOTICE - Subscription to Mailman lists disabled immediately

All,

We need to immediately disable subscription capabilities to all LLVM Mailman
lists.

The current Mailman server is being abused by subscribing valid email addresses
to our lists and because the list requires confirmation, the email address gets
“spam”. An email address is subscribed upwards of 100 times in a short period of
time in many cases. AWS has threatened to turn off our instance unless we take
immediate action. Given the time frame of the situation (24 hours to resolve),
we have no choice but to disable all new subscription capabilities as we can not
distinguish between a real subscription attempt versus the abuse.

Those currently subscribed should see no changes or impact to their workflow. 

I am sure this raises a lot of questions for the LLVM community and we are
working hard and as quickly as possible on a permanent solution to this
situation.

Thanks,
Tanya Lattner
LLVM Foundation

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20210305/e29f2689/attachment.html>

I've been informed by Etienne (on cc) that he made a request via the manual
"subscribe" e-mail address around a week ago now and has gotten no
response. I'm not sure if there are further steps he should be taking?

-- HT

On Fri, Mar 5, 2021 at 4:39 PM Tanya Lattner via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> All,
>
> We need to immediately disable subscription capabilities to all LLVM
> Mailman lists.
>
> The current Mailman server is being abused by subscribing valid email
> addresses to our lists and because the list requires confirmation, the
> email address gets “spam”. An email address is subscribed upwards of 100
> times in a short period of time in many cases. AWS has threatened to turn
> off our instance unless we take immediate action. Given the time frame of
> the situation (24 hours to resolve), we have no choice but to disable all
> new subscription capabilities as we can not distinguish between a real
> subscription attempt versus the abuse.
>
> Those currently subscribed should see no changes or impact to their
> workflow.
>
> I am sure this raises a lot of questions for the LLVM community and we are
> working hard and as quickly as possible on a permanent solution to this
> situation.
>
> Thanks,
> Tanya Lattner
> LLVM Foundation
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20210407/7fcd2de8/attachment.html>