- Mailman-users - lists.mailman3.org

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