April 2022 - Mailman-users - lists.mailman3.org

Remove old bounces in bouncedir
by Stephan Krinetzki 07 Jun '22

07 Jun '22

Hello all, our Mailman3 has over 7GB of bounces in its bouncedir. I noticed that some messages there are already over 3 years old. Now my question: Is there a way to remove the old bounces?

2 6

Manage Member(s) Mailman Settings / Display Names
by Jim Ward 18 May '22

18 May '22

Mailman2 allowed me to list my members and modify a number of their attributes (display_name, etc) Postorius is a beautiful interface BUT I am evidently not finding how to manage my members to the extent that I could in Mailman2 Am I missing something?

4 7

Can login at /admin, but cannot login at the account/login page.
by pabsta＠gmail.com 11 May '22

11 May '22

Hi All, thanks for your contibution to opensource softwares. I have done the installation walkthrough on the wiki page (thanks to Brian Carpenter) and I am almost there. I can run the three services and they provide the relevant web interfaces (admin, postorius, hyperkitty). In comparison to the walkthrough, I did two changes; First, I used different port numbers , as it would otherwise conflict with other services on the server. Second, I disabled the social accounts authentification mechanisms. I am still running on sqllite, as I am still testing things (one task at a time). Using my "superuser" credentials, I can log to the admin section in a fraction of a second. The server response time is less than one second. Once logged in, I can navigate through all the site as an authenticated user, including in the postorius pages related to list management. The services work normally. However, if logout and attempt to login from the postorius website, I get a « 502 bad gateway » error after roughly 30 seconds. The logs in Systemctl for gunicorn register a "DIGEST-MD5 common mech free" error message and the nginx error logs just show a connection drop: 2021/08/12 18:11:09 [error] 26026#26026: *31 upstream prematurely closed connection while reading response header from upstream, client: [ip redacted], server: [domain redacted], request: "POST /accounts/login/ HTTP/2.0", upstream: "http://127.0.0.1:8006/accounts/login/", host: "[domain redacted]", referrer: "https://[domain redacted]/accounts/login/?next=/mailman3/lists/" Two additional clues may help understanding what is going on: 1- If I attempt to login with improper credentials, the services respond normally, and I get the expected red box with "invalid credentials" message on the postorius page. It is only when proper credentials are given that the connection fails. 2- If I attempt to register a new email adress, the services also fail to respond (although with no DIGEST-MD5 message registered). It thus seems to be a post "POST" problem, but what puzzles me is that it is not an issue for the admin page. Below the relevant sections of my settings.py page. The skipped ([...]) sections are as in the walkthrough files. In particular, the AUTH_PASSWORD_VALIDATORS, the EMAIL_BACKEND are as is and the "USE_X_FORWARDED_HOST" is still commented. ##Settings.py [...] # SECURITY WARNING: keep the secret key used in production secret! SECRET_KEY = '[redacted]' # SECURITY WARNING: don't run with debug turned on in production! DEBUG = False ADMINS = ( ('ME', 'my@email'), ) SITE_ID = 1 # Hosts/domain names that are valid for this site; required if DEBUG is False # See https://docs.djangoproject.com/en/1.8/ref/settings/#allowed-hosts ALLOWED_HOSTS = [ "localhost", # Archiving API from Mailman, keep it. "[domain]", # Add here all production URLs you may have. ] # Mailman API credentials MAILMAN_REST_API_URL = 'http://localhost:8005' MAILMAN_REST_API_USER = '[redacted]' MAILMAN_REST_API_PASS = '[redacted]' MAILMAN_ARCHIVER_KEY = '[redacted]' MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1') # Application definition INSTALLED_APPS = ( 'hyperkitty', 'postorius', 'django_mailman3', # Uncomment the next line to enable the admin: 'django.contrib.admin', # Uncomment the next line to enable admin documentation: # 'django.contrib.admindocs', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', #'django_mailman3.lib.auth.fedora', #'allauth.socialaccount.providers.openid', #'allauth.socialaccount.providers.github', #'allauth.socialaccount.providers.gitlab', #'allauth.socialaccount.providers.google', #'allauth.socialaccount.providers.facebook', #'allauth.socialaccount.providers.twitter', #'allauth.socialaccount.providers.stackexchange', ) [...] # Database # https://docs.djangoproject.com/en/1.8/ref/settings/#databases DATABASES = { 'default': { # Use 'sqlite3', 'postgresql_psycopg2', 'mysql', 'sqlite3' or 'oracle'. 'ENGINE': 'django.db.backends.sqlite3', # DB name or path to database file if using sqlite3. 'NAME': os.path.join(BASE_DIR, 'mailmansuite.db'), # The following settings are not used with sqlite3: 'USER': 'XXX', 'PASSWORD': 'XXX', # HOST: empty for localhost through domain sockets or '127.0.0.1' for # localhost through TCP. 'HOST': '', # PORT: set to empty string for default. 'PORT': '', # OPTIONS: for mysql engine only, do not use with other engines. # 'OPTIONS': {'charset': 'utf8mb4'} # Enable utf8 4-byte encodings. } } [...] # Password validation # https://docs.djangoproject.com/en/1.9/ref/settings/#auth-password-validators AUTH_PASSWORD_VALIDATORS = [ { 'NAME': 'django.contrib.auth.password_validation.UserAttributeSimilarityValidator', }, { 'NAME': 'django.contrib.auth.password_validation.MinimumLengthValidator', }, { 'NAME': 'django.contrib.auth.password_validation.CommonPasswordValidator', }, { 'NAME': 'django.contrib.auth.password_validation.NumericPasswordValidator', }, ] # Internationalization # https://docs.djangoproject.com/en/1.8/topics/i18n/ LANGUAGE_CODE = 'fr' TIME_ZONE = 'America/New_York' [...] # If you enable internal authentication, this is the address that the emails # will appear to be coming from. Make sure you set a valid domain name, # otherwise the emails may get rejected. # https://docs.djangoproject.com/en/1.8/ref/settings/#default-from-email # DEFAULT_FROM_EMAIL = "mailing-lists(a)you-domain.org" DEFAULT_FROM_EMAIL = 'username@domain' # If you enable email reporting for error messages, this is where those emails # will appear to be coming from. Make sure you set a valid domain name, # otherwise the emails may get rejected. # https://docs.djangoproject.com/en/1.8/ref/settings/#std:setting-SERVER_EMAIL # SERVER_EMAIL = 'root(a)your-domain.org' SERVER_EMAIL = 'username@domain' # Change this when you have a real email backend EMAIL_BACKEND = 'django.core.mail.backends.console.EmailBackend' [...] # # Social auth # AUTHENTICATION_BACKENDS = ( 'django.contrib.auth.backends.ModelBackend', 'allauth.account.auth_backends.AuthenticationBackend', ) # Django Allauth ACCOUNT_AUTHENTICATION_METHOD = "username_email" ACCOUNT_EMAIL_REQUIRED = True ACCOUNT_EMAIL_VERIFICATION = "mandatory" # You probably want https in production, but this is a dev setup file ACCOUNT_DEFAULT_HTTP_PROTOCOL = "https" ACCOUNT_UNIQUE_EMAIL = True # # Asynchronous tasks # Q_CLUSTER = { 'timeout': 300, 'save_limit': 100, 'retry':360, 'orm': 'default', } [...] # Only display mailing-lists from the same virtual host as the webserver FILTER_VHOST = True POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8006' ## (End of settings.py) I'm happy to provide additional information if it can help. Best, Pier-André

7 8

Templates do not work
by Eggert Ehmke 03 May '22

03 May '22

I created some templates in Postorius to get personalized notifications when there are moderator requests. The notifications I get seem to be the standard texts. When I look into mailman/ mm/var/templates the directory is empty. Nevertheless, the templates I create in Postorius seem to be stored (where?), they just do not work.

3 5

how to mass change users options ?
by Yvan ♞ 30 Apr '22

30 Apr '22

Hello, I transfered a mailing list from mailman to mailman 3, how can I change all users options in mass ? delivery status and receive own posting are blank by default (250 members is too long one by one..) Thanks. Yvan

2 1

Question to add "alias" address in list by group
by Pierre Malard 28 Apr '22

28 Apr '22

Everithing is in the subject. We must add some (a lot) alias address for members and I don’t find any indications on doc to do that with « mailman » command. Is their a way? -- Pierre Malard « Il faut créer en même temps les élites et les débouchés, le syndica- lisme et les usines. Faire l'un sans l'autre, c'est travailler pour le malheur du peuple. » Romain Gary - "Les racines du ciel" |\ _,,,---,,_ /,`.-'`' -. ;-;;,_ |,4- ) )-,_. ,\ ( `'-' '---''(_/--' `-'\_) πr perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-. ;-;;,_: |,A- ) )-,_. ,\ ( `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"' `-'"'"'\_): 24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print' - --> Ce message n’engage que son auteur <-- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

3 3

Localization of auto-responses, question marks in welcome message
by Claus-Justus Heine 25 Apr '22

25 Apr '22

Hi, I know there are already some posts on this subject. From reading the following seems to be the state of the affair: * the list's language settings determines which localized template to use * the list-_servers_ default setting determines which language to use for the subject (so the subject's language is a "global" server configuration setting). Still, in my Ubuntu Impish Mailman 3.3.3 installation the welcome message is sent with charset us-ascii and contains question marks for any "special" -- i.e. non-ascii -- character. Can this be changed s.t. the welcome message is correctly displayed? Kind thanks Claus -- Claus-Justus Heine himself(a)claus-justus-heine.de http://www.claus-justus-heine.de/ Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de

3 6

Problems with shunted Mails
by Stephan Krinetzki 25 Apr '22

25 Apr '22

Hi all, we currently have a problem sending to an email list. The mailing list is an announcement list and is therefore moderated. The mail also arrives for moderation. However, when the mail is released, it is not delivered, but moved to the shunt queue. The error after an unshunt attempt in the log: Apr 19 12:31:43 2022 (17967) Uncaught runner exception: 'NoneType' object has no attribute 'email' Apr 19 12:31:43 2022 (17967) Traceback (most recent call last): File "/opt/mailman/mailman-venv/lib64/python3.6/site-packages/mailman/core/runner.py", line 176, in _one_iteration self._process_one_file(msg, msgdata) File "/opt/mailman/mailman-venv/lib64/python3.6/site-packages/mailman/core/runner.py", line 269, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/opt/mailman/mailman-venv/lib64/python3.6/site-packages/mailman/runners/pipeline.py", line 37, in _dispose process(mlist, msg, msgdata, pipeline) File "/opt/mailman/mailman-venv/lib64/python3.6/site-packages/mailman/core/pipelines.py", line 50, in process handler.process(mlist, msg, msgdata) File "/opt/mailman/mailman-venv/lib64/python3.6/site-packages/mailman/handlers/member_recipients.py", line 84, in process for member in mlist.regular_members.members File "/opt/mailman/mailman-venv/lib64/python3.6/site-packages/mailman/handlers/member_recipients.py", line 85, in <genexpr> if member.delivery_status == DeliveryStatus.enabled) AttributeError: 'NoneType' object has no attribute 'email' Apr 19 12:31:43 2022 (17967) SHUNTING: 1650364303.8361175+08bb48ae877019e8a4c9dff8024c1270782fceb3 Any hints how we can solve the problem here?

2 4

set a new default for max_message_size
by Paul Paulchen 24 Apr '22

24 Apr '22

Hi MM Community, I guess Mark can answer this question in a split second. We want another default than 40kb for the max_message_size. I know you can change it with the mailman shell or with postorius. But we want to skip this part an set the default to 4000kb for instance. I read about the max_message_size in this thread from 2020 https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… According to the answer of Mark you can change the "/usr/lib/python3/dist-packages/mailman/styles/base.py" - mlist.max_message_size. Now time went by, is there a possibility to use the mailman.cfg to set a new default? Cheers and thanks in advance!

3 2

How to delete large numbers of held messages
by lists＠g1fef.co.uk 22 Apr '22

22 Apr '22

We had a mail loop on one of our lists and ended up with over 51k messages in pending (held due to post not form a list member) Trying to delete them from the web UI will take forever, as the largest pagination you can view is 200 at a time. Tried to delete them from the Python interactive shell, but it looks like the API times out after a while. Is there another way to delete all these unwanted held posts? The problem comes after executing: <block> reqs = list(adminlist.held) </block> After a couple of minutes it comes back with: <block> Traceback (most recent call last): File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 699, in urlopen httplib_response = self._make_request( File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 445, in _make_request six.raise_from(e, None) File "<string>", line 3, in raise_from File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 440, in _make_request httplib_response = conn.getresponse() File "/usr/lib/python3.9/http/client.py", line 1347, in getresponse response.begin() File "/usr/lib/python3.9/http/client.py", line 307, in begin version, status, reason = self._read_status() File "/usr/lib/python3.9/http/client.py", line 276, in _read_status raise RemoteDisconnected("Remote end closed connection without" http.client.RemoteDisconnected: Remote end closed connection without response During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439, in send resp = conn.urlopen( File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 755, in urlopen retries = retries.increment( File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 532, in increment raise six.reraise(type(error), error, _stacktrace) File "/usr/lib/python3/dist-packages/six.py", line 718, in reraise raise value.with_traceback(tb) File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 699, in urlopen httplib_response = self._make_request( File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 445, in _make_request six.raise_from(e, None) File "<string>", line 3, in raise_from File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 440, in _make_request httplib_response = conn.getresponse() File "/usr/lib/python3.9/http/client.py", line 1347, in getresponse response.begin() File "/usr/lib/python3.9/http/client.py", line 307, in begin version, status, reason = self._read_status() File "/usr/lib/python3.9/http/client.py", line 276, in _read_status raise RemoteDisconnected("Remote end closed connection without" urllib3.exceptions.ProtocolError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 107, in call response = request( File "/usr/lib/python3/dist-packages/requests/api.py", line 61, in request return session.request(method=method, url=url, **kwargs) File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542, in request resp = self.send(prep, **send_kwargs) File "/usr/lib/python3/dist-packages/requests/sessions.py", line 655, in send r = adapter.send(request, **kwargs) File "/usr/lib/python3/dist-packages/requests/adapters.py", line 498, in send raise ConnectionError(err, request=request) requests.exceptions.ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "<console>", line 1, in <module> File "/usr/lib/python3/dist-packages/mailmanclient/restobjects/mailinglist.py", line 123, in held response, content = self._connection.call( File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 135, in call raise MailmanConnectionError( mailmanclient.restbase.connection.MailmanConnectionError: ('Could not connect to Mailman API: ', "ConnectionError(ProtocolError('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')))") </block>

2 4