mass subscribers disablement!?
 
            I added the additional hosts to ALLOWED HOSTS in settings_local.py and mailman is distributing mail to subscribers again. However, I then received many emails of valid users subscriptions being disabled. What would cause that?
Can subscriber management be done via command line?
 
            On 10/22/21 2:07 PM, Christian Stalberg via Mailman-users wrote:
I added the additional hosts to ALLOWED HOSTS in settings_local.py and mailman is distributing mail to subscribers again. However, I then received many emails of valid users subscriptions being disabled. What would cause that?
Did you just upgrade Mailman core from a version <=3.3.0 to one >=3.3.1? If so, see https://lists.mailman3.org/archives/list/mailman-users(a)mailman3.org/thread...
Can subscriber management be done via command line?
See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/do... for description of the available mailman subcommands.
If you are interested in re-enabling delivery for members whose delivery
is disabled by bounce, you can do this fairly easily in an interactive
mailman shell session. See
https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/do...
Something like the following session:
$ bin/mailman shell
Welcome to the GNU Mailman shell
Use commit() to commit changes.
Use abort() to discard changes since the last commit.
Exit with ctrl+D does an implicit commit() but exit() does not.
 >>> lm = getUtility(IListManager)
 >>> for mlist in lm.mailing_lists:
...     for member in mlist.members.members:
...         if member.delivery_status == DeliveryStatus.by_bounces:
...             member.preferences.delivery_status = DeliveryStatus.enabled
...             print("Re-enabled delivery for bouncing member {} on list {}"
...                   .format(member.address.email, mlist.list_name))
...
<print output here>
 >>> commit()
 >>> exit()
-- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
 
            Yes I upgraded to a version >=3.3.1 and had 70 subscribers disabled. Is there a way to see via the web GUI which subscribers were disabled? Correspondingly, can I re-enable delivery for them via the web GUI?
Thank you in advance.
-----Original Message----- From: Mark Sapiro <mark@msapiro.net> Sent: Friday, October 22, 2021 5:51 PM To: mailman-users@mailman3.org Subject: [MM3-users] Re: mass subscribers disablement!?
On 10/22/21 2:07 PM, Christian Stalberg via Mailman-users wrote:
I added the additional hosts to ALLOWED HOSTS in settings_local.py and mailman is distributing mail to subscribers again. However, I then received many emails of valid users subscriptions being disabled. What would cause that?
Did you just upgrade Mailman core from a version <=3.3.0 to one >=3.3.1? If so, see https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/U 5ZW6X5QLQRXUOMD2DN77CYCOLKVMUXJ/
Can subscriber management be done via command line?
See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/do cs/commands.html for description of the available mailman subcommands.
If you are interested in re-enabling delivery for members whose delivery
is disabled by bounce, you can do this fairly easily in an interactive
mailman shell session. See
https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/do
cs/shell.html
Something like the following session:
$ bin/mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not.
lm = getUtility(IListManager) for mlist in lm.mailing_lists: ... for member in mlist.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... member.preferences.delivery_status = DeliveryStatus.enabled ... print('Re-enabled delivery for bouncing member {} on list {}' ... .format(member.address.email, mlist.list_name)) ... <print output here> commit() exit()
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
 
            On 10/26/21 5:14 AM, Christian Stalberg via Mailman-users wrote:
Yes I upgraded to a version >=3.3.1 and had 70 subscribers disabled. Is there a way to see via the web GUI which subscribers were disabled? Correspondingly, can I re-enable delivery for them via the web GUI?
Only one at a time. You could modify the shell session I posted previously to just display the members.
$ bin/mailman shell
Welcome to the GNU Mailman shell
Use commit() to commit changes.
Use abort() to discard changes since the last commit.
Exit with ctrl+D does an implicit commit() but exit() does not.
 >>> lm = getUtility(IListManager)
 >>> for mlist in lm.mailing_lists:
...     for member in mlist.members.members:
...         if member.delivery_status == DeliveryStatus.by_bounces:
...             print('Delivery disabled by bounce for member {} on list {}'
...                   .format(member.address.email, mlist.list_name))
...
<print output here>
 >>> exit()
Alternatively you can script some mailman commands as in
#!/bin/bash
for list in `bin/mailman lists|sed '1d'`; do
     echo $list
     bin/mailman members --nomail bybounces $list
done
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
 
            After the first time where users were unsubscribed automatically, I added back one at a time all the subscribers who were unsubscribed. Now they have all been unsubscribed again automatically. They are valid working email addresses. How can I stop this behavior from occurring please?
-----Original Message----- From: Mark Sapiro <mark@msapiro.net> Sent: Tuesday, October 26, 2021 11:03 AM To: mailman-users@mailman3.org Subject: [MM3-users] Re: mass subscribers disablement!?
On 10/26/21 5:14 AM, Christian Stalberg via Mailman-users wrote:
Yes I upgraded to a version >=3.3.1 and had 70 subscribers disabled. Is there a way to see via the web GUI which subscribers were disabled? Correspondingly, can I re-enable delivery for them via the web GUI?
Only one at a time. You could modify the shell session I posted previously to just display the members.
$ bin/mailman shell
Welcome to the GNU Mailman shell
Use commit() to commit changes.
Use abort() to discard changes since the last commit.
Exit with ctrl+D does an implicit commit() but exit() does not.
 >>> lm = getUtility(IListManager)
 >>> for mlist in lm.mailing_lists:
...     for member in mlist.members.members:
...         if member.delivery_status == DeliveryStatus.by_bounces:
...             print('Delivery disabled by bounce for member {} on list {}'
...                   .format(member.address.email, mlist.list_name))
...
<print output here>
 >>> exit()
Alternatively you can script some mailman commands as in #!/bin/bash for list in `bin/mailman lists|sed '1d'`; do      echo $list      bin/mailman members --nomail bybounces $list done
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
 
            On 11/26/21 9:39 AM, Christian Stalberg via Mailman-users wrote:
After the first time where users were unsubscribed automatically, I added back one at a time all the subscribers who were unsubscribed. Now they have all been unsubscribed again automatically. They are valid working email addresses. How can I stop this behavior from occurring please?
Do you have the bounce processing notifications Notify owner on  disable and Notify owner on removal set to Yes. If not, set them.
Then, what's in the notices you receive?
You might also consider setting verp_probes: yes in the [mta]
section of mailman.cfg. This will avoid some issues with users being
disabled/unsubscribed due to list posts being rejected as spam.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
- 
                 Christian Stalberg Christian Stalberg
- 
                 Mark Sapiro Mark Sapiro