- Mailman-users - lists.mailman3.org

Moderation request email from a non existing user
by David Lopez June 1, 2022

June 1, 2022

Every day mailman (MM 3.3.3 (Tom Sawyer)) sends me an email with a held unsubcription request from X user. This user is not subcribed to that list anymore but every day an email is sending to the list owner. On the web interface there's nothing pending for approval or similar. Is there anyway to avoid receiving this anoyning email every day? Thanks in advance. David

2 3

hi, how to deal with arc with using mailman+exim4?
by 朱超 May 26, 2022

May 26, 2022

hi, how to deal with arc with using mailman+exim4? Thanks for your suggestion.

2 1

Trouble in Debian11 after import mailman2 archive
by qro＠xs4all.nl May 25, 2022

May 25, 2022

Hi I am struggling with Mainman3 to get it running on Debian11 On a clean VPS I have up and running Apache, mysql and postfix Also the installation mailman3 went fine for the mailman3-full package Then I setup mailman3-web via dpkg-reconfigure mailman3-web, modify in mailman-hyperkitty.cfg MAILMAN_ARCHIVER_KEY. In mailman.config add the [archiver.hyperkitty] things At this point I made a clone for the VPS. On clone 1 I import a mailman2 list: mailman create test(a)xxx.nl mailman import21 test@xxx /peter/mailman/lists/test/config.pck /usr/share/mailman3-web/manage.py hyperkitty_import -l test(a)xxx.nl /peter/mailman/archives/private/test.mbox/test.mbox /usr/share/mailman3-web/manage.py update_index So far so good. I can access the list and its config via the web page,see 1 subscriber (me :-) and can walk though the archive. But when I send an email to the list, its not resend or archived A snip from log files: /var/log/mail.log May 22 20:03:36 server postfix/smtpd[1614]: connect from ewsoutbound.kpnmail.nl[195.121.94.170] May 22 20:03:36 server postfix/smtpd[1614]: 8ECFF80BF9: client=ewsoutbound.kpnmail.nl[195.121.94.170] May 22 20:03:36 server postfix/cleanup[1616]: 8ECFF80BF9: message-id=<d89bf2f7-1519-9e0a-eb41-9211ff6f6a24(a)xs4all.nl> May 22 20:03:36 server postfix/qmgr[1510]: 8ECFF80BF9: from=<peter(a)xxxl.nl>, size=23317, nrcpt=1 (queue active) May 22 20:03:36 server postfix/smtpd[1614]: disconnect from ewsoutbound.kpnmail.nl[195.121.94.170] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 May 22 20:03:36 server postfix/lmtp[1630]: 8ECFF80BF9: to=<test(a)xxx.net>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.23, delays=0.15/0.01/0/0.07, dsn=2.0.0, status=sent (250 Ok) May 22 20:03:36 server postfix/qmgr[1510]: 8ECFF80BF9: removed /var/log/mailman3/smtp.log May 22 20:03:36 2022 (1359) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) May 22 20:03:36 2022 (1359) Peer: ('127.0.0.1', 46148) May 22 20:03:36 2022 (1359) ('127.0.0.1', 46148) handling connection May 22 20:03:36 2022 (1359) ('127.0.0.1', 46148) Data: b'LHLO server.xxx.net' May 22 20:03:36 2022 (1359) ('127.0.0.1', 46148) Data: b'MAIL FROM:<peter(a)xxx.nl>' May 22 20:03:36 2022 (1359) ('127.0.0.1', 46148) sender: peter(a)xxx.nl May 22 20:03:36 2022 (1359) ('127.0.0.1', 46148) Data: b'RCPT TO:<test(a)xxx.net>' May 22 20:03:36 2022 (1359) ('127.0.0.1', 46148) recip: test(a)xxx.net May 22 20:03:36 2022 (1359) ('127.0.0.1', 46148) Data: b'DATA' May 22 20:03:36 2022 (1359) ('127.0.0.1', 46148) Data: b'QUIT' May 22 20:03:36 2022 (1359) ('127.0.0.1', 46148) connection lost May 22 20:03:36 2022 (1359) Connection lost during _handle_client() Second attempt. There are no changes in Postfix or Mailman3! On clone 2 I did create a new list via the webpage/mailman3 This list is working fine. Does resend the message and add it tot the archive. The difference in the log between an imported list an new created is below the ----------- line /var/log/mail.log May 25 08:22:50 server postfix/smtpd[1430]: connect from ewsoutbound.kpnmail.nl[195.121.94.168] May 25 08:22:50 server postfix/smtpd[1430]: 81A0FA0091: client=ewsoutbound.kpnmail.nl[195.121.94.168] May 25 08:22:50 server postfix/cleanup[1434]: 81A0FA0091: message-id=<7c7b1770-db6d-9fc8-5e84-d09315d31124(a)xs4all.nl> May 25 08:22:50 server postfix/qmgr[1355]: 81A0FA0091: from=<peter(a)xxx.nl>, size=6029, nrcpt=1 (queue active) May 25 08:22:50 server postfix/smtpd[1430]: disconnect from ewsoutbound.kpnmail.nl[195.121.94.168] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 May 25 08:22:50 server postfix/lmtp[1435]: 81A0FA0091: to=<test(a)xxx.net>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.18, delays=0.06/0.01/0/0.11, dsn=2.0.0, status=sent (250 Ok) May 25 08:22:50 server postfix/qmgr[1355]: 81A0FA0091: removed ------------- May 25 08:22:52 server postfix/smtpd[1430]: connect from localhost[127.0.0.1] May 25 08:22:52 server postfix/smtpd[1430]: ACE58A0091: client=localhost[127.0.0.1] May 25 08:22:52 server postfix/cleanup[1434]: ACE58A0091: message-id=<7c7b1770-db6d-9fc8-5e84-d09315d31124(a)xs4all.nl> May 25 08:22:52 server postfix/qmgr[1355]: ACE58A0091: from=<test-bounces(a)xxx.net>, size=7804, nrcpt=1 (queue active) May 25 08:22:52 server postfix/smtpd[1430]: disconnect from localhost[127.0.0.1] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 May 25 08:22:53 server postfix/smtp[1437]: ACE58A0091: to=<peter(a)xxx.nl>, relay=mx.kpnmail.nl[195.121.65.158]:25, delay=0.33, delays=0/0.01/0.2/0.12, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as de93fca3-dc03-11ec-bee3-005056998415) May 25 08:22:53 server postfix/qmgr[1355]: ACE58A0091: removed /var/log/mailman3/smtp.log May 25 08:22:50 2022 (1361) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) May 25 08:22:50 2022 (1361) Peer: ('127.0.0.1', 54298) May 25 08:22:50 2022 (1361) ('127.0.0.1', 54298) handling connection May 25 08:22:50 2022 (1361) ('127.0.0.1', 54298) Data: b'LHLO server.xxx.net' May 25 08:22:50 2022 (1361) ('127.0.0.1', 54298) Data: b'MAIL FROM:<peter(a)xxx.nl>' May 25 08:22:50 2022 (1361) ('127.0.0.1', 54298) sender: peter(a)xxx.nl May 25 08:22:50 2022 (1361) ('127.0.0.1', 54298) Data: b'RCPT TO:<test(a)xxx.net>' May 25 08:22:50 2022 (1361) ('127.0.0.1', 54298) recip: test(a)xxx.net May 25 08:22:50 2022 (1361) ('127.0.0.1', 54298) Data: b'DATA' May 25 08:22:50 2022 (1361) ('127.0.0.1', 54298) Data: b'QUIT' May 25 08:22:50 2022 (1361) ('127.0.0.1', 54298) connection lost May 25 08:22:50 2022 (1361) Connection lost during _handle_client() ------------------- May 25 08:22:52 2022 (1363) <7c7b1770-db6d-9fc8-5e84-d09315d31124(a)xs4all.nl> smtp to test(a)xxx.net for 1 recips, completed in 0.0590972900390625 seconds May 25 08:22:52 2022 (1363) <7c7b1770-db6d-9fc8-5e84-d09315d31124(a)xs4all.nl> post to test(a)xxx.net from peter(a)xxx.nl, 6199 bytes Question: Where do I have to look/make changes so I can import the old archive and can send email to it? Greetings Peter

2 1

How to authorise members visibility?
by Pierre Malard May 25, 2022

May 25, 2022

Hello, My setup: - Debian 11 - Mailman3-full v 3.3.3-1 My Question: How to configure the visibility of a list of subscribers to a list? I created a list and set "subscriber visibility" to subscribers only. When I log in as such and try to view the list information, I can't see anywhere how to display that list. It's the same regardless of the setting used for this "subscriber visibility" field (only moderators, only subscribers or anyone). Is this normal? Is there something I misunderstood? Thank you in advance for your lights -- Pierre Malard Responsable architectures système CDS DINAMIS/THEIA Montpellier IRD - UMR Espace-Dev - UAR CPST - IR Data-Terra Maison de la Télédétection 500 rue Jean-François Breton 34093 Montpellier Cx 5 France « 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.

2 1

How to stop minutely mails about readme_renderer
by Axel Rau May 22, 2022

May 22, 2022

Hi all, after fixing an exim issue (now getting cron messages), I’m spammed by these e-mails: - - - /usr/local/py_venv/mailman_33/lib/python3.9/site-packages/readme_renderer/markdown.py:44: UserWarning: Markdown renderers are not available. Install 'readme_renderer[md]' to enable Markdown rendering. warnings.warn(_EXTRA_WARNING) - - - I installed cmarkgfm 0.8.0 in my venv, but this did not help. Besides patching the source, what is the recommended solution for this? Thanks, Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius

3 2

Importing users and mas settings "Moderation Action"
by bob B May 20, 2022

May 20, 2022

I imported email lists and users to version 3 from version 2. One of my lists all the users are set to 'Hold for moderation" for "Moderation Action". I assume this is because they were set to moderation on mailman 2? But if I mass subscribe users via the Gui in mailman 3 then their default "Moderation Action" is set to "none" so I assume it follows list default, is that a correct assumption? I believe there is no way to import mass users and set their "Moderation Action" at the same time is this correct? Wasn't that possible in mailman 2? is there a way to change all their user's "Moderation Action" for a list in bulk? So it looks like for any users I mass subscribe, "Moderation Action" will be set to "none" and if I want to change that I have to do it manually for each user?

2 2

Manage Member(s) Mailman Settings / Display Names
by Jim Ward May 18, 2022

May 18, 2022

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

best pratice - set default MM settings and make them update-save
by Stefan Bauer May 17, 2022

May 17, 2022

Dear mailman-experts, we're running Mailman Core Version 3.3.5 Mailman Core API Version 3.1 Mailman Core Python Version 3.10.4 on Ubuntu 22 with a python venv. Until now, I modified several files manually to adjust mailmans behavior and have to check several boxes when new lists are created. Is this still the only way to go or are there ways i can make all this more update "save" and kind of default settings? a, I removed content of /opt/mailman/venv/lib/python3.10/site-packages/mailman/templates/de/list:member:generic:footer.txt b, I set ... in /opt/mailman/venv/lib/python3.10/site-packages/mailman/styles/base.py mlist.default_member_action = Action.discard mlist.default_nonmember_action = Action.discard mlist.subscription_policy = SubscriptionPolicy.moderate mlist.send_welcome_message = False mlist.archive_policy = ArchivePolicy.never c, I always have to check the follwing manually in mailman web-interface on new lists: Settings-->List Idendity -> remove Subject Prefix Settings-->Message Acceptance -> accept immediately DMARC-Mitigation -> replace from ... unconditionally YES Thank you. Stefan

3 5

Upgrade-path from Ubuntu18LTS to recent mailman release
by Stefan Bauer May 15, 2022

May 15, 2022

Dear Users, we are very happy mailman3-users but suffer from very old packages in Ubuntu 18LTS. Unfortunately due to some python-restrictions¹, mailman3 is broken in Ubuntu20LTS and gone² in Ubuntu 22LTS, so we do not have any working upgrade-path :/ What do you recommend? Any help is greatly appreciated. thanks in advance. Stefan ¹ https://bugs.launchpad.net/ubuntu/+source/mailman3/+bug/1877701 ² https://packages.ubuntu.com/search?keywords=mailman3-full

5 10

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

May 11, 2022

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