"Unsubscribe all" failed with large lists
We are currently testing latest mailman suite (w/Postorius 1.3.3) and notice that that the the API call /3.1/lists/listname.domain/roster/member failed when using "Unsubscribe all" on Postorius for a large list (~15000 members). Not sure whether the issue has been already reported or not.
thanks, Abhilash Raj
On Wed, Jan 20, 2021 at 10:34, Alan So <ktso@cuhk.edu.hk> wrote:
We are currently testing latest mailman suite (w/Postorius 1.3.3) and notice that that the the API call /3.1/lists/listname.domain/roster/member failed when using "Unsubscribe all" on Postorius for a large list (~15000 members).
Not sure whether the issue has been already reported or not.
It has been reported before for sure, but I couldn't find an issue tracking it in Postorius' tracker so I created one1.
The Core and Mailmanclient already have a mass-unsubscribe API that doesn't require looping over all address and unsubscribing them one by one, it just needs to be plumbed through in P, in case someone wants to take a stab at it.
Mailman-users mailing list -- mailman-users@mailman3.org <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave@mailman3.org <mailto:mailman-users-leave@mailman3.org> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>
Thanks.
We are still using Postorius 1.2.4 and Mailman core 3.2.0. However, there is no such issue. Is this specific to Postorius 1.3.x or a result of using together with Mailman core 3.3.2? Postorius 1.2.4 is probably not using mass-unsubscribe API.
We are planning to upgrade Mailman core first to solve another issue and upgrade Postorius a bit later.
Alan So wrote:
Thanks. We are still using Postorius 1.2.4 and Mailman core 3.2.0. However, there is no such issue. Is this specific to Postorius 1.3.x or a result of using together with Mailman core 3.3.2? Postorius 1.2.4 is probably not using mass-unsubscribe API. We are planning to upgrade Mailman core first to solve another issue and upgrade Postorius a bit later.
Just figure out that our production environment with Mailman core 3.2.0 do reply with the API call /3.1/lists/listname.domain/roster/member even for long lists though it takes long time to complete. However, Mailman core 3.3.2 simply give empty reply with long lists after around a minute.
participants (2)
-
Abhilash Raj -
Alan So