Not a single mail was sent - I am migrating (and newly setting up from textfiles) the mailman3 suite, installed fresh from the scratch in (venv) in /opt/mailman.
I noticed that after having used a mix of addmember and also syncmember, one (or yesterday about 100 entries) of 500 had the MIME-coding. Then I used a script to remove users with the "=?UTF...." begin. In postorius users the user was gone and also in the lists where this user was in.
def delete_users(): url = f"{API_URL}/users" r = requests.get(f'{url}', auth = AUTH) r.raise_for_status() users = r.json()['entries']
for user in users:
dn = user.get('display_name')
if type(dn) == type("string") and dn.startswith("="):
print (dn)
self_link = user.get('self_link')
requests.delete(self_link, auth=AUTH)def main(): delete_users()
After a new add/syncmember, that spooky entry was up again!
Then I used mailman delmembers --fromall --no-goodbye-msg --no-admin-notify -m <this@address>: Then after a new add/syncmember, that entry was gone and the correct entry was shown.
That means, that somewhere some remains were stored somewhere. I also have a another issue, where I cannot get rid of a test display_name like "1111 [äöo]" <myemailaddress> for my own user entry (this issue has not yet been filed, as I do not want to flood you here; the "=?utf.." issue seems to be a more apparent problem).
At the moment, none of the ~500 users have "utf" searchable, which is some good news.
Perhaps to mention: I noticed the utf-problems when I used Ctrl-C during heavy script actions while add/syncing the lists which I needed to stop. while testing.
Perhaps this caused an inconsistent database state??? and that present issue was a consequence of my harsh break?