On 3/28/23 04:00, Tibor Molnar wrote:
Mailman3 built from source using virtual environment. Version: GNU Mailman 3.3.8 (Tom Sawyer) Python 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] config file: /etc/mailman3/mailman.cfg
Issue: I have restored the database number of times recently and experienced that every time after restoration (an hour after) all members getting an email that they are unsubscribed due to bounces, however non of the users are actually unsubscribed from any lists. It looks like there are duplicates in database and all the duplicates are getting unsubscribed?
Bounces message: name@email.com unsubscribed from [listname] mailing list due to bounces
That's an admin notice, not a notice to the user.
Only restoring two files: mailman3 and mailman3web
Did anyone come acroos this behavior ?
This seems sort of like <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/U5ZW6X5QLQRXUOMD2DN77CYCOLKVMUXJ/>, but it doesn't seem like that would be the issue here.
It is not right that after restoring a database all 1000 user get an email that they are unsubscribed, but they are actually not. I may do something wrong during the restoring process. Please advise me.
The code that decides which users are to be removed is at <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/model/member.py#L275>
Somehow you must be restoring members whose delivery status is disabled by bounce and whose total_warnings_sent is >= the list's bounce_you_are_disabled_warnings.
What do you get from this query on the mailman3 database
SELECT email FROM member JOIN address ON address_id = address.id JOIN preferences ON member.preferences_id = preferences.id WHERE delivery_status = 3 AND total_warnings_sent > 0;
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan