On 10/25/23 10:44 AM, Stephen J. Turnbull wrote:
Servizio Informatico U.I.C.I. Sezione territoriale di Brescia writes:
Wher I find the disabled user of a mailing list and wher I can reactivate them?
If you are the list owner or superuser, when you visit the list's information page there will be a horizontal menu across the top. One of the entries is Users. Click to open the dropdown menu and choose Members. There doesn't seem to be an explicit notation for disabled users, but if the entry in the far right column "bounce score" is None, the member may be disabled.
I don't think this is correct. Members with delivery disabled by bounce will normally show 0 rather than None for bounce score.
If you have shell access to the server as the Mailman user, you can run this shell interaction to find members with delivery disabled by bounce.
$ mm/bin/mailman shell -l test@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 test@example.com mailing list
>>> for member in m.members.members:
... if member.delivery_status == DeliveryStatus.by_bounces:
... print(member.address.email)
...
>>>
But the question is, why do you want to re-enable their delivery. Granted, there are situations such as a misconfigured MTA or not applying needed DMARC mitigations that could result in 'spurious' bounced deliveries, but normally bounce processing disables delivery, sends warnings to the bouncing address and ultimately unsubscribes them because the address it truly not deliverable.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan