Re-enable member after bouce processed disable
Recently I upgraded Mailman to GNU Mailman 3.3.4 (Tom Sawyer) (Postorius: 1.3.5 and HyperKitty: 1.3.4) which is now processing bounces.
When a member have been disabled due to bounces, how is the member re-enabled? I would guess it would be under the "Users -> Members -> Member options -> Delivery status", but theses are both (Enabled and disabled) unchecked, not indicating whether or not the member is either or.
How do I or the list admins re-enable a bounce-disabled member?
Regards, Henrik
On 12/9/21 6:07 AM, Henrik Rasmussen wrote:
Recently I upgraded Mailman to GNU Mailman 3.3.4 (Tom Sawyer) (Postorius: 1.3.5 and HyperKitty: 1.3.4) which is now processing bounces.
When a member have been disabled due to bounces, how is the member re-enabled? I would guess it would be under the "Users -> Members -> Member options -> Delivery status", but theses are both (Enabled and disabled) unchecked, not indicating whether or not the member is either or.
You are looking at the user's list based preferences. If one of these is unset, it falls back to address based preferences and from there to the user's global preferences. You can see all of these for yourself at the Mailman settings choice in the dropdown at your user name, but for another list member you only see the list based preferences.
How do I or the list admins re-enable a bounce-disabled member?
Just set the member's delivery status on the page you see to Enabled. Even though it was not previously shown as Disabled by Bounces, it will be enabled.
Likewise the member can set her Delivery status to Enabled.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Henrik Rasmussen wrote:
Recently I upgraded Mailman to GNU Mailman 3.3.4 (Tom Sawyer) (Postorius: 1.3.5 and HyperKitty: 1.3.4) which is now processing bounces. When a member have been disabled due to bounces, how is the member re-enabled? I would guess it would be under the "Users -> Members -> Member options -> Delivery status", but theses are both (Enabled and disabled) unchecked, not indicating whether or not the member is either or.
It seems that I was right, however, I need to re-enable all members on a single list who have been disabled due to bounces.
Using the mailman members command it is possible to list such members, however how do I enable them using either the mailman shell command (available) og the mailmanclient (needs first to be installed in the docker container)?
Regards, Henrik Rasmussen
On 1/5/22 12:48 AM, Henrik Rasmussen wrote:
It seems that I was right, however, I need to re-enable all members on a single list who have been disabled due to bounces.
Using the
mailman memberscommand it is possible to list such members, however how do I enable them using either themailman shellcommand (available) og the mailmanclient (needs first to be installed in the docker container)?
There is a mailman shell session in the post at
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
that will re-enable all bounce disabled members on all lists. To do just
a single list do something like
$ bin/mailman shell -l list.example.com
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.
The variable 'm' is the list.example.com mailing list
>>> for member in m.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
participants (2)
-
Henrik Rasmussen -
Mark Sapiro