- Mailman-users - lists.mailman3.org

Detectors and Bounces
by summersan＠nclack.k12.or.us 05 Aug '22

05 Aug '22

Hello All, I've recently upgraded a Mailman 3 server from Debian 10.12 to Debian 11.4 [1]. In that process, I've also upgraded Mailman 3 from version 3.3.4 to version 3.3.5. I think the following guide was originally used when setting up Mailman 3 on the present server: https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 . After that upgrade process, I've noticed that at least one `mailman` process and one `postgres` process were at something like 40 %CPU or higher for extended periods of time (seen using `top` command). Upon further inspection, and through some research online, it seemed like the issue might have to do with bounces (maybe not processing or something) [2][3][4][5][6][7][8]. In my logcheck logs, I was seeing this message multiple times a second: `Running detector: <class 'flufl.bounce._detectors.dsn.DSN'>` I ended up trying to clear out the `/opt/mailman/mm/var/queue/bounces` and `/opt/mailman/mm/var/locks` directories to see if that would help. There seemed to be some sort of positive change, because the log message "spamming" seemed to decrease. The high %CPU for the `mailman` and `postgres` processes in question also seemed to go down over time. But the related `mailman` process would still run at a high %CPU from time to time. I tried checking the `mailman` process using `strace` at some point, but I didn't see an easily evident cause for what was going on—from what I remember, there was something about a "POLLIN" or something that kept looping. When I go to check the same `mailman` process with `strace` today, I just see occasional messages like this: `select(0, NULL, NULL, NULL, {tv_sec=45, tv_usec=43171}) = 0 (Timeout)` My Questions: Is it normal to see large amounts of `Running detector: <class 'flufl.bounce._detectors.dsn.DSN'>` lines in logs? Should there normally be other detectors listed in the logs beyond the `DSN` one? If so, is there a setting I can change somewhere to make this happen? For reference, I can only find one other logcheck log that shows a `Running detector: <class 'flufl.bounce._detectors.dsn.DSN'>` line from before the recent Mailman 3 upgrade. In that past logcheck log, there are other detectors listed as well, which makes me wonder if something is still stuck with the new Mailman 3 install (or if maybe something needs to be changed in a setting file somewhere): Here is an example of previous log lines: Running detector: <class 'flufl.bounce._detectors.sina.Sina'> Running detector: <class 'flufl.bounce._detectors.llnl.LLNL'> Running detector: <class 'flufl.bounce._detectors.exim.Exim'> Running detector: <class 'flufl.bounce._detectors.qmail.Qmail'> Running detector: <class 'flufl.bounce._detectors.exchange.Exchange'> Running detector: <class 'flufl.bounce._detectors.netscape.Netscape'> Running detector: <class 'flufl.bounce._detectors.dsn.DSN'> Running detector: <class 'flufl.bounce._detectors.caiwireless.Caiwireless'> Running detector: <class 'flufl.bounce._detectors.aol.AOL'> Running detector: <class 'flufl.bounce._detectors.yale.Yale'> Running detector: <class 'flufl.bounce._detectors.smtp32.SMTP32'> Running detector: <class 'flufl.bounce._detectors.groupwise.GroupWise'> Running detector: <class 'flufl.bounce._detectors.simplewarning.SimpleWarning'> Running detector: <class 'flufl.bounce._detectors.microsoft.Microsoft'> Running detector: <class 'flufl.bounce._detectors.postfix.Postfix'> Running detector: <class 'flufl.bounce._detectors.simplematch.SimpleMatch'> Running detector: <class 'flufl.bounce._detectors.yahoo.Yahoo'> Thank you for your time, Andy ----- Web References: [1] https://www.debian.org/News/2022/2022032602 [2] https://mail.python.org/archives/list/mailman-developers@python.org/thread/… [3] https://phabricator.wikimedia.org/T282348 [4] https://mail.python.org/archives/list/mailman-users@python.org/thread/MISUM… [5] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… [6] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… [7] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… [8] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…

2 9

Rpsamd greylist configuration for Mailman3
by Prasanth Nair 03 Aug '22

03 Aug '22

Hello, I'm in the process of configuring Rspamd with the Mailman3 server. If Rspamd flags a message under 'greylist' and accepts it after the temporary rejection, is there any way mailman can move that message to the moderator's queue? if it is possible, can someone send me the instructions, please? Kind regards, Prasanth Nair

2 2

Mailman 3 questions (purge archives, list metrics, and auto discard held messages)
by bob B 02 Aug '22

02 Aug '22

Some quick mailman3 questions --Just wanted to check that there is still no way for mailman3 to automatically purge archived emails after a set amount of time? it looks like you have to export the database, purge the messages, then re-import, is this still the only/best way to purge old archived messages? --I noticed on the list info page you have metrics, which is straightforward except for "volume" My volume number is not increasing? What is that counting exactly? --Is there any way to auto discard held messages after x amount of time? I assume not but had a user ask if that was an option. Thanks for the assistance in advance.

3 4

Mailman 3 Consultant needed
by Mark Taylor 01 Aug '22

01 Aug '22

A customer we support wants to migrate a substantial Mailman 2 installation to Mailman 3. We have a team that can handle much, even perhaps most of this, but it’s an important project and we’d prefer to have a deep expert on the team for help/advice and the heavy lifting. Can anyone here recommend and engineer, perhaps even you, who could get involved with us commercially to help make a Mailman 2 to 3 migration successful? Thank you all, and I hope I’ve not violated any list guidelines by asking… You can contact me off-list if you prefer - I’m quite easy to find… Best regards to all, Mark Mark Taylor, Chief Executive Officer SiriUS: Infrastructure for Entrepreneurs® https://www.siriusopensource.com t: +001 509 254 5005

1 0

Programmatic Creation of Users
by jciesla＠techsupportme.com 30 Jul '22

30 Jul '22

I am returning to Mailman after being away for a LONG time and I need to create 40 lists with ~350 subscribers spread across those lists. After a lot of testing I am now able to create users from the Core Shell and set (most of) the necessary values. Having jumped that hurdle I have hit a roadblock and I am hoping that the list can provide some insight and/or solutions. After a lot of research I now understand that what I am doing in the Core Shell is creating a User entity which has one or more email addresses as well as one or more roles and preferences that exist at the global level. This user entity can Subscribe to zero or more lists. If I am incorrect in the summation please let me know! Assuming that the previous information is correct that brings us to my current dilemma. Specifically, the User entity can Subscribe and interact with lists using the email commands, but they can't Login using the Postorius web interface. If I understand correctly the reason that they can't login is that the underlying Django system does not recognize their account because the account that was created in Core isn't accessible by Django. Instead the user needs to create a Django-specific account at which point the information from Core becomes available in the user's web UI. If that is in fact accurate then I want to take the next logical leap: is it possible to programmatically create an account in Django that is tied to the account that was created in Core? Any information is greatly appreciated! -John

2 1

User display name entry field input ignored
by Christian 27 Jul '22

27 Jul '22

Whether I try and add users using mass subscribe, or individually, it seems the display name field entry is ignored. The default is then "none" for the user. Please advise. Thank you!

2 3

Shorted Subjects in Mailman
by Stephan Krinetzki 27 Jul '22

27 Jul '22

Hello all, We have been experiencing the following problem lately: When a user sends a mail with an unusually long subject to a mailing list, this subject is shortened. Here are the two examples: Original subject: "[SAV-LINUX] Notice from Sophos Anti-Virus on lx1bcms-storage.physik.rwth-aachen.de" (82 characters long) Subject in Mailman: "[edv-support][SAV-LINUX] Notice from Sophos Anti-Virus on" (57 characters long) Is there a rule that Mailman truncates the subject or why does this happen? Is there any way to work around this? In the Mailman Topic Header, however, the full subject is always readable. Translated with www.DeepL.com/Translator (free version)

4 13

Problem replying via Hyperkitty
by Jeff 27 Jul '22

27 Jul '22

Hello Everyone, A few of my users read our mailing list through Hyperkitty. Whenever they reply through the web, their replies simply disappear. One example from today was logged as follows: [pid: 2287|app: 0|req: 116007/153551] xxx.xx.xx.xx () {72 vars in 1992 bytes} [Thu Jun 30 11:26:16 2022] POST /archives/list/listname(a)domainname.org/message/46WUOPZITVMKJN4TXR6CP3WMFUEAVJKD/reply => generated 3213 bytes in 70 msecs (HTTP/1.1 200) 6 headers in 188 bytes (3 switches on core 0) A couple of basic questions: 1) when a users replies in this manner, does their response go to the list or to the subscriber to whom they are replying? 2) what log files could I check to see what — if anything — happens to these emails? 3) Are there any settings that need to be set to make this work? Thanks much. Any help will be appreciated. Jeff

2 3

Apache Configuration for Subdomain
by Mail Person 26 Jul '22

26 Jul '22

I'm trying to move my mailman3 web interface from example.com/mailman3 to just lists.example.com like this site. I am not having luck with the apache configuration. I've tried below but I just get a 403: <VirtualHost *:80> ServerAdmin admin(a)example.com ServerName lists.example.com ServerAlias www.lists.example.com <Directory "/var/lib/mailman3/web/static"> Require all granted </Directory> <IfModule mod_proxy_uwsgi.c> ProxyPass /favicon.ico ! ProxyPass /static ! ProxyPass / unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost </IfModule> </VirtualHost> Alias /favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico Alias /static /var/lib/mailman3/web/static

3 9

Apache Conf
by Guiseppin Thomas 26 Jul '22

26 Jul '22

Hi, Currently, I use a nginx configuration for mailman. It's work perfectly. I tried to do the same with Apache, but the statics files are not delivered (404). Basically, it's the same configuration: /server { listen 80; server_name mailing.ddd.fr; access_log /var/log/nginx/mailing.access.log; error_log /var/log/nginx/mailing.error.log; location /static/ { alias /opt/mailman/static/; expires 30d; } proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; location / { proxy_pass http://localhost:8000; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; } } <VirtualHost *:80> ServerName mailing.ddd.fr ErrorLog ${APACHE_LOG_DIR}/mailing.error.log CustomLog ${APACHE_LOG_DIR}/mailing.access.log combined <Location /static/> Alias "/opt/mailman/static/" </Location> <Location /> ProxyPass http://localhost:8000/ ProxyPassReverse http://localhost:8000/ ProxyPreserveHost On </Location> </VirtualHost>/ I missed something ? Thanks.

5 10

Error while running mailman-web compilemessages
by Prasanth Nair 26 Jul '22

26 Jul '22

Hello, I'm in the process of installing a Mailman3 server. I get the following error messages when I run the command 'mailman-web compilemessages'. It was working fine before and noticed this recently. Can someone suggest a solution to solve this issue, please? *Execution of msgfmt failed: /opt/mailman/venv/lib/python3.8/site-packages/django_extensions/locale/ar/LC_MESSAGES/django.po:25: 'msgstr' is not a valid Python format string, unlike 'msgid'. Reason: The character that terminates the directive number 1 is not a valid conversion specifier./opt/mailman/venv/lib/python3.8/site-packages/django_extensions/locale/ar/LC_MESSAGES/django.po:82: 'msgstr' is not a valid Python format string, unlike 'msgid'. Reason: In the directive number 1, the character ')' is not a valid conversion specifier./opt/mailman/venv/lib/python3.8/site-packages/django_extensions/locale/ar/LC_MESSAGES/django.po:104: 'msgstr' is not a valid Python format string, unlike 'msgid'. Reason: The string ends in the middle of a directive./opt/mailman/venv/lib/python3.8/site-packages/django_extensions/locale/ar/LC_MESSAGES/django.po:109: 'msgstr' is not a valid Python format string, unlike 'msgid'. Reason: The string ends in the middle of a directive.msgfmt: found 4 fatal errors* Kind regards, Prasanth Nair

4 7

List and Domain listing slow
by Patrik Peng 25 Jul '22

25 Jul '22

Hi there Recently we migrated 4000+ lists from Mailman 2 to 3 and noticed a drastic slowdown of response time (30+ secs) when listing lists or domains while logged in as any user. Affected are the following paths: * https://mm3.com/mailman3/lists/ * https://mm3.com/mailman3/domains/ When visiting one of the affected pages, a lot of API requests are visible in `mailman.log`: [25/Jul/2022:11:02:02 +0200] "GET /3.1/domains/domain1.com HTTP/1.1" 200 202 "-" "GNU Mailman REST client v3.3.3" [25/Jul/2022:11:02:02 +0200] "GET /3.1/domains/domain2.com HTTP/1.1" 200 188 "-" "GNU Mailman REST client v3.3.3" [25/Jul/2022:11:02:02 +0200] "GET /3.1/domains/domain3.com HTTP/1.1" 200 200 "-" "GNU Mailman REST client v3.3.3" [25/Jul/2022:11:02:02 +0200] "GET /3.1/domains/domain4.com HTTP/1.1" 200 218 "-" "GNU Mailman REST client v3.3.3" I'm suspecting an n+1 issue where a request is made for every list entry and even if the API response times are quick (15-20ms), this time accumulates. Regards, Patrik ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

1 0

Trouble importing a Mailman 3 Postgres database into a new Mailman 3 instance (Docker)
by skenny＠scss.tcd.ie 22 Jul '22

22 Jul '22

Our in-production Mailman 3 service is running under Docker (maxking's mailman-web, mailman-core and Postgres database containers). I want to move Mailman to a different server, where I have a clean install of Mailman 3 up and running. When I take a database dump of the in-production database, and import it on the new server, a ton of errors are produced, and the core and web containers die after 15 seconds or so. I have noticed that if I first delete the mailmandb database on the new server, then create it anew, and _then_ do the import, everything is fine. I see all my lists in the web interface on the new server, it's all good. But deleting and then creating a new blank mailmandb database just prior to importing ... it can't be the right thing to do. Below is a sample of the errors that are reported on the stdout from my docker-compose command. I'd be very grateful for any pointers as to where to go next with this. Many thanks in advance, Stephen Kenny database_1 | ERROR: relation "auth_permission_id_seq" already exists database_1 | STATEMENT: CREATE SEQUENCE public.auth_permission_id_seq database_1 | START WITH 1 database_1 | INCREMENT BY 1 database_1 | NO MINVALUE database_1 | NO MAXVALUE database_1 | CACHE 1; database_1 | ERROR: insert or update on table "_request"well violates foreign key constraint "_request_mailing_list_id_fkey" database_1 | DETAIL: Key (mailing_list_id)=(774) is not present in table "mailinglist". database_1 | STATEMENT: COPY public._request (id, key, request_type, data_hash, mailing_list_id) FROM stdin; database_1 | STATEMENT: ALTER TABLE ONLY public.auth_group_permissions database_1 | ADD CONSTRAINT auth_group_permissions_group_id_permission_id_0cd325b0_uniq UNIQUE (group_id, permission_id); database_1 | ERROR: multiple primary keys for table "auth_group_permissions" are not allowed database_1 | STATEMENT: ALTER TABLE ONLY public.auth_group_permissions database_1 | ADD CONSTRAINT auth_group_permissions_pkey PRIMARY KEY (id); database_1 | ERROR: multiple primary keys for table "auth_group" are not allowed database_1 | STATEMENT: ALTER TABLE ONLY public.auth_group database_1 | ADD CONSTRAINT auth_group_pkey PRIMARY KEY (id); database_1 | ERROR: relation "auth_permission_content_type_id_codename_01ab375a_uniq" already exists database_1 | ERROR: relation "account_emailaddress_user_id_2c513194" already exists database_1 | STATEMENT: CREATE INDEX account_emailaddress_user_id_2c513194 ON public.account_emailaddress USING btree (user_id); database_1 | ERROR: relation "account_emailconfirmation_email_address_id_5b7f8c58" already exists database_1 | STATEMENT: CREATE INDEX account_emailconfirmation_email_address_id_5b7f8c58 ON public.account_emailconfirmation USING btree (email_address_id); database_1 | ERROR: relation "account_emailconfirmation_key_f43612bd_like" already exists database_1 | STATEMENT: CREATE INDEX account_emailconfirmation_key_f43612bd_like ON public.account_emailconfirmation USING btree (key varchar_pattern_ops); database_1 | ERROR: constraint "hyperkitty_tagging_thread_id_ab30508b_fk_hyperkitty_thread_id" for relation "hyperkitty_tagging" already exists database_1 | STATEMENT: ALTER TABLE ONLY public.hyperkitty_tagging database_1 | ADD CONSTRAINT hyperkitty_tagging_thread_id_ab30508b_fk_hyperkitty_thread_id FOREIGN KEY (thread_id) REFERENCES public.hyperkitty_thread(id) DEFERRABLE INITIALLY DEFERRED; database_1 | ERROR: constraint "hyperkitty_tagging_user_id_9af832e2_fk_auth_user_id" for relation "hyperkitty_tagging" already exists database_1 | STATEMENT: ALTER TABLE ONLY public.hyperkitty_tagging database_1 | ADD CONSTRAINT hyperkitty_tagging_user_id_9af832e2_fk_auth_user_id FOREIGN KEY (user_id) REFERENCES public.auth_user(id) DEFERRABLE INITIALLY DEFERRED; and finally .... mailman-core | Traceback (most recent call last): mailman-core | File "/usr/bin/mailman", line 8, in <module> mailman-core | sys.exit(main()) mailman-core | File "/usr/lib/python3.8/site-packages/click/core.py", line 1130, in __call__ mailman-core | return self.main(*args, **kwargs) mailman-core | File "/usr/lib/python3.8/site-packages/click/core.py", line 1054, in main mailman-core | with self.make_context(prog_name, args, **extra) as ctx: mailman-core | File "/usr/lib/python3.8/site-packages/click/core.py", line 920, in make_context mailman-core | self.parse_args(ctx, args) mailman-core | File "/usr/lib/python3.8/site-packages/click/core.py", line 1613, in parse_args mailman-core | rest = super().parse_args(ctx, args) mailman-core | File "/usr/lib/python3.8/site-packages/click/core.py", line 1378, in parse_args mailman-core | value, args = param.handle_parse_result(ctx, opts, args) mailman-core | File "/usr/lib/python3.8/site-packages/click/core.py", line 2360, in handle_parse_result mailman-core | value = self.process_value(ctx, value) mailman-core | File "/usr/lib/python3.8/site-packages/click/core.py", line 2322, in process_value mailman-core | value = self.callback(ctx, self, value) mailman-core | File "/usr/lib/python3.8/site-packages/mailman/bin/mailman.py", line 95, in initialize_config mailman-core | initialize(value) mailman-core | File "/usr/lib/python3.8/site-packages/mailman/core/initialize.py", line 218, in initialize mailman-core | initialize_2(propagate_logs=propagate_logs) mailman-core | File "/usr/lib/python3.8/site-packages/mailman/core/initialize.py", line 177, in initialize_2 mailman-core | config.db = getUtility(IDatabaseFactory, utility_name).create() mailman-core | File "/usr/lib/python3.8/site-packages/mailman/database/factory.py", line 55, in create mailman-core | SchemaManager(database).setup_database() mailman-core | File "/usr/lib/python3.8/site-packages/mailman/database/factory.py", line 84, in setup_database mailman-core | current_rev = context.get_current_revision() mailman-core | File "/usr/lib/python3.8/site-packages/alembic/runtime/migration.py", line 435, in get_current_revision mailman-core | raise util.CommandError( mailman-core | alembic.util.exc.CommandError: Version table 'alembic_version' has more than one head present; please use get_current_heads() mailman-core exited with code 1 mailman-web | Compiling locale files in /usr/lib/python3.8/site-packages mailman-web | Traceback (most recent call last): mailman-web | File "/opt/mailman-web/manage.py", line 10, in <module> mailman-web | execute_from_command_line(sys.argv) mailman-web | File "/usr/lib/python3.8/site-packages/django/core/management/__init__.py", line 419, in execute_from_command_line mailman-web | utility.execute() mailman-web | File "/usr/lib/python3.8/site-packages/django/core/management/__init__.py", line 363, in execute mailman-web | settings.INSTALLED_APPS mailman-web | File "/usr/lib/python3.8/site-packages/django/conf/__init__.py", line 82, in __getattr__ mailman-web | self._setup(name) mailman-web | File "/usr/lib/python3.8/site-packages/django/conf/__init__.py", line 69, in _setup mailman-web | self._wrapped = Settings(settings_module) mailman-web | File "/usr/lib/python3.8/site-packages/django/conf/__init__.py", line 170, in __init__ mailman-web | mod = importlib.import_module(self.SETTINGS_MODULE) mailman-web | File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module mailman-web | return _bootstrap._gcd_import(name[level:], package, level) mailman-web | File "<frozen importlib._bootstrap>", line 1014, in _gcd_import mailman-web | File "<frozen importlib._bootstrap>", line 991, in _find_and_load mailman-web | File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked mailman-web | File "<frozen importlib._bootstrap>", line 671, in _load_unlocked mailman-web | File "<frozen importlib._bootstrap_external>", line 848, in exec_module mailman-web | File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed mailman-web | File "/opt/mailman-web/settings.py", line 65, in <module> mailman-web | MAILMAN_ARCHIVER_FROM = (os.environ.get('MAILMAN_HOST_IP', gethostbyname(os.environ.get('MAILMAN_HOSTNAME', 'mailman-core'))),) mailman-web | socket.gaierror: [Errno -2] Name does not resolve mailman-web | python3: can't open file 'manage.py': [Errno 2] No such file or directory mailman-web exited with code 2

3 6

Messages Showing Up as "Forwarded"
by Mail Person 22 Jul '22

22 Jul '22

Sorry if this is an easy question, but I've got mailman3 up and running and all my test messages show up with forwarding language around them rather than just the message, see below: ---------- Forwarded message ---------- From: Person <person(a)gmail.com> To: all(a)domain.com Cc: Bcc: Date: Thu, 21 Jul 2022 13:56:22 -0700 Subject: Hello Members This is a wonderful test ---------- Forwarded message ---------- From: Person <person(a)gmail.com> To: all(a)domain.com Cc: Bcc: Date: Thu, 21 Jul 2022 13:56:22 -0700 Subject: Hello Members _______________________________________________ Mailing list footer

2 1

Can't Start Mailman3 Core on Fresh Install
by Mail Person 21 Jul '22

21 Jul '22

Hi Everyone. I'm installing Mailman3 on a Ubunu 18.03 server using MySQL as the backend. After installing using the mailman3-full package and configuring it, I'm getting the following error when trying to start the mailman3 service: l 21 04:28:44 eps mailman3[81963]: packet.raise_for_error() Jul 21 04:28:44 eps mailman3[81963]: File "/usr/local/lib/python3.8/dist-packages/pymysql/protocol.py", line 221, in raise_for_error Jul 21 04:28:44 eps mailman3[81963]: err.raise_mysql_exception(self._data) Jul 21 04:28:44 eps mailman3[81963]: File "/usr/local/lib/python3.8/dist-packages/pymysql/err.py", line 143, in raise_mysql_exception Jul 21 04:28:44 eps mailman3[81963]: raise errorclass(errno, errval) Jul 21 04:28:44 eps mailman3[81963]: sqlalchemy.exc.OperationalError: (pymysql.err.OperationalError) (1045, "Access denied for user 'mailman3'@'127.0.0.1' (using password: YES)") Jul 21 04:28:44 eps mailman3[81963]: (Background on this error at: http://sqlalche.me/e/e3q8) I'm not sure why the access issue is happening. Mailman3-web is running fine and I can see the site at mailman3/postorius/lists (but it says Page Not Found).

4 7

check/update delivery status via python script
by Eggert Ehmke 19 Jul '22

19 Jul '22

Somehow I can't get the starting point in the documentation to do stuff like this. Besides, when I try to run examples from https://docs.mailman3.org/projects/mailman/en/release-3.0/src/mailman/ commands/docs/withlist.html[1] I run into errors like AttributeError: 'Withlist' object has no attribute 'process' Where to start? I thought I have some python experience but your API makes my head burn. -------- [1] https://docs.mailman3.org/projects/mailman/en/release-3.0/src/mailman/ commands/docs/withlist.html

2 2

Hacking attempts?
by Lists 17 Jul '22

17 Jul '22

Hi, We are seeing thousands of these emails every day, looks like someone is trying to hack our Mailman3 but would appreciate someone with more knowledge of MM3 to confirm. Is this a problem with our setup? i.e. the “Internal Server Error” bit, or are the hackers just sending bad data that is causing the error? also how do we stop/block this? TIA and here is a typical email: Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/accounts/fedora/login/ Internal Server Error: /mailman3/accounts/fedora/login/ TypeError at /accounts/fedora/login/ _openid_consumer() missing 2 required positional arguments: 'provider' and 'endpoint' Request Method: GET Request URL: https://mailman.ardc.net/mailman3/accounts/fedora/login/?process=login&next… <https://mailman.ardc.net/mailman3/accounts/fedora/login/?process=login&next…> Django Version: 2.2.26 Python Executable: /usr/bin/uwsgi-core Python Version: 3.9.2 Python Path: ['.', '', '/usr/lib/python39.zip', '/usr/lib/python3.9', '/usr/lib/python3.9/lib-dynload', '/usr/local/lib/python3.9/dist-packages', '/usr/lib/python3/dist-packages', '/usr/lib/python3.9/dist-packages'] Server time: Thu, 14 Jul 2022 02:34:04 -0400 Installed Applications: ('hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', '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') Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Traceback: File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 34. response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 115. response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 113. response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py" in view 71. return self.dispatch(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py" in dispatch 97. return handler(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django_mailman3/lib/auth/fedora/views.py" in get 56. return self.post(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django_mailman3/lib/auth/fedora/views.py" in post 67. client = _openid_consumer(request) Exception Type: TypeError at /accounts/fedora/login/ Exception Value: _openid_consumer() missing 2 required positional arguments: 'provider' and 'endpoint' Request information: USER: AnonymousUser GET: process = 'login' next = '/mailman3/hyperkitty/list/44net(a)mailman.ampr.org <mailto:mailman3/hyperkitty/list/44net@mailman.ampr.org>/message/O5Z2YZBJZXFPH2ACAORN6BST7B2S3M3P/' POST: No POST data FILES: No FILES data COOKIES: No cookie data META: CONTEXT_DOCUMENT_ROOT = '/var/www/html' CONTEXT_PREFIX = '' DOCUMENT_ROOT = '/var/www/html' GATEWAY_INTERFACE = 'CGI/1.1' HTTPS = 'on' HTTP_ACCEPT = 'text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8' HTTP_ACCEPT_ENCODING = 'gzip,deflate' HTTP_CONNECTION = 'Keep-Alive' HTTP_HOST = 'mailman.ardc.net <http://mailman.ardc.net/>' HTTP_USER_AGENT = 'Mozilla/5.0 (compatible; BLEXBot/1.0; +http://webmeup-crawler.com/ <http://webmeup-crawler.com/>)' PATH = '/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin' PATH_INFO = '/accounts/fedora/login/' QUERY_STRING = 'process=login&next=/mailman3/hyperkitty/list/44net(a)mailman.ampr.org <mailto:process=login&next=/mailman3/hyperkitty/list/44net@mailman.ampr.org>/message/O5Z2YZBJZXFPH2ACAORN6BST7B2S3M3P/' REMOTE_ADDR = '157.90.177.212' REMOTE_PORT = '63384' REQUEST_METHOD = 'GET' REQUEST_SCHEME = 'https' REQUEST_URI = '/mailman3/accounts/fedora/login/?process=login&next=/mailman3/hyperkitty/list/44net(a)mailman.ampr.org <mailto:mailman3/accounts/fedora/login/?process=login&next=/mailman3/hyperkitty/list/44net@mailman.ampr.org>/message/O5Z2YZBJZXFPH2ACAORN6BST7B2S3M3P/' SCRIPT_FILENAME = 'proxy:uwsgi://localhost//accounts/fedora/login/' <uwsgi://localhost//accounts/fedora/login/'> SCRIPT_NAME = '/mailman3' SERVER_ADDR = '44.1.1.29' SERVER_ADMIN = 'postmaster(a)ardc.net <mailto:postmaster@ardc.net>' SERVER_NAME = 'mailman.ardc.net <http://mailman.ardc.net/>' SERVER_PORT = '443' SERVER_PROTOCOL = 'HTTP/1.1' SERVER_SIGNATURE = '<address>Apache/2.4.53 (Debian) Server at mailman.ardc.net <http://mailman.ardc.net/> Port 443</address>\n' SERVER_SOFTWARE = 'Apache/2.4.53 (Debian)' SSL_TLS_SNI = 'mailman.ardc.net <http://mailman.ardc.net/>' uwsgi.core = 1 uwsgi.node = b'mailman' uwsgi.version = b'2.0.19.1-debian' wsgi.errors = <_io.TextIOWrapper name=2 mode='w' encoding='UTF-8'> wsgi.file_wrapper = '' wsgi.input = <uwsgi._Input object at 0x7f8e0b4a0410> wsgi.multiprocess = False wsgi.multithread = True wsgi.run_once = False wsgi.url_scheme = 'https' wsgi.version = '(1, 0)' Settings: Using settings module settings ABSOLUTE_URL_OVERRIDES = {} ACCOUNT_AUTHENTICATION_METHOD = 'username_email' ACCOUNT_DEFAULT_HTTP_PROTOCOL = 'https' ACCOUNT_EMAIL_REQUIRED = True ACCOUNT_EMAIL_VERIFICATION = 'mandatory' ACCOUNT_UNIQUE_EMAIL = True ADMINS = "(('Mailman Suite Admin', 'postmaster(a)ardc.net <mailto:postmaster@ardc.net>'),)" ALLOWED_HOSTS = ['*'] APPEND_SLASH = True AUTHENTICATION_BACKENDS = "('django.contrib.auth.backends.ModelBackend', 'allauth.account.auth_backends.AuthenticationBackend')" AUTH_PASSWORD_VALIDATORS = '********************' AUTH_USER_MODEL = 'auth.User' BASE_DIR = '/usr/share/mailman3-web' CACHES = {'default': {'BACKEND': 'django.core.cache.backends.locmem.LocMemCache'}} CACHE_MIDDLEWARE_ALIAS = 'default' CACHE_MIDDLEWARE_KEY_PREFIX = '********************' CACHE_MIDDLEWARE_SECONDS = 600 COMPRESSORS = {'css': 'compressor.css.CssCompressor', 'js': 'compressor.js.JsCompressor'} COMPRESS_CACHEABLE_PRECOMPILERS = '()' COMPRESS_CACHE_BACKEND = 'default' COMPRESS_CACHE_KEY_FUNCTION = '********************' COMPRESS_CLEAN_CSS_ARGUMENTS = '' COMPRESS_CLEAN_CSS_BINARY = 'cleancss' COMPRESS_CLOSURE_COMPILER_ARGUMENTS = '' COMPRESS_CLOSURE_COMPILER_BINARY = 'java -jar compiler.jar' COMPRESS_CSS_HASHING_METHOD = 'mtime' COMPRESS_DATA_URI_MAX_SIZE = 1024 COMPRESS_DEBUG_TOGGLE = None COMPRESS_ENABLED = True COMPRESS_FILTERS = {'css': ['compressor.filters.css_default.CssAbsoluteFilter'], 'js': ['compressor.filters.jsmin.JSMinFilter']} COMPRESS_JINJA2_GET_ENVIRONMENT = <function CompressorConf.JINJA2_GET_ENVIRONMENT at 0x7f8e17d7a670> COMPRESS_MINT_DELAY = 30 COMPRESS_MTIME_DELAY = 10 COMPRESS_OFFLINE = True COMPRESS_OFFLINE_CONTEXT = {'STATIC_URL': '/mailman3/static/'} COMPRESS_OFFLINE_MANIFEST = 'manifest.json' COMPRESS_OFFLINE_TIMEOUT = 31536000 COMPRESS_OUTPUT_DIR = 'CACHE' COMPRESS_PARSER = 'compressor.parser.AutoSelectParser' COMPRESS_PRECOMPILERS = '()' COMPRESS_REBUILD_TIMEOUT = 2592000 COMPRESS_ROOT = '/var/lib/mailman3/web/static' COMPRESS_STORAGE = 'compressor.storage.CompressorFileStorage' COMPRESS_TEMPLATE_FILTER_CONTEXT = {'STATIC_URL': '/mailman3/static/'} COMPRESS_URL = '/mailman3/static/' COMPRESS_URL_PLACEHOLDER = '/__compressor_url_placeholder__/' COMPRESS_VERBOSE = False COMPRESS_YUGLIFY_BINARY = 'yuglify' COMPRESS_YUGLIFY_CSS_ARGUMENTS = '--terminal' COMPRESS_YUGLIFY_JS_ARGUMENTS = '--terminal' COMPRESS_YUI_BINARY = 'java -jar yuicompressor.jar' COMPRESS_YUI_CSS_ARGUMENTS = '' COMPRESS_YUI_JS_ARGUMENTS = '' CSRF_COOKIE_AGE = 31449600 CSRF_COOKIE_DOMAIN = None CSRF_COOKIE_HTTPONLY = False CSRF_COOKIE_NAME = 'csrftoken' CSRF_COOKIE_PATH = '/' CSRF_COOKIE_SAMESITE = 'Lax' CSRF_COOKIE_SECURE = False CSRF_FAILURE_VIEW = 'django.views.csrf.csrf_failure' CSRF_HEADER_NAME = 'HTTP_X_CSRFTOKEN' CSRF_TRUSTED_ORIGINS = [] CSRF_USE_SESSIONS = False DATABASES = {'default': {'ENGINE': 'django.db.backends.mysql', 'NAME': 'mailman', 'USER': 'mailman', 'PASSWORD': '********************', 'HOST': ‘X.X.X.X', 'PORT': '', 'OPTIONS': {'init_command': "SET sql_mode='STRICT_TRANS_TABLES'", 'charset': 'utf8mb4'}, 'ATOMIC_REQUESTS': False, 'AUTOCOMMIT': True, 'CONN_MAX_AGE': 0, 'TIME_ZONE': None, 'TEST': {'CHARSET': None, 'COLLATION': None, 'NAME': None, 'MIRROR': None}}} DATABASE_ROUTERS = [] DATA_UPLOAD_MAX_MEMORY_SIZE = 2621440 DATA_UPLOAD_MAX_NUMBER_FIELDS = 1000 DATETIME_FORMAT = 'N j, Y, P' DATETIME_INPUT_FORMATS = ['%Y-%m-%d %H:%M:%S', '%Y-%m-%d %H:%M:%S.%f', '%Y-%m-%d %H:%M', '%Y-%m-%d', '%m/%d/%Y %H:%M:%S', '%m/%d/%Y %H:%M:%S.%f', '%m/%d/%Y %H:%M', '%m/%d/%Y', '%m/%d/%y %H:%M:%S', '%m/%d/%y %H:%M:%S.%f', '%m/%d/%y %H:%M', '%m/%d/%y'] DATE_FORMAT = 'N j, Y' DATE_INPUT_FORMATS = ['%Y-%m-%d', '%m/%d/%Y', '%m/%d/%y', '%b %d %Y', '%b %d, %Y', '%d %b %Y', '%d %b, %Y', '%B %d %Y', '%B %d, %Y', '%d %B %Y', '%d %B, %Y'] DEBUG = False DEBUG_PROPAGATE_EXCEPTIONS = False DECIMAL_SEPARATOR = '.' DEFAULT_CHARSET = 'utf-8' DEFAULT_CONTENT_TYPE = 'text/html' DEFAULT_EXCEPTION_REPORTER_FILTER = 'django.views.debug.SafeExceptionReporterFilter' DEFAULT_FILE_STORAGE = 'django.core.files.storage.FileSystemStorage' DEFAULT_FROM_EMAIL = 'postorius(a)mailman.ardc.net <mailto:postorius@mailman.ardc.net>' DEFAULT_INDEX_TABLESPACE = '' DEFAULT_TABLESPACE = '' DISALLOWED_USER_AGENTS = [] EMAILNAME = 'mailman.ardc.net <http://mailman.ardc.net/>' EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_HOST_PASSWORD = '********************' EMAIL_HOST_USER = '' EMAIL_PORT = 25 EMAIL_SSL_CERTFILE = None EMAIL_SSL_KEYFILE = '********************' EMAIL_SUBJECT_PREFIX = '[Django] ' EMAIL_TIMEOUT = None EMAIL_USE_LOCALTIME = False EMAIL_USE_SSL = False EMAIL_USE_TLS = False FILE_CHARSET = 'utf-8' FILE_UPLOAD_DIRECTORY_PERMISSIONS = None FILE_UPLOAD_HANDLERS = ['django.core.files.uploadhandler.MemoryFileUploadHandler', 'django.core.files.uploadhandler.TemporaryFileUploadHandler'] FILE_UPLOAD_MAX_MEMORY_SIZE = 2621440 FILE_UPLOAD_PERMISSIONS = None FILE_UPLOAD_TEMP_DIR = None FILTER_VHOST = False FIRST_DAY_OF_WEEK = 0 FIXTURE_DIRS = [] FORCE_SCRIPT_NAME = None FORMAT_MODULE_PATH = None FORM_RENDERER = 'django.forms.renderers.DjangoTemplates' HAYSTACK_CONNECTIONS = {'default': {'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', 'PATH': '/var/lib/mailman3/web/fulltext_index'}} HOSTNAME = 'localhost.local' IGNORABLE_404_URLS = [] INSTALLED_APPS = "('hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', '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')" INTERNAL_IPS = [] LANGUAGES = [('af', 'Afrikaans'), ('ar', 'Arabic'), ('ast', 'Asturian'), ('az', 'Azerbaijani'), ('bg', 'Bulgarian'), ('be', 'Belarusian'), ('bn', 'Bengali'), ('br', 'Breton'), ('bs', 'Bosnian'), ('ca', 'Catalan'), ('cs', 'Czech'), ('cy', 'Welsh'), ('da', 'Danish'), ('de', 'German'), ('dsb', 'Lower Sorbian'), ('el', 'Greek'), ('en', 'English'), ('en-au', 'Australian English'), ('en-gb', 'British English'), ('eo', 'Esperanto'), ('es', 'Spanish'), ('es-ar', 'Argentinian Spanish'), ('es-co', 'Colombian Spanish'), ('es-mx', 'Mexican Spanish'), ('es-ni', 'Nicaraguan Spanish'), ('es-ve', 'Venezuelan Spanish'), ('et', 'Estonian'), ('eu', 'Basque'), ('fa', 'Persian'), ('fi', 'Finnish'), ('fr', 'French'), ('fy', 'Frisian'), ('ga', 'Irish'), ('gd', 'Scottish Gaelic'), ('gl', 'Galician'), ('he', 'Hebrew'), ('hi', 'Hindi'), ('hr', 'Croatian'), ('hsb', 'Upper Sorbian'), ('hu', 'Hungarian'), ('hy', 'Armenian'), ('ia', 'Interlingua'), ('id', 'Indonesian'), ('io', 'Ido'), ('is', 'Icelandic'), ('it', 'Italian'), ('ja', 'Japanese'), ('ka', 'Georgian'), ('kab', 'Kabyle'), ('kk', 'Kazakh'), ('km', 'Khmer'), ('kn', 'Kannada'), ('ko', 'Korean'), ('lb', 'Luxembourgish'), ('lt', 'Lithuanian'), ('lv', 'Latvian'), ('mk', 'Macedonian'), ('ml', 'Malayalam'), ('mn', 'Mongolian'), ('mr', 'Marathi'), ('my', 'Burmese'), ('nb', 'Norwegian Bokmål'), ('ne', 'Nepali'), ('nl', 'Dutch'), ('nn', 'Norwegian Nynorsk'), ('os', 'Ossetic'), ('pa', 'Punjabi'), ('pl', 'Polish'), ('pt', 'Portuguese'), ('pt-br', 'Brazilian Portuguese'), ('ro', 'Romanian'), ('ru', 'Russian'), ('sk', 'Slovak'), ('sl', 'Slovenian'), ('sq', 'Albanian'), ('sr', 'Serbian'), ('sr-latn', 'Serbian Latin'), ('sv', 'Swedish'), ('sw', 'Swahili'), ('ta', 'Tamil'), ('te', 'Telugu'), ('th', 'Thai'), ('tr', 'Turkish'), ('tt', 'Tatar'), ('udm', 'Udmurt'), ('uk', 'Ukrainian'), ('ur', 'Urdu'), ('vi', 'Vietnamese'), ('zh-hans', 'Simplified Chinese'), ('zh-hant', 'Traditional Chinese')] LANGUAGES_BIDI = ['he', 'ar', 'fa', 'ur'] LANGUAGE_CODE = 'en-us' LANGUAGE_COOKIE_AGE = None LANGUAGE_COOKIE_DOMAIN = None LANGUAGE_COOKIE_NAME = 'django_language' LANGUAGE_COOKIE_PATH = '/' LOCALE_PATHS = [] LOGGING = {'version': 1, 'disable_existing_loggers': False, 'filters': {'require_debug_false': {'()': 'django.utils.log.RequireDebugFalse'}}, 'handlers': {'mail_admins': {'level': 'ERROR', 'filters': ['require_debug_false'], 'class': 'django.utils.log.AdminEmailHandler'}, 'file': {'level': 'INFO', 'class': 'logging.handlers.RotatingFileHandler', 'filename': '/var/log/mailman3/web/mailman-web.log', 'formatter': 'verbose'}, 'console': {'class': 'logging.StreamHandler', 'formatter': 'simple'}}, 'loggers': {'django.request': {'handlers': ['mail_admins', 'file'], 'level': 'INFO', 'propagate': True}, 'django': {'handlers': ['file'], 'level': 'INFO', 'propagate': True}, 'hyperkitty': {'handlers': ['file'], 'level': 'INFO', 'propagate': True}, 'postorius': {'handlers': ['file'], 'level': 'INFO', 'propagate': True}}, 'formatters': {'verbose': {'format': '%(levelname)s %(asctime)s %(process)d %(name)s %(message)s'}, 'simple': {'format': '%(levelname)s %(message)s'}}} LOGGING_CONFIG = 'logging.config.dictConfig' LOGIN_REDIRECT_URL = 'list_index' LOGIN_URL = 'account_login' LOGOUT_REDIRECT_URL = None LOGOUT_URL = 'account_logout' MAILMAN_ARCHIVER_FROM = "('127.0.0.1', '::1', '10.4.16.129', '44.1.1.29')" MAILMAN_ARCHIVER_KEY = '********************' MAILMAN_REST_API_PASS = '********************' MAILMAN_REST_API_URL = '********************' MAILMAN_REST_API_USER = '********************' MANAGERS = [] MEDIA_ROOT = '' MEDIA_URL = '' MESSAGE_STORAGE = 'django.contrib.messages.storage.fallback.FallbackStorage' MESSAGE_TAGS = {40: 'danger'} MIDDLEWARE = "('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware')" MIGRATION_MODULES = {} MONTH_DAY_FORMAT = 'F j' NUMBER_GROUPING = 0 PASSWORD_HASHERS = '********************' PASSWORD_RESET_TIMEOUT_DAYS = '********************' POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost/mailman3/ <http://localhost/mailman3/>' PREPEND_WWW = False Q_CLUSTER = {'timeout': 300, 'save_limit': 100, 'orm': 'default', 'poll': 5} ROOT_URLCONF = 'urls' SECRET_KEY = '********************' SECURE_BROWSER_XSS_FILTER = False SECURE_CONTENT_TYPE_NOSNIFF = False SECURE_HSTS_INCLUDE_SUBDOMAINS = False SECURE_HSTS_PRELOAD = False SECURE_HSTS_SECONDS = 0 SECURE_PROXY_SSL_HEADER = None SECURE_REDIRECT_EXEMPT = [] SECURE_SSL_HOST = None SECURE_SSL_REDIRECT = False SERVER_EMAIL = 'root(a)mailman.ardc.net <mailto:root@mailman.ardc.net>' SESSION_CACHE_ALIAS = 'default' SESSION_COOKIE_AGE = 1209600 SESSION_COOKIE_DOMAIN = None SESSION_COOKIE_HTTPONLY = True SESSION_COOKIE_NAME = 'sessionid' SESSION_COOKIE_PATH = '/' SESSION_COOKIE_SAMESITE = 'Lax' SESSION_COOKIE_SECURE = False SESSION_ENGINE = 'django.contrib.sessions.backends.db' SESSION_EXPIRE_AT_BROWSER_CLOSE = False SESSION_FILE_PATH = None SESSION_SAVE_EVERY_REQUEST = False SESSION_SERIALIZER = 'django.contrib.sessions.serializers.PickleSerializer' SETTINGS_MODULE = 'settings' SHORT_DATETIME_FORMAT = 'm/d/Y P' SHORT_DATE_FORMAT = 'm/d/Y' SIGNING_BACKEND = 'django.core.signing.TimestampSigner' SILENCED_SYSTEM_CHECKS = [] SITE_ID = 1 SOCIALACCOUNT_PROVIDERS = {} STATICFILES_DIRS = '()' STATICFILES_FINDERS = "('django.contrib.staticfiles.finders.FileSystemFinder', 'django.contrib.staticfiles.finders.AppDirectoriesFinder', 'compressor.finders.CompressorFinder')" STATICFILES_STORAGE = 'django.contrib.staticfiles.storage.StaticFilesStorage' STATIC_ROOT = '/var/lib/mailman3/web/static' STATIC_URL = '/mailman3/static/' TEMPLATES = [{'BACKEND': 'django.template.backends.django.DjangoTemplates', 'DIRS': [], 'APP_DIRS': True, 'OPTIONS': {'context_processors': ['django.template.context_processors.debug', 'django.template.context_processors.i18n', 'django.template.context_processors.media', 'django.template.context_processors.static', 'django.template.context_processors.tz', 'django.template.context_processors.csrf', 'django.template.context_processors.request', 'django.contrib.auth.context_processors.auth', 'django.contrib.messages.context_processors.messages', 'django_mailman3.context_processors.common', 'hyperkitty.context_processors.common', 'postorius.context_processors.postorius']}}] TEST_NON_SERIALIZED_APPS = [] TEST_RUNNER = 'django.test.runner.DiscoverRunner' THOUSAND_SEPARATOR = ',' TIME_FORMAT = 'P' TIME_INPUT_FORMATS = ['%H:%M:%S', '%H:%M:%S.%f', '%H:%M'] TIME_ZONE = 'UTC' USE_I18N = True USE_L10N = True USE_THOUSAND_SEPARATOR = False USE_TZ = True USE_X_FORWARDED_HOST = True USE_X_FORWARDED_PORT = False WSGI_APPLICATION = 'wsgi.application' X_FRAME_OPTIONS = 'SAMEORIGIN' YEAR_MONTH_FORMAT = 'F Y’

7 19

Messages attached to probe messages
by Bjoern Franke 15 Jul '22

15 Jul '22

Hi, some time ago I started a discussion where I wrongly assumed that probe messages were sent accidentally from example.com Some digging showed now that the sender of the probe messages are correct, but the attached messages seem to be wrong. An attached example for bouncing messages was: From: Mailman <mailman(a)example.com> To: Mailman Bounces <mailman-bounces(a)example.com> Subject: SMTP Delivery Failure Message-ID: <165577237837.35.8042057157021349872@mailman-core> Date: Tue, 21 Jun 2022 00:46:18 +0000 Message-ID-Hash: TOJ7WDT3TXWOEHZB4USRUOPZUW7BEATI X-Message-ID-Hash: TOJ7WDT3TXWOEHZB4USRUOPZUW7BEATI Mail to bjo(a)schafweide.org failed at outgoing SMTP Error code: 554 Error message: b'5.7.1 Spam message rejected' I took a look into the logs and found no example.com, but: Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) handling connection Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) >> b'LHLO mail.ffnw.de' Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) >> b'MAIL FROM:<yzvotmm(a)forestanes.mom> SIZE=293338' Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) sender: yzvotmm(a)forestanes.mom Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) >> b'RCPT TO:<vorstand(a)lists.ffnw.de>' Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) recip: vorstand(a)lists.ffnw.de Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) >> b'DATA' Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) >> b'QUIT' Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) connection lost Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) Connection lost during _handle_client() Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> response exception: (554, b'5.7.1 Spam message rejected') Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> response exception: (554, b'5.7.1 Spam message rejected') Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> smtp to vorstand(a)lists.ffnw.de for 6 recips, completed in 0.7157599925994873 seconds Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> post to vorstand(a)lists.ffnw.de from vorstand(a)lists.ffnw.de, 294362 bytes, 6 failures Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> delivery to foo(a)stadel.info failed with code 554, b'5.7.1 Spam message rejected' Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> delivery to abc(a)ffnw.de failed with code 554, b'5.7.1 Spam message rejected' Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> delivery to def(a)ffnw.de failed with code 554, b'5.7.1 Spam message rejected' Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> delivery to xyz(a)ffnw.de failed with code 554, b'5.7.1 Spam message rejected' Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> delivery to bjo(a)schafweide.org failed with code 554, b'5.7.1 Spam message rejected' Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> delivery to blabla(a)osnabrueck.freifunk.net failed with code 554, b'5.7.1 Spam message rejected' Jun 21 00:46:49 2022 (35) <165577240769.30.3077851374384466408@mailman-core> smtp to vorstand(a)lists.ffnw.de for 1 recips, completed in 0.5507137775421143 seconds

3 6

Adding user - Error 409 Subscription request already pending
by kevin＠coastalaska.org 14 Jul '22

14 Jul '22

We have a couple of people trying to subscribe to our list but receive an error similar to: {"title": "409 Conflict", "description": "Subscription request already pending"} If I try to Mass Subscribe them in Postorius I get this error: HTTP Error 409: b'{"title": "409 Conflict", "description": "Subscription request already pending"}' In Postorius I don't see them hung up in Subscription requests. What to do? Thanks, Kevin

5 17

message size
by ronald.clarke＠sydney.edu.au 12 Jul '22

12 Jul '22

Dear Mailman users, I recently had a message from a user of my Mailman account blocked because there were attachments that exceeded 2 MB. This is the message I got: "Message body is too big: 5312119 bytes with a limit of 2000 KB". Is there any way to increase the maximum allowable size of attachments? Thanks, Ron Clarke

3 2

message size
by Ronald Clarke 12 Jul '22

12 Jul '22

Dear Mailman users, I recently had a message from a user of my Mailman account blocked because there were attachments that exceeded 2 MB. This is the message I got: Message body is too big: 5312119 bytes with a limit of 2000 KB. Is there any way to increase the maximum allowable size of attachments? Thanks, Ron Dr Ronald J. Clarke Associate Professor of Physical Chemistry | German Academic Exchange Service (DAAD) Ambassador Humboldt Fellow | Secretary-General of the International Union of Pure and Applied Biophysics (IUPAB) Privat-Dozent for Physical Chemistry, Johann Wolfgang Goethe-University, Frankfurt (Main) Room 517, School of Chemistry (F11) | The University of Sydney | NSW | 2006 T +61 2 9351 4406 | F +61 2 9351 3329 | E ronald.clarke(a)sydney.edu.au<mailto:ronald.clarke@sydney.edu.au>

1 0

mailman 3.x upgrade and downgrade
by skooperit＠gmail.com 12 Jul '22

12 Jul '22

Hi all, I have a few contradictory questions. 1. How to upgrade the 3.x version? 2. Is it possible to migrate (downgrade) the lists from mailman 3.x to 2.1? 3. If so, what would be the best way to do that? My mailing list server is running on a CenOS-7x with postgreSQL and the following mailman packages: django-mailman3 1.3.5 mailman 3.3.2 mailman-hyperkitty 1.1.0 mailman-web 0.0.3 mailmanclient 3.3.2 postorius 1.3.3 We have ~200 lists with more than a decade of history. thanks -- Carlos Souza

3 4

Mailman 3 stops delivering to a domain after too many bounces
by Julian Kippels 12 Jul '22

12 Jul '22

Hi, We have recently upgraded from Mailman 2 to Mailman 3. Since then I have observed many user reports that mails to mailing lists don't reach all members. My suspicion is that there are too many "dead" members on those lists. This was not a problem on Mailman 2, but has become a problem on Mailman 3. It seems to me that for example Mailman 3 sends mails to the first 5 existing member addresses from domain A, then encounters several (20 or so seems to be the threshold) "dead" member addresses from domain A that generate a bounce and then does not even attempt to reach the remaining 800 member adresses from domain A and only sends to members on domain B and domain C. Is there a way to globaly ignore bounces and send out mails to all members of a list, no matter what? Thanks, Julian

4 7

Notes about successfuly upgrade from python 3.7 to 3.9
by Guillermo Hernandez (Oldno7) 12 Jul '22

12 Jul '22

I've successfuly upgrade servers with mailman3 lists from FreeBSD 12.3 with python 3.7 to FreeBSD 13.1 with python 3.9 After doing the O.S. and all the python related apps upgraded I did the following steps: (note that my mailman3 installation is system-wide, pip drived and apache24/uwsgi served. The user that owns mailman3 is "mailman3" and all the stuff lies in "/usr/local/mailman3") -> su -> cd /usr/local/mailman3 -> pip install --upgrade django-mailman3 mailman mailman-hyperkitty mailmanclient postorius django hyperkitty uwsgi mod-wsgi -> mod_wsgi-express module-config (it returns the path for the apache24 httpd.conf adjustments. I edited it) -> su -m mailman3 -c "python3 manage.py collectstatic" -> su -m mailman3 -c "python3 manage.py migrate" -> su -m mailman3 -c "python3 manage.py compress" -> cd /usr/local/lib/python3.9/site-packages/ -> cd postorius -> django-admin compilemessages -> cd ../hyperkitty -> django-admin compilemessages -> cd ../django_mailman3 -> django-admin compilemessages I had to edit again /usr/local/lib/python3.9/site-packages/mistune/scanner.py and add this two lines (this is a little bit annoying) from mistune.util import escape_html from mistune.util import escape_url And that was all. Restarted the servers and all is going smoothly All of this steps have been documented in this list by Mark & Stephen whom I'm very grateful. P.S.: As I did some upgrades ago, I didn't have to modify settings.py in the Hyperkitty area to add DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' But if you come from an old mailman/Hyperkitty version, you'll have to include in it. And the it's same if you are using UWSGI, you have to include in your apache config: WSGIPassAuthorization On -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

2 2

Walk-thru for Ubuntu Bionic Mailman 3 Full setup
by kelly.close＠lrewater.com 09 Jul '22

09 Jul '22

I hope this is helpful to the Ubuntu folks out there. Once some critical small things were figured out, turns out it's pretty easy to get Mailman 3 running successfully under Ubuntu 18.04. The linked google doc includes my own walkthru, which includes using a cloud server image for Ubuntu 18.04 and a LAMP setup with Apache 2 and PHP, as well as Python and PostgreSQL, and the mailman3-full package that comes with that Ubuntu distribution. The walk-thru uses Postfix for mail and PostgreSQL for the back end database. https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan… If you use this and see needed corrections or additions, please let me know! ~Kelly

6 21

Sorry to repeat a question, but how do I permanently delete messages, again?
by William Oliver 08 Jul '22

08 Jul '22

I askled this question some months ago, but for the life of me cannot find the response (though there is one). I want to purge some specific emails from the list archives. A user posted what he thought was a personal message to the list, and is embarrased by it, so I told him I couldn't delete emails that were already downloaded onto client machines, but I can delete it so that new users won't be able to see it. But... I can't figure out how to do it. I asked this once before, some months ago, and as I remember there is a command line way of doing it, but not a GUI way. But i can't remember what it was. Thanks! billo

2 2

Problem migrating from Ubuntu packaged Mailman to Virtualenv, including Hyperkitty
by tim＠thecutts.org 07 Jul '22

07 Jul '22

Hi everyone, As we all know, mailman3 got dropped from Ubuntu 22. So I updated the operating system anyway, and decided to switch to a virtualenv setup, keeping the old Debian/Ubuntu database and log locations etc. With some lumps and bumps, this has gone OK; the web interface appears to be working, and I can use the mailman CLI to manipulate the lists. So far so good. However, there do seem to be two problems, which might be linked: 1. If I send a message to my test list, it does not get sent on to any members. I can see the lmtp delivery to mailman. But nothing comes out again. I can see the two test messages in the “shunt” directory 2. Trying to look in the archives for my mailing lists does not work. On the web, I get "An error occurred while processing your request.”, and the log file seems to show a schema error in the hyper kitty table: ERROR 2022-07-07 13:18:41,634 116894 django.request Internal Server Error: /mailman3/archives/list/fairhaven-members(a)thecutts.org/ Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 86, in _execute return self.cursor.execute(sql, params) psycopg2.errors.UndefinedColumn: column hyperkitty_mailinglist.archive_rendering_mode does not exist LINE 1: ...e_policy", "hyperkitty_mailinglist"."created_at", "hyperkitt... ^ Do I need to run a database migration manually? If so, how? I’m not very familiar with Django, it seems a bit hideously complex to me. Are these issues likely to be related, or do I have two things going on here? Regards Tim

3 2

Problem with database change sqlite -> mysql
by moritz both 07 Jul '22

07 Jul '22

Greetings, I am totally new to this list and relatively new to mailman3 and came here because I have a problem I would like to solve soon. I hope somebody has a clue: I am running a really small list site with 10 or so lists, all of them have low traffic and no more than ~70 members. The lists are running on a shared server at uberspace. I followed their guide at https://lab.uberspace.de/guide_mailman-3/ Mailman Core Version GNU Mailman 3.3.5 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.8.13 (default, May 19 2022, 15:06:19) [GCC 9.3.1 20200408 (Red Hat 9.3.1-2)] Since my migration from mm2 to mm3 I see what I consider high loads and excessive i/o and memory usage. My guess is that the main problem is the database backend for mailman, posterious and hyperkitty, which is sqlite. The database is >200MB at the moment (I have not found out why it is so huge, I tried to delete the hyperkitty archives from there and no longer archive messages, but maybe I have not managed to delete all). I take any recommandation for this situation. My current idea is changing the database backend to something else, i.e. mysql. I tried to follow this guide https://www.rockandnull.com/django-dumpdata/ but the "loaddata" command fails. The stack trace is below. Unfortunatelly, I have close to no knowledge of django and don't know why the Email matching query not exists. Will postgres make things easier? Thanks in advance for any help. Moritz Here is the stacktrace: Traceback (most recent call last): File "/home/daneben/.local/lib/python3.8/site-packages/django/db/models/fields/related_descriptors.py", line 173, in __get__ rel_obj = self.field.get_cached_value(instance) File "/home/daneben/.local/lib/python3.8/site-packages/django/db/models/fields/mixins.py", line 15, in get_cached_value return instance._state.fields_cache[cache_name] KeyError: 'starting_email' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "manage.py", line 10, in <module> execute_from_command_line(sys.argv) File "/home/daneben/.local/lib/python3.8/site-packages/django/core/management/__init__.py", line 419, in execute_from_command_line utility.execute() File "/home/daneben/.local/lib/python3.8/site-packages/django/core/management/__init__.py", line 413, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/home/daneben/.local/lib/python3.8/site-packages/django/core/management/base.py", line 354, in run_from_argv self.execute(*args, **cmd_options) File "/home/daneben/.local/lib/python3.8/site-packages/django/core/management/base.py", line 398, in execute output = self.handle(*args, **options) File "/home/daneben/.local/lib/python3.8/site-packages/django/core/management/commands/loaddata.py", line 78, in handle self.loaddata(fixture_labels) File "/home/daneben/.local/lib/python3.8/site-packages/django/core/management/commands/loaddata.py", line 123, in loaddata self.load_label(fixture_label) File "/home/daneben/.local/lib/python3.8/site-packages/django/core/management/commands/loaddata.py", line 190, in load_label obj.save(using=self.using) File "/home/daneben/.local/lib/python3.8/site-packages/django/core/serializers/base.py", line 223, in save models.Model.save_base(self.object, using=using, raw=True, **kwargs) File "/home/daneben/.local/lib/python3.8/site-packages/django/db/models/base.py", line 763, in save_base pre_save.send( File "/home/daneben/.local/lib/python3.8/site-packages/django/dispatch/dispatcher.py", line 180, in send return [ File "/home/daneben/.local/lib/python3.8/site-packages/django/dispatch/dispatcher.py", line 181, in <listcomp> (receiver, receiver(signal=self, sender=sender, **named)) File "/home/daneben/.local/lib/python3.8/site-packages/hyperkitty/signals.py", line 96, in Thread_on_pre_save kwargs["instance"].on_pre_save() File "/home/daneben/.local/lib/python3.8/site-packages/hyperkitty/models/thread.py", line 157, in on_pre_save self.find_starting_email() File "/home/daneben/.local/lib/python3.8/site-packages/hyperkitty/models/thread.py", line 149, in find_starting_email if self.starting_email is not None: File "/home/daneben/.local/lib/python3.8/site-packages/django/db/models/fields/related_descriptors.py", line 187, in __get__ rel_obj = self.get_object(instance) File "/home/daneben/.local/lib/python3.8/site-packages/django/db/models/fields/related_descriptors.py", line 307, in get_object return super().get_object(instance) File "/home/daneben/.local/lib/python3.8/site-packages/django/db/models/fields/related_descriptors.py", line 154, in get_object return qs.get(self.field.get_reverse_related_filter(instance)) File "/home/daneben/.local/lib/python3.8/site-packages/django/db/models/query.py", line 435, in get raise self.model.DoesNotExist( hyperkitty.models.email.DoesNotExist: Problem installing fixture '/home/daneben/mailman-suite/datadump.json': Email matching query does not exist.

3 5

Django errors after deleting a thread
by peter＠chubb.wattle.id.au 06 Jul '22

06 Jul '22

After deleting a thread via the web interface (because it's spam), I get lots of messages from hyperkitty E.g. Internal Server Error: /hyperkitty/list/list@domain/top-threads DoesNotExist at /hyperkitty/list/list@domain/top-threads Thread matching query does not exist. Request Method: GET Request URL: https://example.com/hyperkitty/list/list@domain/top-threads Django Version: 2.2.17 Python Executable: /usr/bin/uwsgi-core Python Version: 3.8.6 Python Path: ['.', '', '/usr/lib/python38.zip', '/usr/lib/python3.8', '/usr/lib/python3.8/lib-dynload', '/usr/local/lib/python3.8/dist-packages', '/usr/lib/python3/dist-packages'] Server time: Wed, 25 Nov 2020 07:12:00 +1100 Installed Applications: ('hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', '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') Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Traceback: File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 34. response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 115. response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 113. response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/lib/view_helpers.py" in inner 135. return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/mlist.py" in overview_top_threads 220. 'threads': mlist.top_threads, File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py" in top_threads 168. return self.cached_values["top_threads"]() File "/usr/lib/python3/dist-packages/hyperkitty/models/common.py" in __call__ 59. return self.get_or_set(*args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py" in get_or_set 376. return [Thread.objects.get(pk=pk) for pk in thread_ids] File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py" in <listcomp> 376. return [Thread.objects.get(pk=pk) for pk in thread_ids] File "/usr/lib/python3/dist-packages/django/db/models/manager.py" in manager_method 82. return getattr(self.get_queryset(), name)(*args, **kwargs) File "/usr/lib/python3/dist-packages/django/db/models/query.py" in get 406. raise self.model.DoesNotExist( Exception Type: DoesNotExist at /hyperkitty/list/devel(a)sel4.systems/top-threads Exception Value: Thread matching query does not exist. Request information: USER: AnonymousUser GET: No GET data POST: No POST data FILES: No FILES data COOKIES: No cookie data

3 4

mailman3 suddenly stopped working after routine package upgrade with "apt update" and "apt upgrade".
by gordon＠dickens.com 05 Jul '22

05 Jul '22

My mailman3 installation is installed in Debian using the Mailman Suite's Virtualenv (venv) instructions (not the Debian mailman3 packages) and has been working great for several months until I recently executed a routine package upgrade with "apt update" and "apt upgrade" after which the mailman3 service quit working with the following error dialog in response to "systemctl start mailman3" # systemctl start mailman3 Job for mailman3.service failed because the control process exited with error code. See "systemctl status mailman3.service" and "journalctl -xe" for details. root@slc:/opt/mailman/venv/bin# systemctl status mailman3 ● mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/mailman3/mailman3.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2022-07-05 10:31:55 EDT; 4s ago Process: 3011826 ExecStart=/opt/mailman/venv/bin/mailman start (code=exited, status=2) CPU: 822ms Jul 05 10:31:54 slc.mailhub4u.com systemd[1]: Starting GNU Mailing List Manager... Jul 05 10:31:55 slc.mailhub4u.com mailman[3011826]: Usage: mailman start [OPTIONS] Jul 05 10:31:55 slc.mailhub4u.com mailman[3011826]: Try 'mailman start -h' for help. Jul 05 10:31:55 slc.mailhub4u.com mailman[3011826]: Error: A previous run of GNU Mailman did not exit cleanly (stale_lock). Try using --force Jul 05 10:31:55 slc.mailhub4u.com systemd[1]: mailman3.service: Control process exited, code=exited, status=2/INVALIDARGUMENT Jul 05 10:31:55 slc.mailhub4u.com systemd[1]: mailman3.service: Failed with result 'exit-code'. Jul 05 10:31:55 slc.mailhub4u.com systemd[1]: Failed to start GNU Mailing List Manager. Then, the command, "systemctl status mailman3" results in: # systemctl status mailman3 ● mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/mailman3/mailman3.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2022-07-05 10:31:55 EDT; 19min ago Process: 3011826 ExecStart=/opt/mailman/venv/bin/mailman start (code=exited, status=2) CPU: 822ms Jul 05 10:31:54 slc.mailhub4u.com systemd[1]: Starting GNU Mailing List Manager... Jul 05 10:31:55 slc.mailhub4u.com mailman[3011826]: Usage: mailman start [OPTIONS] Jul 05 10:31:55 slc.mailhub4u.com mailman[3011826]: Try 'mailman start -h' for help. Jul 05 10:31:55 slc.mailhub4u.com mailman[3011826]: Error: A previous run of GNU Mailman did not exit cleanly (stale_lock). Try using --force Jul 05 10:31:55 slc.mailhub4u.com systemd[1]: mailman3.service: Control process exited, code=exited, status=2/INVALIDARGUMENT Jul 05 10:31:55 slc.mailhub4u.com systemd[1]: mailman3.service: Failed with result 'exit-code'. Jul 05 10:31:55 slc.mailhub4u.com systemd[1]: Failed to start GNU Mailing List Manager. The only reason that I believe that the apt package upgrade caused the problem is because everything stopped working immediately after the package upgrade commands, "apt update" and "apt upgrade" were executed. Looking at the apt logs, the following packages were apparently upgraded: Start-Date: 2022-07-01 13:18:17 Commandline: apt upgrade Requested-By: gordon (1000) Install: linux-image-5.10.0-15-amd64:amd64 (5.10.120-1, automatic) Upgrade: tzdata:amd64 (2021a-1+deb11u3, 2021a-1+deb11u4), linux-image-amd64:amd64 (5.10.113-1, 5.10.120-1), libssl-dev:amd64 (1.1.1n-0+deb11u2, 1.1.1n-0+deb11u3), libssl-doc:amd64 (1.1.1n-0+deb11u2, 1.1.1n-0+deb11u3), libssl1.1:amd64 (1.1.1n-0+deb11u2, 1.1.1n-0+deb11u3), openssl:amd64 (1.1.1n-0+deb11u2, 1.1.1n-0+deb11u3), linux-libc-dev:amd64 (5.10.113-1, 5.10.120-1) End-Date: 2022-07-01 13:19:04 Start-Date: 2022-07-01 13:21:18 Commandline: apt autoremove Requested-By: gordon (1000) Remove: linux-image-5.10.0-13-amd64:amd64 (5.10.106-1) End-Date: 2022-07-01 13:21:22 Otherwise, other than this package upgrade command, nothing changed on my system between the time that mailman3 was working properly and when it stopped working. Does anyone see any potential problems with any of the packages that were upgraded? The logfile, /var/log/syslog, has the following lines immediately after the "systemctl start mailman3" command was executed: Jul 5 11:07:41 slc mailman[3030034]: Usage: mailman start [OPTIONS] Jul 5 11:07:41 slc mailman[3030034]: Try 'mailman start -h' for help. Jul 5 11:07:41 slc mailman[3030034]: Error: A previous run of GNU Mailman did not exit cleanly (stale_lock). Try using --force Jul 5 11:07:41 slc mariadbd[859]: 2022-07-05 11:07:41 1744540 [Warning] Aborted connection 1744540 to db: 'mailman3' user: 'mailman' host: 'localhost' (Got an error reading communication packets) Jul 5 11:07:41 slc systemd[1]: mailman3.service: Control process exited, code=exited, status=2/INVALIDARGUMENT Jul 5 11:07:41 slc systemd[1]: mailman3.service: Failed with result 'exit-code'. As an FYI, I have attempted to start the service using --force, however, it made no difference. BTW, I don't know if this is significant or not but the following error message (or similar message) is displayed often in the logs: slc mariadbd[859]: 2022-07-05 11:07:41 1744540 [Warning] Aborted connection 1744540 to db: 'mailman3' user: 'mailman' host: 'localhost' (Got an error reading communication packets) In any event, does anyone see any other potential causes for why the mailman3 service will not run? Thanks very much! Gordon

2 2

Monthly mailman-web job using a lot of memory
by Andy Smith 04 Jul '22

04 Jul '22

Hi, Is it normal for the monthly job: @monthly www-data [ -f /usr/bin/django-admin ] && flock -n /var/run/mailman3-web/cron.monthly /usr/share/mailman3-web/manage.py runjobs monthly to use nearly 3½GiB of memory? PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 770203 www-data 20 0 4516756 3.4g 1.6g R 99.7 43.5 12:08.00 python3 /usr/share/mailman3-web/manage.py runjo+ I assume it's updating the full text indexes or something. There are around 250k messages in our archives. In the job list I see: appname - jobname - when - help -------------------------------------------------------------------------------- hyperkitty - update_and_clean_index - monthly - Update the full-text index and clean old entries so I'm guessing it's that, but there is also: hyperkitty - update_index - hourly - Update the full-text index which hasn't been noitceably a problem so I wonder why the "and clean old entries" bit is so much more heavyweight, what exactly it dopes and if there's any way to make it lighter on resources? Thanks, Andy

3 7

mailman3 + postfix + dovecot + postfixadmin
by Geoff Nordli 03 Jul '22

03 Jul '22

Hi. Did anyone figure out the issue or have a working configuration with this: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… I am getting the same error, with the same configuration. Issue: Postfix LMTP does not pass messages onto MM3:LMTP. Instead the behavior summary is as follows: Jul 3 11:56:30 mail1 postfix/lmtp[824956]: 5168B20017A: to=<lmtp:[127.0.0.1]:8024@domain.com>, orig_to=<testing(a)domain.com>, relay=mail1.domain.com[private/dovecot-lmtp], delay=0.08, delays=0.03/0.01/0.02/0.01, dsn=5.1.1, status=bounced (host mail1.domain.com[private/dovecot-lmtp] said: 550 5.1.1 <"lmtp:[127.0.0.1]:8024"@domain.com> User doesn't exist: lmtp:[127.0.0.1]:8024@domain.com (in reply to RCPT TO command)) thanks, Geoff

2 2

Emails about moderation are sent to list owners, want them sent to moderators instead
by Elias Rudberg 02 Jul '22

02 Jul '22

Hello, This is about GNU Mailman 3.3.3 (Tom Sawyer). For each list there are both "owners" and "moderators". As I understand it, the idea is that owners have the power to change configuration for the list, while moderators have more limited power, they can only moderate but not change configuration. When an email is sent from a non-member to a list that requires moderation in such a case, an email with subject like "[listname] post from [sender] requires approval" is sent to the list owners. I would like those emails to be sent to moderators instead. The reason why I want it to work that way is that list owners sometimes want to delegate the work of moderating to the moderators. List owners then want to keep the power to change list configuration, but they do not want to be bothered by individual moderation emails. Is there a way to configure mailman3 to make it send moderation emails to moderators instead of owners? Or, have I misunderstood the purpose of "owners" and "moderators"? If so, I would be grateful if someone could explain. / Elias

2 1

uwsgi memory usage
by peter＠chubb.wattle.id.au 29 Jun '22

29 Jun '22

Hi Folks, I think there's a memory leak somewhere in the system. Over time, on a relatively small set of lists, I see the uwsgi process grow and grow until the system OOMs. I'm using the Debian packaged mailman3 suite, on the Unstable distribution. This is version 3.3.3. I've reported the bug to the Debian maintainers (who are overloaded...), but was wondering if others had seen this issue. Is it a Debian issue, a local config issue, or a general problem? Peter C

4 4

Hyperkitty failure "Forbidden" - Please check IP-Address assigned to MAILMAN_ARCHIVER_FROM in the settings file
by christopher.claus＠tgcamberg1848.de 29 Jun '22

29 Jun '22

Hi together, i noticed an error during upgrade, which i did not noticed before, but i see no relation to the upgrade itself. Nevertheless the message is very clear, i am not able to solve this issue. My problem ist, that hyperkitty is not working. In mailman.log, you can see this message: Jun 29 13:38:25 2022 (28) ACCEPT: <006501d88bac$b21201f0$163605d0$@mydomain> Jun 29 13:38:28 2022 (32) HyperKitty failure on https://mydomain/hyperkitty/api/mailman/urls: <html><title>Forbidden</title><body> <h1>Access is forbidden</h1><p>Please check the IP addresses assigned to MAILMAN_ARCHIVER_FROM in the settings file. </p></body></html> (403) I´m using setting_local.py in web-part with following code: # Try to get the address of Mailman Core automatically. MAILMAN_HOST_IP = gethostbyname('mailman-core') MAILMAN_ARCHIVER_FROM = (os.environ.get('MAILMAN_HOST_IP', gethostbyname(os.environ.get('MAILMAN_HOSTNAME', 'mailman-core'))),) Debugging inside my docker-container, this python-code works fine (hostname etc. are correct): bash-5.0# python3 test.py MAILMAN_HOST_IP 172.18.0.4 MAILMAN_ARCHIVER_FROM ('172.18.0.4',) bash-5.0# I also tried to set MAILMAN_ARCHIVER_FROM directly to the IP not using the list, but there was no change. I think, the problem is located at another place and the error-message took me to the wrong place. Does anybody has an idea where to look at? Best regards, chrclaus

1 1

Run 'manage.py makemigrations' to make new migrations
by christopher.claus＠tgcamberg1848.de 29 Jun '22

29 Jun '22

Hello together, at startup of my docker-container with mailman 0.4.3 i got some warnings to apply some data-model-migrations. I´m very unfamilar with python and django and be not sure how to handle it. Are these warnings from mailman and should i migrate the data-model (and how)? Or should i ignore these message for keeping mailman in a safe state? Best regards, chrclaus System check identified some issues: WARNINGS: django_mailman3.MailDomain: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the DjangoMailman3Config.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. django_mailman3.Profile: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the DjangoMailman3Config.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Attachment: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Email: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Favorite: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.LastView: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.MailingList: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Profile: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Tag: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Tagging: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Thread: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.ThreadCategory: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Vote: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. postorius.EmailTemplate: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the PostoriusConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: No migrations to apply. Your models in app(s): 'postorius' have changes that are not yet reflected in a migration, and so won't be applied. Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them.

3 3

docker setup
by epi＠epinux.com 28 Jun '22

28 Jun '22

Hi, attempting to install mailman3 on a remote ubuntu server - my docker-compose file looks like: https://gist.github.com/epifanio/e668b0b7f3709de8063661d947223e2a /opt/mailman/core/mailman-extra.cfg ``` [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 127.0.1.1 lmtp_port: 8024 smtp_host: 127.0.1.1 smtp_port: 25 configuration: /etc/postfix-mailman.cfg ``` opt/mailman/web/settings_local.py ``` EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = '127.0.1.1' EMAIL_PORT = 25 USE_SSL = False DEFAULT_FROM_EMAIL = "mailman(a)lists.libkml.org" SERVER_EMAIL = "mailman(a)lists.libkml.org" DEBUG = True ALLOWED_HOSTS='libkml.org' ``` I know I am still missing the NGNIX/APACHE settings, but trying to access the service at: libkml.org:8000 I get a django error Invalid HTTP_HOST header: 'libkml.org:8000'. You may need to add 'libkml.org' to ALLOWED_HOSTS. but I have the 'libkml.org' to ALLOWED_HOSTS in both `opt/mailman/web/settings_local.py` and in the dockerfile: https://gist.github.com/epifanio/e668b0b7f3709de8063661d947223e2a#file-mail… https://gist.github.com/epifanio/e668b0b7f3709de8063661d947223e2a#file-mail… Can you help me please to understand what I am doing wrong? Thanks!

3 5

What's the difference between (purpose of) reject and ignore
by denis.bitouze＠univ-littoral.fr 27 Jun '22

27 Jun '22

Hi, at a page of the form .../postorius/lists/mylist/held_messages, it is possible to: - Accept - Reject - Ignore messages to be moderated. I didn't find any documentation about the difference between (the purpose of) “Reject” and “Ignore”. Since the list I'm currently moderating suffers from a lot of spammers, I wonder if there is a way to at the same time: - remove the spam from the moderation list (“Reject”? “Ignore”?), - add the emails from the removed spams to the list of banished emails (since copying-pasting each mail to be banished is a pain). Thanks in advance!

5 13

Excluding archives from a mailman3web database backup
by Andy Smith 24 Jun '22

24 Jun '22

Hi, In doing regular database dumps for backup purposes I note that by far the largest quantity of data is HyperKitty's archives. We already keep external archives using the prototype archiver (and some rotation of Maildirs), because we see value in having a simple archive outside of HyperKitty. So, I'd rather not be backing up this data twice. In event of disaster I'd like to be able to do a maildir2mbox on what prototype has written and re-import the resulting mbox file. Is that a realistic proposal? i.e. does a typical maildir2mbox conversion script generate something that "manage.py hyperkitty_import" would be happy with when run on prototype's maildir? If so, is it safe to just exclude every table starting with "hyperkitty_" from the database backup of mailman3web? Dumping only the schema for these, I mean, so that an import would restore empty tables. Thanks, Andy

2 2

How can I clear "Subscription request already pending" status ?
by Axel Rau 24 Jun '22

24 Jun '22

Hi all, I’m getting HTTP Error 409: Subscription request already pending I (as listmaster) would like to subscribe the new member manually, but this fails with above message. Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius

3 2

Docker images with Hyper kitty 1.1.0
by bob B 23 Jun '22

23 Jun '22

Maxking, it looks like the docker images with tags "latest" and more importantly "0.4.2" which I believe is supposed to be the latest version, have mailman-hyperkitty 1.1.0 installed, which does not work with the installed Hyperkitty version, so archiving is broken? is this correct? Any eta on when this will be corrected? it looks like "rolling" has mailman-hyperkitty 1.2.1 but the notes say to consider rolling as beta software. Thanks

3 3

I'm new to mailman
by LIULIANG 23 Jun '22

23 Jun '22

Hello everyone, My name is Liang Liu. Currently, I am a GSoC student and I am developing a list configuration tool for mailman. You can learn more about what I am doing by following the link below. https://wiki.list.org/DEV/Google%20Summer%20of%20Code%202022#List_Configura… If you have good suggestions feel free to send me an email. As time goes on, I maybe asking some questions of what the user needs. And I will be consulting with developers on how to get work done. Hope we have a good summer. Yours sincerely, Liang Liu

1 0

Mails sent by mailman-web runjobs hourly
by Eggert Ehmke 17 Jun '22

17 Jun '22

I get lots of mails originating from the mailman-web runjobs hourly. They are sent to mailman@<mytld>. The content looks like 07:00:03 [Q] INFO Enqueued 12571 07:00:03 [Q] INFO Enqueued 12572 07:00:03 [Q] INFO Enqueued 12573 How can I disable these emails?

4 3

Removing the option to delete a list on the Postorious interface
by Wong, Wesley 14 Jun '22

14 Jun '22

Hi, I have a question on the Postorious web interface in Mailman 3. I have found that a list owner can delete a list through the Postorious interface if they have the role of owner to the list. I wanted to have it either disabled or removed but I am not sure where to look to make changes to it. I would rather remove it from the interface totally so it would be done from the command line. Any help would be greatly appreciated. wesley Wesley Wong Senior Systems Engineer Anderson Computing & Information Services | ACIS 310-206-2571 [ucla-logo---new_smaller] ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: image001.png Replaced multipart/alternative part with first alternative.

2 1

How to configure mailman3-web
by robert.winkler＠bioprocess.org 14 Jun '22

14 Jun '22

Hi, I just installed mailman3-web on my Ubuntu 20.04 LTS web server. Port 8001 is open, the service is running: root@localhost:/etc/mailman3# systemctl status mailman3-web.service ● mailman3-web.service - Mailman3-web uWSGI service Loaded: loaded (/lib/systemd/system/mailman3-web.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2022-06-14 17:05:06 UTC; 47s ago Docs: file:///usr/share/doc/mailman3-web/README.rst Main PID: 30135 (uwsgi) Status: "uWSGI is ready" Tasks: 10 (limit: 2306) Memory: 147.7M CGroup: /system.slice/mailman3-web.service ├─30135 /usr/bin/uwsgi --plugin python3 --ini /etc/mailman3/uwsgi.ini ├─30152 /usr/bin/uwsgi --plugin python3 --ini /etc/mailman3/uwsgi.ini ├─30153 /bin/sh -c python3 manage.py qcluster ├─30155 python3 manage.py qcluster ├─30158 python3 manage.py qcluster ├─30159 python3 manage.py qcluster ├─30160 python3 manage.py qcluster ├─30161 python3 manage.py qcluster └─30162 python3 manage.py qcluster Jun 14 17:05:05 localhost systemd[1]: Starting Mailman3-web uWSGI service... Jun 14 17:05:05 localhost uwsgi[30135]: [uWSGI] getting INI configuration from /etc/mailman3/uwsgi.ini Jun 14 17:05:06 localhost systemd[1]: Started Mailman3-web uWSGI service. in /etc/mailman3/mailman-web.py I changed localhost for my domain:port: MAILMAN_REST_API_URL = 'http://meteomex.com:8001' POSTORIUS_TEMPLATE_BASE_URL = 'http://meteomex.com:8001/mailman3/ and restarted the service. on the server side, it looks fine, the mailman3 DB in postgresql exists. However, I cannot access the web interface, trying, e.g. http://meteomex.com:8001/mailman3/ 'http://meteomex.com/mailman3 'http://meteomex.com:8001 anything I am missing? E.g. concerning the Apache config? Thanks, Robert

2 1

Mailman3 Setup
by George R. Kasica 11 Jun '22

11 Jun '22

Hello: I'm in the process of setting up Mailman3 on Ubuntu 20.04. I have the following Environment, and please ask if I left something needed out: Postfix Apache2 MySQL Mailman3 (all 3 bits mailman3, mailman3-web, python-mailman-hyperkitty) The install SEEMS to have worked, but I'm looking for a guide for setup now. I used to run 2.1 about 18 months ago, but the server failed, and I never reinstalled it. I figured now, with a newish Ubuntu 20.04LTS Server, I'd go the mailman3 route...I've seen MANY posts of issues getting MM3 working with 20.04. Should I go back to 2.1, or what is the best way to get mailman-3 configured? Thank you, George Kasica

4 6

Turned on archiving and it is not working
by bob B 09 Jun '22

09 Jun '22

I normally have archives not enabled on all my lists and I do not even have hyperkitty enabled for them. but I need to turn on archiving for one list and it is not working. I made sure hyper kitty is enabled for the list, and I have private archives enabled. I even restarted my environment (more on that in a moment) and still the list works but nothing gets archived. my mail log shows Jun 09 18:49:10 2022 (28) Exception in the HyperKitty archiver: <html><title>Auth required</title><body> <h1>Authorization Required</h1><p>The archiver key is now File "/usr/lib/python3.8/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message <h1>Authorization Required</h1><p>The archiver key is now <h1>Authorization Required</h1><p>The archiver key is now I am running in docker: my HYPERKITTY_API_KEY is the same in my docker yaml file for mailman-core & mailman-web (I am using an external database) mailman info GNU Mailman 3.3.5 (Tom Sawyer) Python 3.8.10 (default, May 6 2021, 06:30:44) [GCC 9.3.0] Hyperkitty web interface is working and I can log in so it is up HyperKitty version 1.3.5. This used to work when I initially installed, so not sure why it is broken now. Any thoughts on what to do next?

2 4

Validity of membership opt-in
by Julian Kippels 08 Jun '22

08 Jun '22

Hi, If someone joins a mailinglist there is a process where they have to opt in by replying to a welcome mail. I would like to know for how long this opt-in is valid? Or does it never expire? Thanks, Julian Kippels

2 1

Include receipant address as a variable
by chucka＠blackforest-co.com 07 Jun '22

07 Jun '22

I send out a monthly newsletter via MM. To keep traffic smaller the email has a link to the PDF of the newsletter. I need to somehow include a variable (the To: email) as part of the link. ie href = thewebsite/nl.pdf?tomjones(a)email.com That way I can tell A) who is reading the NL and B) popup a notice: Your membership dues have been paid through 2023. Google hasn't been any help - although I'll keep searching. Thanks for any help

2 7

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