I think this will have to be somewhat manual process. It does seem that each request can be approved in a new tab, so that should allow to run multiple requests in parallel.

@mreynolds I'll be processing them at your request, I just hope they are not all spam :-s

Note that the list is configured as: Confirm: Subscribers need to confirm the subscription using an email sent to them.

So I expect these pending subscription are folks who started but did not finish the process.

Even though I've already approved a number of requests, I feel like I should stop and wait for your feedback on whether you really want me to approve these requests (or, reject them).

Thanks!

Hi @pingou!

So I expect these pending subscription are folks who started but did not finish the process.

Maybe, but once I click confirm, that request disappears from the list. So it would appear to me that all these people are waiting on "us".

Now I did go through the list and removed a few suspicious email addresses, but the rest are not "obliviously" spam. So I would still like to approve all of them.

Now, a question I have is why have I never received any membership request notifications? I am an owner, but not the original Admin. So I don't know if that has to do with it, but is that something else you can look into, or should I file a new ticket for that?

Now I did go through the list and removed a few suspicious email addresses, but the rest are not "obliviously" spam. So I would still like to approve all of them.

Ok, going to do it :)

Now, a question I have is why have I never received any membership request notifications? I am an owner, but not the original Admin. So I don't know if that has to do with it, but is that something else you can look into, or should I file a new ticket for that?

One of our issue is that our mailman stack is really outdated at this point, so that may be a bug that has since been fixed. We hope to be able to upgrade it at some point, but there is really no ETA on this :(

Now I did go through the list and removed a few suspicious email addresses, but the rest are not "obliviously" spam. So I would still like to approve all of them.

Ok, going to do it :)

Thank you

Now, a question I have is why have I never received any membership request notifications? I am an owner, but not the original Admin. So I don't know if that has to do with it, but is that something else you can look into, or should I file a new ticket for that?

One of our issue is that our mailman stack is really outdated at this point, so that may be a bug that has since been fixed. We hope to be able to upgrade it at some point, but there is really no ETA on this :(

That's fine, I was just completely stunned when I just happened to check the subscription request and saw 1800 requests. Who knows how long ago these requests were made :-( Does not look good for our project, and here I thought no one was really interested in our project because of the lack of subscription requests. I will obviously be checking it regularly since I know I'm not getting notified.

I am pretty sure that these are (as @pingou said) addresses that asked to subscribe, mailman sent them a confirm email and they never confirmed.

But perhaps something was broken and mailman didn't send the confirm right? Or it was marked as spam or otherwise dropped?

I am pretty sure that these are (as @pingou said) addresses that asked to subscribe, mailman sent them a confirm email and they never confirmed.

Maybe? But in that case, why do I even need to confirm the requests? What is the purpose of the confirm button? If I do "confirm" it, the request goes away and is no longer visible. So from my POV, until I confirm, they can not get subscribed.

But you guys know all of this better than I do. I just want a clean list (389-ds-base has three lists (389-users, 389-announce, and 389-devel) , the other lists are empty. it's just 389-devel that has thousands of requests, and I don't want to continue to leave people hanging. If it can be ignored, then just empty that queue so I can catch new requests, but the way it looks to me is that these requests are waiting for "us". But hey, I'm not arguing :-) I just want to get it straightened out one way or another. Thanks!

Maybe? But in that case, why do I even need to confirm the requests? What is the purpose of the confirm button? If I do "confirm" it, the request goes away and is no longer visible. So from my POV, until I confirm, they can not get subscribed.

To allow you as list admin to bypass that requirement. ie, if a user contacted you and said they never got the confirm email, you could click that button and they would be subscribed without replying to the confirm email.

But you guys know all of this better than I do. I just want a clean list (389-ds-base has three lists (389-users, 389-announce, and 389-devel) , the other lists are empty. it's just 389-devel that has thousands of requests, and I don't want to continue to leave people hanging. If it can be ignored, then just empty that queue so I can catch new requests, but the way it looks to me is that these requests are waiting for "us". But hey, I'm not arguing :-) I just want to get it straightened out one way or another. Thanks!

I don't think there's any harm in accepting them... it could have been some bug or issue that dropped the requests at the time period when they were trying to subscribe.

Alright, the list is cleared.

To do this, after doing a lot of manual clicking I gave up and went the JS way.
So I have:
- Enable pop-up windows in firefox's preferences
- In firefox's about:config bump the configuration key: dom.popup_maximum from 20 to 200.
- Then on the page listing the subscription requests, I've ran this piece of JS:

$(document).find(".btn-success").each(function(idx, el){
  if ($(el).text() == 'Accept'){
    console.log(idx);
    if (idx < 150){
       window.opener = null;
       window.open($(el).attr('href'), '_blank');
    }
  }
});

I basically opened 150 tabs with an "Accept" request in each of them. Once all the tabs had returned (either successfully or not), I reloaded the list and re-ran the script.

It took a little while but it worked :)

Let us know if you need anything else :)

It took a little while but it worked :)

nice!

Let us know if you need anything else :)

Hopefully not! :) As always, great job guys!