- Mailman-users - lists.mailman3.org

Mailman3 not working following distribution upgrade from Debian 10 to 11.
by gordon＠dickens.com March 6, 2022

March 6, 2022

I performed a distribution upgrade from Debian 10 Buster (which runs mailman 3.2.1) to Debian 11 Bullseye (which runs mailman 3.3.1) with the command "apt-get full-upgrade -y" and everything apparently worked properly except at the end of the upgrade when the following error dialog was generated by the mailman3-web and mailman3-full post-installation scripts: Setting up mailman3-web (0+20200530-2) ... Determining localhost credentials from /etc/mysql/debian.cnf: succeeded. dbconfig-common: writing config to /etc/dbconfig-common/mailman3-web.conf dbconfig-common: flushing administrative password sed: -e expression #2, char 77: unterminated `s' command dpkg: error processing package mailman3-web (--configure): installed mailman3-web package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of mailman3-full: mailman3-full depends on mailman3-web; however: Package mailman3-web is not configured yet. dpkg: error processing package mailman3-full (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: mailman3-web mailman3-full E: Sub-process /usr/bin/dpkg returned an error code (1) Now, every time that I execute "apt-get upgrade" then I continue to get the above error dialog. Also, the command "dpkg-reconfigure mailman3-web" generates this output: /usr/sbin/dpkg-reconfigure: mailman3-web is broken or not fully installed So, I am now stuck since apt-get is saying that mailman3-web is not configured yet, however, neither apt-get nor dpkg-reconfigure will successfully configure mailman3-web. Does anybody have any idea how to fix this? I would very much appreciate some suggestions. Thanks, Gordon

6 29

Remove login from list subscription page
by bob B March 1, 2022

March 1, 2022

Is there any way to easily remove the login button for the List subscription page? 99% of our list do not use archiving, and log-in just confuses users so We would like for them just to be able to sign up to be on the list.

2 1

Mass un/subscribe optimization?
by Bryan Loniewski Feb. 28, 2022

Feb. 28, 2022

Hi -- We've noticed slowness in mass un/subscribing users; looking through the issue(s) log we see both #419 [1] and #627 [2] open and related. From the cmd line we get better performance, but with the subscriber size on many of our Faculty/Staff/Students ad-hoc lists (think 1k-15K subscribed addresses) and with our number of lists (2600) and unique owners utilizing these actions it would be helpful to optimize the mass actions. We wanted to get some thoughts and guidance on what needs to be optimized/redesigned/fixed? Or is there already something in the works, but needs more time? We may be able to provide resources to encourage and/or assist with any development and/or testing... We run a split core/web setup with Apache,mod_wsgi and MySQL backend (AWS hosted). [1] - https://gitlab.com/mailman/mailman/-/issues/419 [2] - https://gitlab.com/mailman/mailman/-/issues/627

2 1

Migration of archives from Sympa to MM3
by Tom Fillmore Feb. 28, 2022

Feb. 28, 2022

Hi, all - At the moment I have a site that uses Sympa. It has more than 150 lists. Moving existing lists to MM3 looks doable the archives are a different story. Has anyone ever migrated archives from Sympa to MM3? Sorry if this is answered somewhere else... Thanks T Fillmore southern California The earth is but one country and mankind its citizens... - Baha'u'llah

2 2

Migrating archives from mailman2 to mailman3 with attachments
by bob B Feb. 28, 2022

Feb. 28, 2022

So I see the process for migrating an archive from mailman2 to mailman3 https://docs.mailman3.org/en/latest/migration.html.................. i.e python manage.py hyperkitty_import -l foo-list(a)example.com $var_prefix/archives/private/foo-list.mbox/foo-list.mbox but does the migration handle attachments?? attachments are in ..../archives/private/foo-list/attachments. I assume this is if you are upgrading in place? I am migrating to a new server and my plan is to follow these steps but copy the config.pck. and .mbox files to the new server and import them, but then it looks like I need to copy the attachment directory? if so how do I import the attachments to mailman3?

2 1

sending messages in response to posts from non-members
by David Bremner Feb. 27, 2022

Feb. 27, 2022

I'd like to turn off the "bounce messages" sent by mailman to non-members. My reasoning is that most such posts are spammers, and often use forged return-paths / From's, so I end of sending steady stream of backscatter to amazon.com etc... Is this configurable (without postorius) somehow? d

2 2

"autorespond to list owner" setting when importing from mailman2 to mailman3
by bob B Feb. 25, 2022

Feb. 25, 2022

In mailman2 a list was moderated, the admin would also get an email to approve the message, our lists mainly have admins and no moderators. The admins did the moderation. In mailman3 it looks this is now a setting "autorespond to list owner" was this a setting in mailman 2? Anyway, in importing email list from mailman 2 to 3, it appears that this setting is set to "No automatic response", is that right? So does this means if I import all my lists from mailman 2, then the admins will not get moderation notifications until I make that setting change on each list?

2 4

Python 3.9 support
by dancab＠caltech.edu Feb. 25, 2022

Feb. 25, 2022

I just upgraded our Mailman3 system to use Python 3.9. About 6 hours after the deployment there was a PyMySQL error and delivery of messages stopped until I restarted the services. I'm pasting the full stack trace error from mailman.log below. It mentions PyMySQL. We have PyMySQL-1.0.2 installed. Thanks for your help. ---- Dan Caballero Systems Administrator Academic Computing Solutions IMSS - Caltech https://imss.caltech.edu Feb 23 23:27:10 2022 (300) Uncaught runner exception: (pymysql.err.OperationalError) (1053, 'Server shutdown in progress') [SQL: SELECT anon_1.member_id AS anon_1_member_id, anon_1.member__member_id AS anon_1_member__member_id, anon_1.member_role AS anon_1_member_role, anon_1.member_list_id AS anon_1_member_list_id, anon_1.member_moderation_action AS anon_1_member_moderation_action, anon_1.member_address_id AS anon_1_member_address_id, anon_1.member_preferences_id AS anon_1_member_preferences_id, anon_1.member_user_id AS anon_1_member_user_id, anon_1.member_bounce_score AS anon_1_member_bounce_score, anon_1.member_last_bounce_received AS anon_1_member_last_bounce_received, anon_1.member_last_warning_sent AS anon_1_member_last_warning_sent, anon_1.member_total_warnings_sent AS anon_1_member_total_warnings_sent FROM (SELECT `member`.id AS member_id, `member`._member_id AS member__member_id, `member`.`role` AS member_role, `member`.list_id AS member_list_id, `member`.moderation_action AS member_moderation_action, `member`.address_id AS member_address_id, `member`.preferences_id AS member_preferences_id, `member`.user_id AS member_user_id, `member`.bounce_score AS member_bounce_score, `member`.last_bounce_received AS member_last_bounce_received, `member`.last_warning_sent AS member_last_warning_sent, `member`.total_warnings_sent AS member_total_warnings_sent FROM `member`, address WHERE `member`.list_id = %(list_id_1)s AND `member`.`role` = %(role_1)s AND address.email = %(email_1)s AND `member`.address_id = address.id UNION SELECT `member`.id AS member_id, `member`._member_id AS member__member_id, `member`.`role` AS member_role, `member`.list_id AS member_list_id, `member`.moderation_action AS member_moderation_action, `member`.address_id AS member_address_id, `member`.preferences_id AS member_preferences_id, `member`.user_id AS member_user_id, `member`.bounce_score AS member_bounce_score, `member`.last_bounce_received AS member_last_bounce_received, `member`.last_warning_sent AS member_last_warning_sent, `member`.total_warnings_sent AS member_total_warnings_sent FROM `member`, address, user WHERE `member`.list_id = %(list_id_2)s AND `member`.`role` = %(role_2)s AND address.email = %(email_2)s AND `member`.user_id = user.id AND user._preferred_address_id = address.id) AS anon_1] [parameters: {'list_id_1': 'avery-disc.caltech.edu', 'role_1': 1, 'email_1': 'nandrade(a)caltech.edu', 'list_id_2': 'avery-disc.caltech.edu', 'role_2': 1, 'email_2': 'nandrade(a)caltech.edu'}] (Background on this error at: http://sqlalche.me/e/13/e3q8) Feb 23 23:27:10 2022 (300) Traceback (most recent call last): File "/opt/mailmanve/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1276, in _execute_context self.dialect.do_execute( File "/opt/mailmanve/lib/python3.9/site-packages/sqlalchemy/engine/default.py", line 608, in do_execute cursor.execute(statement, parameters) File "/opt/mailmanve/lib/python3.9/site-packages/pymysql/cursors.py", line 148, in execute result = self._query(query) File "/opt/mailmanve/lib/python3.9/site-packages/pymysql/cursors.py", line 310, in _query conn.query(q) File "/opt/mailmanve/lib/python3.9/site-packages/pymysql/connections.py", line 548, in query self._affected_rows = self._read_query_result(unbuffered=unbuffered) File "/opt/mailmanve/lib/python3.9/site-packages/pymysql/connections.py", line 775, in _read_query_result result.read() File "/opt/mailmanve/lib/python3.9/site-packages/pymysql/connections.py", line 1156, in read first_packet = self.connection._read_packet() File "/opt/mailmanve/lib/python3.9/site-packages/pymysql/connections.py", line 725, in _read_packet packet.raise_for_error() File "/opt/mailmanve/lib/python3.9/site-packages/pymysql/protocol.py", line 221, in raise_for_error err.raise_mysql_exception(self._data) File "/opt/mailmanve/lib/python3.9/site-packages/pymysql/err.py", line 143, in raise_mysql_exception raise errorclass(errno, errval) pymysql.err.OperationalError: (1053, 'Server shutdown in progress') The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/opt/mailmanve/lib/python3.9/site-packages/mailman/core/runner.py", line 176, in _one_iteration self._process_one_file(msg, msgdata) File "/opt/mailmanve/lib/python3.9/site-packages/mailman/core/runner.py", line 269, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/opt/mailmanve/lib/python3.9/site-packages/mailman/runners/outgoing.py", line 111, in _dispose self._func(mlist, msg, msgdata) File "/opt/mailmanve/lib/python3.9/site-packages/mailman/mta/deliver.py", line 86, in deliver refused = agent.deliver(mlist, msg, msgdata) File "/opt/mailmanve/lib/python3.9/site-packages/mailman/mta/base.py", line 164, in deliver member = mlist.members.get_member(recipient) File "/opt/mailmanve/lib/python3.9/site-packages/mailman/model/roster.py", line 120, in get_member memberships = self._get_all_memberships(email) File "/opt/mailmanve/lib/python3.9/site-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/opt/mailmanve/lib/python3.9/site-packages/mailman/model/roster.py", line 116, in _get_all_memberships return members_a.union(members_u).all() File "/opt/mailmanve/lib/python3.9/site-packages/sqlalchemy/orm/query.py", line 3373, in all return list(self) File "/opt/mailmanve/lib/python3.9/site-packages/sqlalchemy/orm/query.py", line 3535, in __iter__ return self._execute_and_instances(context) File "/opt/mailmanve/lib/python3.9/site-packages/sqlalchemy/orm/query.py", line 3560, in _execute_and_instances result = conn.execute(querycontext.statement, self._params) File "/opt/mailmanve/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1011, in execute return meth(self, multiparams, params) File "/opt/mailmanve/lib/python3.9/site-packages/sqlalchemy/sql/elements.py", line 298, in _execute_on_connection return connection._execute_clauseelement(self, multiparams, params) File "/opt/mailmanve/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1124, in _execute_clauseelement ret = self._execute_context( File "/opt/mailmanve/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1316, in _execute_context self._handle_dbapi_exception( File "/opt/mailmanve/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1510, in _handle_dbapi_exception util.raise_( File "/opt/mailmanve/lib/python3.9/site-packages/sqlalchemy/util/compat.py", line 182, in raise_ raise exception File "/opt/mailmanve/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1276, in _execute_context self.dialect.do_execute( File "/opt/mailmanve/lib/python3.9/site-packages/sqlalchemy/engine/default.py", line 608, in do_execute cursor.execute(statement, parameters) File "/opt/mailmanve/lib/python3.9/site-packages/pymysql/cursors.py", line 148, in execute result = self._query(query) File "/opt/mailmanve/lib/python3.9/site-packages/pymysql/cursors.py", line 310, in _query conn.query(q) File "/opt/mailmanve/lib/python3.9/site-packages/pymysql/connections.py", line 548, in query self._affected_rows = self._read_query_result(unbuffered=unbuffered) File "/opt/mailmanve/lib/python3.9/site-packages/pymysql/connections.py", line 775, in _read_query_result result.read() File "/opt/mailmanve/lib/python3.9/site-packages/pymysql/connections.py", line 1156, in read first_packet = self.connection._read_packet() File "/opt/mailmanve/lib/python3.9/site-packages/pymysql/connections.py", line 725, in _read_packet packet.raise_for_error() File "/opt/mailmanve/lib/python3.9/site-packages/pymysql/protocol.py", line 221, in raise_for_error err.raise_mysql_exception(self._data) File "/opt/mailmanve/lib/python3.9/site-packages/pymysql/err.py", line 143, in raise_mysql_exception raise errorclass(errno, errval) sqlalchemy.exc.OperationalError: (pymysql.err.OperationalError) (1053, 'Server shutdown in progress') [SQL: SELECT anon_1.member_id AS anon_1_member_id, anon_1.member__member_id AS anon_1_member__member_id, anon_1.member_role AS anon_1_member_role, anon_1.member_list_id AS anon_1_member_list_id, anon_1.member_moderation_action AS anon_1_member_moderation_action, anon_1.member_address_id AS anon_1_member_address_id, anon_1.member_preferences_id AS anon_1_member_preferences_id, anon_1.member_user_id AS anon_1_member_user_id, anon_1.member_bounce_score AS anon_1_member_bounce_score, anon_1.member_last_bounce_received AS anon_1_member_last_bounce_received, anon_1.member_last_warning_sent AS anon_1_member_last_warning_sent, anon_1.member_total_warnings_sent AS anon_1_member_total_warnings_sent FROM (SELECT `member`.id AS member_id, `member`._member_id AS member__member_id, `member`.`role` AS member_role, `member`.list_id AS member_list_id, `member`.moderation_action AS member_moderation_action, `member`.address_id AS member_address_id, `member`.preferences_id AS member_preferences_id, `member`.user_id AS member_user_id, `member`.bounce_score AS member_bounce_score, `member`.last_bounce_received AS member_last_bounce_received, `member`.last_warning_sent AS member_last_warning_sent, `member`.total_warnings_sent AS member_total_warnings_sent FROM `member`, address WHERE `member`.list_id = %(list_id_1)s AND `member`.`role` = %(role_1)s AND address.email = %(email_1)s AND `member`.address_id = address.id UNION SELECT `member`.id AS member_id, `member`._member_id AS member__member_id, `member`.`role` AS member_role, `member`.list_id AS member_list_id, `member`.moderation_action AS member_moderation_action, `member`.address_id AS member_address_id, `member`.preferences_id AS member_preferences_id, `member`.user_id AS member_user_id, `member`.bounce_score AS member_bounce_score, `member`.last_bounce_received AS member_last_bounce_received, `member`.last_warning_sent AS member_last_warning_sent, `member`.total_warnings_sent AS member_total_warnings_sent FROM `member`, address, user WHERE `member`.list_id = %(list_id_2)s AND `member`.`role` = %(role_2)s AND address.email = %(email_2)s AND `member`.user_id = user.id AND user._preferred_address_id = address.id) AS anon_1] [parameters: {'list_id_1': 'avery-disc.caltech.edu', 'role_1': 1, 'email_1': 'nandrade(a)caltech.edu', 'list_id_2': 'avery-disc.caltech.edu', 'role_2': 1, 'email_2': 'nandrade(a)caltech.edu'}] (Background on this error at: http://sqlalche.me/e/13/e3q8)

2 4

Hyperkitty failure?
by Stephen Daniel Feb. 24, 2022

Feb. 24, 2022

Mailman3 people -- Hyperkitty is failing in my new setup. In the log I see messages that look like this: Feb 24 11:43:44 2022 (28621) HyperKitty failure on https://lists.example.com/archives/api/mailman/archive: <html> <head><title>401 Authorization Required</title> /opt/mailman/mm/mailman-hyperkitty.cfg looks like this: [general] base_url: https://lists.example.com/archives api_key: SOMESTRING settings_local.py includes this line: MAILMAN_ARCHIVER_KEY = 'SOMESTRING' and mailman.cfg contains [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /opt/mailman/mm/mailman-hyperkitty.cfg Any suggestions on how to get hyperkitty working? Thanks! -- Steve

2 2

cleanup lost users completly - mailman shell
by Paul Paulchen Feb. 21, 2022

Feb. 21, 2022

Hi community, I was wondering if there is a walk-through for the following issue - or is it even an issue? We got plenty lists with a lot of users come and go from time to time. Thanks to the thread, I understood how to pick on adress and delete them via the mailman shell; https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… >>> um = getUtility(IUserManager) >>> usr = um.get_user('user(a)example.com') >>> um.delete_user(usr) >>> commit() Thanks to this thread, I know how to find the lost souls in our mailman environment https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… >>> um = getUtility(IUserManager) >>> for usr in um.users: ... if len(list(usr.memberships.members)) > 0: ... continue ... adr = usr.addresses[0] ... print(f'Name: {adr.display_name}, Email: {adr.email}, Created: {usr.created_on}') So I can see them now. Is there a technique, to clean them up? To get rid of them out of the system? I am not a python programmer, but I guess there is a way to use, instead of a single user, a list of users in the delete command of the mailman shell? e.g. (sorry if this example leads to any pain for any coder/ programmer) user1(a)example.com user2(a)example.com user3(a)example.com >>> um = getUtility(IUserManager) >>> usr = um.get_user('user1(a)example.com','user2(a)example.com','user3(a)example.com') >>> um.delete_user(usr) >>> commit() Hope I made my intention clear. I want to get rid of the users who don't belong/ or are subscribe to a list anymore. Thanks in advance! Paul

4 3

aborted connection
by Sandor Dibuz Feb. 20, 2022

Feb. 20, 2022

Am I right expecting that such warnings are harmless and probably come from timeouts and/or unterminated connections to the DB? Feb 19 14:15:18 localhost mariadbd[28859]: 2022-02-19 14:15:18 22154 [Warning] Aborted connection 22154 to db: 'mailman3' user: 'mailman3' host: 'localhost' (Got an error reading communication packets) Thank you. Sanyi

2 4

I did something stupid. Can i back out of it?
by William Oliver Feb. 20, 2022

Feb. 20, 2022

So... I run a small mailinglist using mailman3 that has been workiing great for a couple of months. Last week, all my users from gmail got kicked off because gmail decided that the list messages were "unsolicited email". I didn't find out about it until the users hit their mailman3 bounce limit. I *thought* would be seeing all the bounce messages, but apparently not. I didn't see any config settings for "see all the bounce messages" so i thought to myself, "Self, well maybe that's because my mailinglist username doesn't have a mailbox in /home/listname". So, I decided to try that. I created /home/listname/Maildir/* and logged in as fplist to see if it would put mail there. In order to log in as listname, I gave the user listname a password. Then the world ended. The mailinglist works OK for *new* posts, but it is now impossible to *reply* to posts. So, if I post as a member from user(a)somewhere.org to listname(a)example.com, it works. If I hit reply, with the From: line rewritten as listname(a)example.com, it fails. The error I get is: The reported error was “Error performing TLS handshake: An unexpected TLS packet was received.”. My suspicion is that there are two passwords floating around for "listname" -- one in mailman3 and the one in /etc/shadow, but I don't know. In retrospect, this was not my finest moment. But is there an easy way to back out of this? Thanks! billo

2 8

certain msgs not archived
by Sandor Dibuz Feb. 18, 2022

Feb. 18, 2022

Hi good folks, I'm new to the group, so bear with me please. A decade or more with Mm2.1 but recently upgraded to Mm3 so no experiences with this latter. Details: Debian 11.2 (stable), everything installed from deb packages, mariadb10.5, python3.9, mailman3.3.3, hyperkitty1.3.4, etc. everything stock Debian. A few low volume lists, one of them migrated from Mm2.1 but most started newly. Couple of glitches, resolved them most so far. but could not cope with this one yet so I must ask your advice. On one of my maillists certain messages can't seem to make it to the archive. They spread right among list members but stuck in /var/lib/mailman3/archives/hyperkitty/spool and hyperkitty can not handle and archive them due to finding an incorrect string. This is a mailman-web.log excerpt below believed to be relevant but please just tell me if you need further details. I didn't want to flood with longer quotation for now but I can share full Django error email if needed. 12:18:19 [Q] INFO Enqueued 8697 ERROR 2022-02-16 12:18:19,310 5898 django.request Internal Server Error: /mailman3/hyperkitty/api/mailman/archive Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/mysql/base.py", line 71, in execute return self.cursor.execute(query, args) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 209, in execute res = self._query(query) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 315, in _query db.query(q) File "/usr/lib/python3/dist-packages/MySQLdb/connections.py", line 226, in query _mysql.connection.query(self, query) MySQLdb._exceptions.OperationalError: (1366, "Incorrect string value: '\\xF0\\x9F\\x8C\\xB9\\x0D\\x0A...' for column `mailman3web`.`hyperkitty_email`.`conten t` at row 1") The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/decorators/http.py", line 40, in inner return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/mailman.py", line 81, in _decorator return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django/views/decorators/csrf.py", line 54, in wrapped_view return view_func(*args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/mailman.py", line 127, in archive add_to_list(mlist_fqdn, msg) File "/usr/lib/python3/dist-packages/hyperkitty/lib/incoming.py", line 153, in add_to_list email.save() File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 743, in save self.save_base(using=using, force_insert=force_insert, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 780, in save_base updated = self._save_table( File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 873, in _save_table result = self._do_insert(cls._base_manager, using, fields, update_pk, raw) File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 910, in _do_insert return manager._insert([self], fields=fields, return_id=update_pk, File "/usr/lib/python3/dist-packages/django/db/models/manager.py", line 82, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 1186, in _insert return query.get_compiler(using=using).execute_sql(return_id) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1377, in execute_sql cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 67, in execute return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 76, in _execute_with_wrappers return executor(sql, params, many, context) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/utils.py", line 89, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/mysql/base.py", line 71, in execute return self.cursor.execute(query, args) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 209, in execute res = self._query(query) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 315, in _query db.query(q) File "/usr/lib/python3/dist-packages/MySQLdb/connections.py", line 226, in query _mysql.connection.query(self, query) django.db.utils.OperationalError: (1366, "Incorrect string value: '\\xF0\\x9F\\x8C\\xB9\\x0D\\x0A...' for column `mailman3web`.`hyperkitty_email`.`content` a t row 1") ERROR 2022-02-16 12:18:19,310 5898 django.request Internal Server Error: /mailman3/hyperkitty/api/mailman/archive Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/mysql/base.py", line 71, in execute return self.cursor.execute(query, args) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 209, in execute res = self._query(query) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 315, in _query db.query(q) File "/usr/lib/python3/dist-packages/MySQLdb/connections.py", line 226, in query _mysql.connection.query(self, query) MySQLdb._exceptions.OperationalError: (1366, "Incorrect string value: '\\xF0\\x9F\\x8C\\xB9\\x0D\\x0A...' for column `mailman3web`.`hyperkitty_email`.`conten t` at row 1") The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/decorators/http.py", line 40, in inner return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/mailman.py", line 81, in _decorator return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django/views/decorators/csrf.py", line 54, in wrapped_view return view_func(*args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/mailman.py", line 127, in archive add_to_list(mlist_fqdn, msg) File "/usr/lib/python3/dist-packages/hyperkitty/lib/incoming.py", line 153, in add_to_list email.save() File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 743, in save self.save_base(using=using, force_insert=force_insert, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 780, in save_base updated = self._save_table( File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 873, in _save_table result = self._do_insert(cls._base_manager, using, fields, update_pk, raw) File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 910, in _do_insert return manager._insert([self], fields=fields, return_id=update_pk, File "/usr/lib/python3/dist-packages/django/db/models/manager.py", line 82, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 1186, in _insert return query.get_compiler(using=using).execute_sql(return_id) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1377, in execute_sql cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 67, in execute return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 76, in _execute_with_wrappers return executor(sql, params, many, context) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/utils.py", line 89, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/mysql/base.py", line 71, in execute return self.cursor.execute(query, args) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 209, in execute res = self._query(query) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 315, in _query db.query(q) File "/usr/lib/python3/dist-packages/MySQLdb/connections.py", line 226, in query _mysql.connection.query(self, query) Btw. I noticed this yesterday evening and there are 5 msgs stuck this way in spool so far. Thanks for you anticipated help. Sanyi

2 7

Thanks to this very helpful community!
by Stephen Daniel Feb. 18, 2022

Feb. 18, 2022

All -- I want to express my heartfelt thanks to the people on this list who helped me stand up a modest mailman3 server. As of today I have 3 lists with a total of ~150 users running in production on a small VM in google's cloud. This implementation replaces a venerable mailman2 implementation running on servers that are to be decommissioned at some point in the near future. Thanks again! -- Stephen

1 0

FILTER_VHOST = True doesn't work fine with alias_domain
by Élodie BOSSIER Feb. 18, 2022

Feb. 18, 2022

Hello, My mailman3 installation is now functional, but the config "FILTER_VHOST = True" doesn't work fine when I define "alias_domain" for the 2 domains. I need to define that because I need to get "postfix_vmap" file. As you can see, list from others domains are visible on this URL : https://ml.franceserv.fr/postorius/lists/ I would like https://ml.franceserv.fr/postorius/lists/ and https://ml.viticreation.fr/postorius/lists/ with their own lists. Where I should check please to solve this ? Thank you in advance.

2 5

Mailman3-web/Postorius behind Lighttpd
by Élodie BOSSIER Feb. 18, 2022

Feb. 18, 2022

Hi, I'm using Mailman 3.3.3 (Tom Sawyer) on Debian Bullseye 11.2 from packages : #dpkg -l | grep mailman ii mailman3 3.3.3-1 all Mailing list management system ii mailman3-full 3.3.3-1 all Full Mailman3 mailing list management suite (metapackage) ii mailman3-web 0+20200530-2 all Django project integrating Mailman3 Postorius and HyperKitty ii python3-django-mailman3 1.3.5-2 all Django library to help interaction with Mailman3 (Python 3 version) ii python3-mailman-hyperkitty 1.1.0-10 all Mailman3 plugin to archive emails with HyperKitty ii python3-mailmanclient 3.3.2-1 all Python bindings for Mailman3 REST API (Python 3 version) I can access from localhost to http://127.0.0.1:8000/ which move me correctly to http://127.0.0.1:8000/postorius/lists/ and all seem to be correct. But 127.0.0.1:8000 listen only in localhost : #netstat -tanpu | grep 8000 tcp 0 0 127.0.0.1:8000 0.0.0.0:* LISTEN 626175/python3 So I try to use my lighttpd as proxy as recommanded with this config : > scgi.protocol = "uwsgi" > scgi.server = ( > "/" => (( "host" => "127.0.0.1", "port" => 8000, "check-local" => > "disable" )), > ) but it's return me a "502 Bad Gateway". I see nothing on there logs : - /var/log/lighttpd/error.log - /var/log/mailman3/web/error.log - /var/log/mailman3/web/access.log But on the file : /var/log/mailman3/web/mailman-web.log I can see that : > QUERY_STRING > REQUEST_URI/postorius/lists/REDIRECT_STATUS200 > SCRIPT_NAME" 400 - I don't know what I'm doing wrong ... There is a way to solve it with lighttpd or bind the port 8000 to 0.0.0.0 instead 127.0.0.1 (which is not recommanded) ? Thank you in advance. Best regards, Elodie

2 2

High memory usage
by Prasanth Nair Feb. 18, 2022

Feb. 18, 2022

Hi, We are having an issue with high memory usage on our Mailman3 server. Initially, our server had 16GB RAM and the memory usage went up from 5% to 92% within a week. So, we increased the memory capacity to 32GB RAM and we can see that the memory usage is going up in the same pattern. Any idea why it is happening? or any suggestions? Kind regards, Prasanth Nair

5 10

Template Ignored?
by Stephen Daniel Feb. 17, 2022

Feb. 17, 2022

Mailman3 people -- I created a new list, and used postorius to create a template for " list:user:notice:welcome". I then used the mass subscription feature to add myself to the list, having checked "pre-confirmed", "pre-approved", and "pre-verified". I received a welcome message that appears to be the default welcome message. It certainly wasn't what I put into my template. Any suggestions on how I get mailman to use my template? Things I might be doing wrong? Thanks! -- Steve

2 5

changing the main template for subscriptions and more
by Jens Günther Feb. 15, 2022

Feb. 15, 2022

Hey there, in Mailman2 there was a simple link in the moderation-emails, with which I was able to open directly the "held-messages". I know how to manually integrate such a link with the variables of mailman (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) But: How can I change the template for all the lists (respectively maildomains/webdomains) so that I don't have to do this manually for all lists? I searched a bit for the corresponding template, but didn't find it. At the end it only says the following: "At your convenience, visit your dashboard to approve or deny the request." -> here I would like to add the following: "At your convenience, visit your dashboard to approve or deny the request: https://$domain/postorius/lists/$short_listname.$domain/held_messages" Or if someone sees another possibility to get us on the right track, it would be more than welcome, thank you! Kind regards, Jens.

4 7

Help with mailman user and mailman Web users
by Sherin Feb. 15, 2022

Feb. 15, 2022

Hi, I have installed mailman3 server and configured MailmanWeb ( hyperkity + Postorious ) . The service and everything works fine, but I am little bit confuses with the user management in mailman3, 1) I created an owner user for a mailing list using the mailmanclient api tools, # from mailmanclient.client import Client 2) I can't login to the Mailmanweb with this user For further investigation shows the mailman have its own database and the web frontend have its own database too. So my question is how to configure the webfrontend ( hyperkit+ postorious ) to use the accounts logins created from the mailmanclient api from the mailman core database. Or is there a way to use only one user management system ? Any help will be appreciated. -- Sherin

2 1

converting bulk accept_these_nonmembers in migration from mailman 2 to 3
by Lucio Chiappetti Feb. 12, 2022

Feb. 12, 2022

I have been instructed by Mark Sapiro to subscribe to this list to post questions related to mailman3. On Mon, 31 Jan 2022, Mark Sapiro wrote: > On 1/31/22 06:20, Lucio Chiappetti wrote: >> One of the lists of which I am a co-moderator has been moved from >> mailman 2 to 3. Actually the migration has been made operative yesterday (and so we got the first problems ...). Basic background. There are a number of lists within my institution (a nationwide research institution with many seats across our country), some are institutional (all staff subscribed ex officio) and managed by staff in one seat, some other are non-institutional (subscription is optional) and are managed by a few volunteers in other cities different from the seat where the mailman server runs. > In particular, the list settings for *_these_nonmembers are at Settings > -> Message Acceptance, but these settings in particular are deprecated > in Mailman 3 except for regexps. In Mailman 3 the preferred way to say > accept a nonmember is to create a nonmember for that user and set it's > Moderation action to Default Processing. If, a nonmember posts, the > nonmember record is automatically created, Let me explain our case, and how it was managed in mailman2. - originally our staff (of the order of 1000) had addresses like user(a)place.inaf.it or user(a)place.astro.it. Some had even two (say place1.inaf.it and place2.inaf.it), so they subscribed with ONE of their work addresses - later we got addresses like name.surname(a)inaf.it. New users subscribe with this address but MANY of the old ones continue to use the PREVIOUS address. - we implemented a spam filtering policy as follows: - staff (and former staff) can SUBSCRIBE with any address or CHANGE their address. Any subscribed address will be recognised. Mail is NOT held in moderation unless too bulky, or has undisclosed recipients - mail from non members with any address in the .it TLD or in the tng.iac.es domain (where some of our staff work) goes into moderation (this is achieved via regexp in hold_these_nonmembers) - anything else is silently discarded as spam (generic_nonmember_action = discard) - when some staff posts from a non-subscribed address (be it the home address, or one of the alternate addresses described above) it therefore goes into moderation because of hold_these_nonmembers - in mailman2 we could let them pass "manually" (if we recognised the person) or (in case they used an alternate address) tick to add them permanently to accept_these_nonmembers (in one tick) - at the end we got somehow fed up of this but we did NOT want to accept any address of the form ^.+@.+\.inaf.it (which could be forged) but found that we could simply put in accept_these_nonmembers two entries like @list1 @list2 where list1 and list2 are two institutional lists on the same server which contain all permanent and temporary staff or assimilated with their official address (these lists are automagically generated each week) (so at least any VALID EXISTING official address is accepted) What I found now (after the migration done by the administrators of the central seat) is that in mailman3: - accept_these_nonmembers is empty - there are 189 entries listed in Non-members (which look those formerly in accept_these_nonmembers) - hold_these_nonmembers was copied identical with the same regexp's as in mailman2 - I have inspected a few of them and found that they have Administration options Moderation set to List default - the effect of this apparently was that a post from some.guy(a)inaf.it (whose subscription address is guy(a)somewhere.inaf.it) was hold for moderation is this due to a loop with the regexp in hold_these_nonmembers ? the default action would be to let it pass Or should we set Administration options Moderation to Accept immediately ? - if so, how can we do it automatically for all 189 entries ? - or move back the 189 addresses to accept_these_nonmembers ? - or for the future have persons posting with alternate addrresses accepted for the future WITH ONE CLICk ? - AND LAST BUT NOT LEAST would the syntax @list1 in accept_these_nonmembers work in mailman3 ? already putting it back will save a lot of work. Many thanks -- Lucio Chiappetti - INAF/IASF - via Corti 12 - I-20133 Milano (Italy) For more info : http://www.iasf-milano.inaf.it/~lucio/personal.html ------------------------------------------------------------------------ "All that is google does not glitter Nor all who use alpine/procmail are lost"

2 3

moderation notices for list-owner being redirected to mailman address
by Philippe B Feb. 10, 2022

Feb. 10, 2022

We have seen a very strange behavior on 2 separate occasions/lists over the past month. A SENDER(a)SOME.DOMAIN emails OURLIST(a)OUR.DOMAIN, and that post is (correctly) held for moderation. The moderation notification is sent by OURLIST-owner(a)OUR.DOMAIN to OURLIST-owner(a)OUR.DOMAIN, and everything works fine. But in a few very rare cases, at some point during the convoluted delivery path to the mailbox of the actual human owner of OURLIST, the recipient is changed from OURLIST-owner(a)OUR.DOMAIN to mailman(a)OUR.DOMAIN. I am going to paste full headers below (with fake public IPs), but I think that these 2 particular lines highlight the problem: X-MailFrom: OURLIST-bounces+OURLIST-owner=OUR.DOMAIN(a)OUR.DOMAIN X-MailFrom: OURLIST-bounces+mailman=OUR.DOMAIN(a)OUR.DOMAIN because only the first one is present normally. We know from the headers that the recipient gets changed on the Mailman host, but we have no idea why or how, because all the aliases are set up correctly, and there is no connection between OURLIST's (non-)members/etc and mailman(a)OUR.DOMAIN. Do you have any troubleshooting suggestions? Thanks. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Note: ec2-12-34-56-78.us-west-2.compute.amazonaws.com, lists.OUR.DOMAIN, and MAILMAN-SERVER.OUR.DOMAIN are different ways of addressing essentially the same system. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Received: from SMTP-SERVER.OUR.DOMAIN (SMTP-SERVER.OUR.DOMAIN [6.7.8.9]) by MAILMAN-SERVER.OUR.DOMAIN (Postfix) with ESMTP id 2B6E51A288F for <mailman(a)lists.OUR.DOMAIN>; Tue, 1 Feb 2022 07:10:52 -0800 (PST) Received: by SMTP-SERVER.OUR.DOMAIN (Postfix) id E825C207053B; Tue, 1 Feb 2022 07:10:51 -0800 (PST) Delivered-To: mailman(a)OUR.DOMAIN Received: from SMTP-SERVER.OUR.DOMAIN (localhost [127.0.0.1]) by SMTP-SERVER.OUR.DOMAIN (Postfix) with ESMTP id D468B2070A45 for <mailman(a)OUR.DOMAIN>; Tue, 1 Feb 2022 07:10:51 -0800 (PST) X-Spam-Scanned: at OUR-ORGANIZATION on SMTP-SERVER.OUR.DOMAIN by amavisd-new Authentication-Results: SMTP-SERVER.OUR.DOMAIN (amavisd-new); dkim=pass (1024-bit key) header.d=OUR.DOMAIN header.b="********"; dkim=pass (1024-bit key) header.d=OUR.DOMAIN header.b="********" Received: from filter-send ([127.0.0.1]) by SMTP-SERVER.OUR.DOMAIN (SMTP-SERVER.OUR.DOMAIN [127.0.0.1]) (amavisd-new, port 12345) with LMTP id YgQELyXHaR1X for <mailman(a)OUR.DOMAIN>; Tue, 1 Feb 2022 07:10:51 -0800 (PST) Received: from [172.17.0.2] (ec2-12-34-56-78.us-west-2.compute.amazonaws.com [12.34.56.78]) by SMTP-SERVER.OUR.DOMAIN (Postfix) with ESMTP id 9E8DE207053B for <mailman(a)OUR.DOMAIN>; Tue, 1 Feb 2022 07:10:51 -0800 (PST) DKIM-Filter: OpenDKIM Filter v2.11.0 SMTP-SERVER.OUR.DOMAIN 9E8DE207053B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=OUR.DOMAIN; s=unixmail; t=**********; bh=*******************************************=; h=Subject:From:To:Date:List-Id:List-Help:List-Owner:List-Subscribe: List-Unsubscribe:From; b=***************************************************************** ****************************************************************** ****************************************= Received: from SMTP-SERVER.OUR.DOMAIN (SMTP-SERVER.OUR.DOMAIN [6.7.8.9]) by MAILMAN-SERVER.OUR.DOMAIN (Postfix) with ESMTP id B138C1A288F for <OURLIST-owner(a)lists.OUR.DOMAIN>; Tue, 1 Feb 2022 07:10:49 -0800 (PST) Received: by SMTP-SERVER.OUR.DOMAIN (Postfix) id 7766E207053B; Tue, 1 Feb 2022 07:10:49 -0800 (PST) Delivered-To: OURLIST-owner(a)OUR.DOMAIN Received: from SMTP-SERVER.OUR.DOMAIN (localhost [127.0.0.1]) by SMTP-SERVER.OUR.DOMAIN (Postfix) with ESMTP id 676682070A73 for <OURLIST-owner(a)OUR.DOMAIN>; Tue, 1 Feb 2022 07:10:49 -0800 (PST) X-Spam-Scanned: at OUR-ORGANIZATION on SMTP-SERVER.OUR.DOMAIN by amavisd-new Received: from filter-send ([127.0.0.1]) by SMTP-SERVER.OUR.DOMAIN (SMTP-SERVER.OUR.DOMAIN [127.0.0.1]) (amavisd-new, port 12345) with LMTP id j2xEFERoaVLS for <OURLIST-owner(a)OUR.DOMAIN>; Tue, 1 Feb 2022 07:10:49 -0800 (PST) Received: from [172.17.0.2] (ec2-12-34-56-78.us-west-2.compute.amazonaws.com [12.34.56.78]) by SMTP-SERVER.OUR.DOMAIN (Postfix) with ESMTP id 2C264207053B for <OURLIST-owner(a)OUR.DOMAIN>; Tue, 1 Feb 2022 07:10:49 -0800 (PST) DKIM-Filter: OpenDKIM Filter v2.11.0 SMTP-SERVER.OUR.DOMAIN 2C264207053B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=OUR.DOMAIN; s=unixmail; t=**********; bh=*******************************************=; h=Subject:From:To:Date:List-Id:List-Help:List-Owner:List-Subscribe: List-Unsubscribe:From; b=***************************************************************** ****************************************************************** ****************************************= Subject: OURLIST(a)OUR.DOMAIN post from SENDER(a)SOME.DOMAIN requires approval From: OURLIST-owner(a)OUR.DOMAIN To: OURLIST-owner(a)OUR.DOMAIN MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6658935924254827098==" Message-ID: <164372824697.288.9427163605184740636@MAILMAN-SERVER> Date: Tue, 01 Feb 2022 07:10:46 -0800 Precedence: bulk X-Mailman-Version: 3.3.5 List-Id: <OURLIST.OUR.DOMAIN> List-Help: <mailto:OURLIST-request@OUR.DOMAIN?subject=help> List-Owner: <mailto:OURLIST-owner@OUR.DOMAIN> List-Subscribe: <mailto:OURLIST-join@OUR.DOMAIN> List-Unsubscribe: <mailto:OURLIST-leave@OUR.DOMAIN> X-MailFrom: OURLIST-bounces+OURLIST-owner=OUR.DOMAIN(a)OUR.DOMAIN X-MailFrom: OURLIST-bounces+mailman=OUR.DOMAIN(a)OUR.DOMAIN X-Mailman-Rule-Hits: implicit-dest X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-mailman.OUR.DOMAIN-0; nonmember-moderation; administrivia; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header

3 13

Customise Postorius templates?
by Duane Raymond Feb. 8, 2022

Feb. 8, 2022

Hi, I'm looking to do some radical customisation of the Postorius (and Hyperkitty) templates over the next 6 ish months and was wondering if there is a 'best practice' way to do this that will survive updates to MM3. I've searched around and not found much and also tested copying venv/lib/python3.7/site-packages/postorius/templates/postorius/lists/summary.html to var/templates/lists/summary.html As suggested in some posts - but it didn't seem to pick up the customisation - only customisations in the venv path worked - and they get overwritten on update. Is there a 'best' way for this? I'd also like to eventually share them with the community and maybe add them to the repo if people want that....but for now I'll start with my own experiments. (and if there is documentation I have missed for this, let me know!)

5 10

Time Zone Issue in Postorius
by Andy Summers Feb. 8, 2022

Feb. 8, 2022

Hello, I'm encountering an error that sounds similar to this previous thread: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… I've tried setting my TIME_ZONE to 'UTC' in my settings.py and settings_local.py files (and restarting Mailman), but when I check the datetime for a held message in Postorius, the datetime seems to be pushed +8 hours unexpectedly. My Postorius account time zone is set to "US/Pacific". As a workaround, I might be able to find a "wrong" time zone that would possibly reduce the unintentional additional hours difference and show the "correct" time zone in Postorius for the "Held Messages" page, but I don't think this is the right way to fix the issue. I think I've tried setting the TIME_ZONE setting to "America/Los_Angeles" in my settings.py file in place of 'UTC' in the past, but the result was still different than expected. Does anyone know if there are other places besides the mailman settings.py and settings_local.py files where something needs to be set so that I don't get an unintentional extra +8 hours of time difference when looking at messages on the "Held Messages" page of a mailing list? Thank you, Andrew

5 5

Error 500 on held_messages page
by Stephan Krinetzki Feb. 4, 2022

Feb. 4, 2022

Hello all, we now have at least one mailing list (there may be more affected) that generates a 500 error when calling the held_messages page. After looking at the held messages via the mailman shell, we have identified three mails that have neither a subject nor a message body. How can we remove these three mails from the database? This is the mailman shell command we used: mailman shell -l listname(a)lists.example.com <removed> Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. Die Variable 'm' ist die listname(a)lists.example.com Mailingliste >>> msg_db = getUtility(IMessageStore) >>> req_db = IListRequests(m) >>> reqs = list(req_db.held_requests) >>> for req in reqs: ... print('{}: {}'.format(req.id, req.request_type)) ... 32598: 1 [...] 107656: 1 107737: 1 107758: 1 >>> from mailman.app.moderator import handle_message >>> handle_message(m, 107758, Action.discard) >>> reqs = list(req_db.held_requests) >>> for req in reqs: ... print('{}: {}'.format(req.id, req.request_type)) ... 32598: 1 [...] 107656: 1 107737: 1 >>> handle_message(m, 92927, Action.discard) Traceback (most recent call last): File "<console>", line 1, in <module> File "/opt/mailman/mailman-venv/lib64/python3.6/site-packages/mailman/app/moderator.py", line 112, in handle_message key, msgdata = requestdb.get_request(id) TypeError: 'NoneType' object is not iterable >>>

2 4

HELP: mailman send empty mails
by Axel Rau Feb. 4, 2022

Feb. 4, 2022

In one mailing list all posts are empty, just one sentence: The content of this message was lost. It was probably cross-posted to multiple lists and previously handled on another list. What can I do? I'm lost Axel -- PGP-Key: CDE74120 ☀ computing @ chaos claudius

3 2

Docker mailman 3 and upgrading questions
by bob B Feb. 1, 2022

Feb. 1, 2022

I am running mailman 3 in docker and trying to figure out -how to upgrade -can you back out. For example I installed docker with a git pull • git clone https://github.com/maxking/docker-mailman docker images shows REPOSITORY TAG IMAGE ID CREATED SIZE maxking/mailman-web 0.3 9ba9d3d7084d 4 months ago 487MB maxking/mailman-core 0.3 26c920c0094b 4 months ago 178MB **** database is hosted via external database I only installed it a few months ago, am I really on 0.3.0 , I assume I am on 3.0 from 2019 and that is what "git clone https://github.com/maxking/docker-mailman" gets???? looking at the release matrix "https://github.com/maxking/docker-mailman/releases?page=2" It looks like the latest releases are 0.4.1 for core & 0.4.2 for web, How do I upgrade, is it a "git pull" or "docker update" command? If something does not work, is there a way to back out? What version should I go to from 0.3? I am thinking it should be v0.3.12 cause that won't break anything? But how do I do that? The documentation at https://asynchronous.in/docker-mailman/. says

2 1

Is there an example of a complete installation for https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-install (ie. standard installation)?
by matt＠fes.org Feb. 1, 2022

Feb. 1, 2022

What i'm looking for is the directory structure, files, configs of a working mailman3 installation (with passwords/secrets obscured, etc). - /etc/mailman3, /opt/mailman, /etc/nginx, /etc/postfix, etc... I've tried 3 or 4 installations with varying degrees of success. For me, more issues seem related to configuration, not the actual installation. So having an example installation to compare proper configuration (and perhaps file/directory placement) would really help to sanity check what i've installed. Since this installed copy would be created for each release, it would exist at some point. Is it possible this could be made available (with pws/secrets obscured...)? I've seen quite a few threads related to configuration issues...hopefully it would help with those as well.

2 3

National language messages in mm3 notifications
by Ivan Kuznetsov Feb. 1, 2022

Feb. 1, 2022

Hello There is a problem with moderator/administrator notifications used national (non-acsii) characters in templates. Messages came with all non-ascii chars changed to '?' As I can see some parts of customizable text are originated from localized messages (mailman/messages/<country code>/LC_MESSAGES), other from site/domain/list templates. I made some localization/translation of LS_MESSAGES for Russian language via Weblate site and import .po file to test site setup. Web interface messages seems to be ok but email notifications are not. Content-type: and Content-Transfer-Encoding: headers are not suitable for national charsets. Mailman processes has enviroment variable LANG set to ru_RU.UTF-8. Preferred language for site administrator (listmaster) is Russian What am I missing in setup? Return-Path: <test-bounces(a)solvo.ru> [...] Received: from mail-g3-vlan10 (localhost [IPv6:::1]) by mail-g3 (Postfix) with ESMTP id 889784800512D for <kia(a)solvo.ru>; Tue, 18 Jan 2022 00:00:22 +0300 (MSK) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: ????????? ????????????? ???????? ? ?????? ???????? test(a)solvo.ru: 1. From: listmaster(a)solvo.ru To: =?utf-8?b?0JjQstCw0L0g0JrRg9C30L3QtdGG0L7Qsg==?= <kia(a)solvo.ru> Message-ID: <164245320388.3361727.10723274392705308145@mail-g3-vlan10> Date: Tue, 18 Jan 2022 00:00:03 +0300 Precedence: bulk X-Mailman-Version: 3.3.5 List-Id: =?utf-8?b?0KLQtdGB0YLQvtCy0YvQuSDRgdC/0LjRgdC+0Lo=?= <test.solvo.ru> List-Help: <mailto:test-request@solvo.ru?subject=help> List-Owner: <mailto:test-owner@solvo.ru> List-Subscribe: <mailto:test-join@solvo.ru> List-Unsubscribe: <mailto:test-leave@solvo.ru> [...] The test(a)solvo.ru list has 1 moderation requests waiting. ????????? ????????? ????????: ????????????: ikuznetsov(a)solvo.ru Please attend to this at your earliest convenience.

2 3

No resend after delivery bouned
by Axel Rau Jan. 31, 2022

Jan. 31, 2022

My listserver has been blocked with 550 and I received bounce score on <list_add> has been incremented. notifications. After resolving the block issue, I'm now waiting for mailman to resend the mails. Now, after 3 hours, nothing has happened so far. What is wrong here? Axel -- PGP-Key: CDE74120 ☀ computing @ chaos claudius

3 2

Re: Held messages: Long time waiating for response of the Mailman API
by Krinetzki, Stephan Jan. 31, 2022

Jan. 31, 2022

Hi everyone, any news here? We are running with Pyton 3.6 - maybe a Python Upgrade can speed Mailman up? Regards Stephan -- Stephan Krinetzki IT Center Gruppe: Anwendungsbetrieb und Cloud Abteilung: Systeme und Betrieb RWTH Aachen University Seffenter Weg 23 52074 Aachen Tel: +49 241 80-24866 Fax: +49 241 80-22134 krinetzki(a)itc.rwth-aachen.de www.itc.rwth-aachen.de Social Media Kanäle des IT Centers: https://blog.rwth-aachen.de/itc/ https://www.facebook.com/itcenterrwth https://www.linkedin.com/company/itcenterrwth https://twitter.com/ITCenterRWTH https://www.youtube.com/channel/UCKKDJJukeRwO0LP-ac8x8rQ ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: application/pkcs7-signature Name: smime.p7s

5 14

DMARC DNS settings for MM3?
by Jay Hamilton-Roth Jan. 31, 2022

Jan. 31, 2022

Emails from our list are currently being blocked by Google & Yahoo because of the "Dmarc policy of the sender domain" (according to Google Postmaster). Our list doesn't do any munging for "Reply goes to list" and our DMARC Mitigations is set for "No DMARC mitigations" and we're not DMARC Mitigating unconditionally. Given this is our MM3 policy, it's not clear what the DMARC DNS policy should be for consistency (note: we currently don't have a DMARC DNS setting). MM3 documentation doesn't have enough info, and reading up on DMARC Records it's not clear if we should be: v=DMARC1;p=reject;pct=100;rua=mailto:postmaster@ourdomain.com -or- v=DMARC1;p=quarantine;pct=100;ruf=mailto:postmaster@ourdomain.com -or something else- Our DNS' SPF record is: v=spf1 ip4:aa.bb.cc.dd +a +mx ~all [Note: aa.bb.cc.dd is a redacted address] I'd rather not experiment on DMARC record settings for fear of making a bad situation worse. Thanks in advance for any assistance.

2 1

mailman 2.1 or 3.0 (or another MLM)
by nate Jan. 29, 2022

Jan. 29, 2022

Hello mailman users out there - I have been a casual user of mailman for 21 years now I think it is. Most of my lists were super small (my only current lists have no more than 8 members each), super low volume. It's "just worked" over the years, no issues. I have been using Linux since 1996, not a newbie here. 21 years ago I deployed mailman as part of our corporate email and then there were a lot more users. Since that time I just use mailman on my personal server. I did a apt-get dist-upgrade on my system and was surprised to see mailman had vanished. Wasn't expecting that.. not a big deal, or so I thought. I am running Devuan 4, which is based on Debian. Investigating further it seems Debian at some point dropped Mailman 2.1 and started including Mailman 3. OK, not too bad I thought.. I was/am prepared to start my mailing lists from scratch again, manually copy/paste over settings/users/etc. Don't care about archives etc. I setup mailman 2.1 on another Devuan 3.x system and copied my mailman configs over to it, and can view them fine via the mailman cgi scripts through Apache, I was planning on just copy/pasting list settings between the two systems for each list. Roughly 10-15mins into trying to get mailman3 off the ground I just find myself overwhelmed. That doesn't happen often. I'm honestly completely shocked at how it seems the complexity of the system has increased by orders of magnitude. I have been browsing around https://docs.mailman3.org/en/latest/pre-installation-guide.html (and other links on that documentation site) But as much information as there is, to me there really isn't any information there. If that makes sense. I'm sure it doesn't make sense so let me give an example. On this page: https://docs.mailman3.org/en/latest/config-web.html I assume that would lead me to how do I configure the web interface so I can do stuff with it. I setup an admin account, then it goes into scheduled tasks(which appear to be handled by the Debian package already but don't know what these tasks would have to do with a web interface). I tried sending a test email but that failed, I looked at the setting up email portion but it does not give any indication where that config would be stored, a recursive grep on /etc for EMAIL_BACKEND turns up nothing (there is a /etc/mailman3 directory with some files in there). Then it goes into other things like task queues, full text searching, here I am just looking for info on where this web interface is, where is the config, what port does it listen on? Is it a cgi like mailman2? It seems like it could be a standalone service. Then it shows a bunch of other settings, not indicating what file these are stored in(or what directory the file is in), etc etc etc. Debian's own documentation is severely lacking in this department as well, normally I am used to going to /usr/share/doc/<package>/ and there is some useful stuff. There is stuff for mailman3 but it's minimal at best. So I'm thinking mailman3 is not the package for me. I've really appreciated mailman 2.1 (and earlier versions) as I said they always just worked, never had to think about them. I'm sure a lot of good hard work has been put into 3, I just don't recall the last time I looked at a project and just honestly didn't even know where to begin which surprised me so much given my 20+ year history of mailman as a user and as an admin. Is there some document(s) out there that would be more beneficial to me in setting up mailman3? I see that mailman 2 looks like it's still being maintained, I assume mailman3 is the result of python3 code and mailman2 perhaps uses python 2.7? I am unsure on the ability to run mailman2 on a modern Debian-based distro since of course Python 2.7 is pretty obsolete at this point (or maybe Mailman 2.1 doesn't use python I don't recall). I could try to install the older mailman 2.1 package on Devuan 4 and see what happens I don't know if it would be that simple or not. Or is there a better MLM for simple use cases? I used Majordomo back in the 90s and was happy to get onto Mailman from that. Something similar to Mailman 2.1 in features/functionality. Worst case I could just use aliases in my postfix config at the end of the day that is all that is really needed, though I do like some level of access control on who can email the lists(even if nobody outside the list knows the list exists), I've had some of these lists for 2 decades, old habits die hard right? I did some searches for mailing list software on the Debian package archives and saw a few options, nothing really stood out at me as something super interesting yet though. I don't mean to come across as harsh or complaining or anything I'm just here in shock kind of. Thinking about what the best solution for me would be. My mailing lists have been broken for a couple of weeks but that's really not a big deal. thanks nate

6 14

Cannot request password reset: "The e-mail address is not assigned to any user account"
by dave＠aasv.org Jan. 28, 2022

Jan. 28, 2022

I have set up Mailman Core Version GNU Mailman 3.3.5 with Mailman Core API Version 3.1 (Python 3.8.10) using the version 0.40 Docker images. I was able to get things set up and tested by requesting a password reset for the MAILMAN_ADMIN_USER specified in the docker.yaml. Using the web API, I have created several mailing lists and I have added members to these lists also using the web API (most relevant: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) specifying that each member is already pre_verified, pre_confirmed, and pre_approved. The lists themselves seem to be working fine. The problem is when our staff try to reset their password (through Postorious) to get access and do moderation tasks. The error message "The e-mail address is not assigned to any user account" displays no matter which email address I enter (except the one from MAILMAN_ADMIN_USER which works). Using the MAILMAN_ADMIN_USER I can sign in, view the list of all the users, see their Addresses (one each) and Subscriptions, but even after toggling off "Verified" for the staff email address, clicking Update, then turning Verified back on and updating again, I still can't reset the password for that email address from the "forgot pasword" screen. Even tried adding that email address as another list owner. I have not made any API calls specific to adding users because the API documentation says, "Since her email address is not yet known to Mailman, a user is created for her." This does seem to have happened; GET 127.0.0.1:8001/3.1/users does show everyone's display name and unique user_id strings. I have tried using the API to PATCH a temporary password to the user but that didn't fix the inability to reset. The encrypted password does show in the /users/ data reported by the API (where previously there had been none), and a POST to users/<user_id>/login with that password return the 204 status shown to indicate success (instead of 403)... but I can't log in using Postorious with this user's email address and password. I also tried PATCHing the cleartext_password to /users/<email_address> and wasn't able to login or reset after that either. According to the API, each of the users -- webadmin where I can reset the password and staff where I can't -- does have a single address. (In the following, I redacted the API username and password ; changed email addresses, and IP address. And the display name, but left the timestamps and user_ids ) $ curl --user xxxx:xxxx "127.0.0.1:8001/3.1/users/29bf1eef2ee14f39a7990757544f11a9/addresses" {"start": 0, "total_size": 1, "entries": [{"email": "webadmin(a)example.com", "original_email": "webadmin(a)example.com", "registered_on": "2021-11-25T04:20:33.408184", "self_link": "http://1.2.3.4:8001/3.1/addresses/webadmin@example.com", "verified_on": "2021-11-25T04:20:33.960577", "user": "http://1.2.3.4:8001/3.1/users/29bf1eef2ee14f39a7990757544f11a9", "http_etag": "\"394c07148f3fd0479cc582358b63b919fd988e36\""}], "http_etag": "\"a6621373598d299c32aa946fef7e32167d796bf3\""} $ curl --user xxxx:xxxx "127.0.0.1:8001/3.1/users/73235926306843ccb41f288d0464240a/addresses" {"start": 0, "total_size": 1, "entries": [{"email": "staff(a)example.com", "original_email": "staff(a)example.com", "registered_on": "2021-12-15T02:25:24.055741", "self_link": "http://1.2.3.4:8001/3.1/addresses/staff@example.com", "display_name": "Staff Member", "verified_on": "2021-12-15T02:40:04.941153", "user": "http://1.2.3.4:8001/3.1/users/73235926306843ccb41f288d0464240a", "http_etag": "\"f24ba7ca9d71a7f814dc41d70c48ce947c1324be\""}], "http_etag": "\"e8d5b9f3ce0abbc7bbf51c03c69367f82679f93e\""} I am probably missing something, but this second query seems to confirm that the address "staff(a)example.com" is assigned to the user 73235926306843ccb41f288d0464240a and so shouldn't I should be able to request a password reset for "staff(a)example.com"? I've tried tailing all the log files I can find while attempting the reset and am not seeing any error messages, but I don't know exactly where to look. Thank you for any suggestions for what to try next! Dave

3 4

bounce handling in mm3 available?
by Stefan Bauer Jan. 28, 2022

Jan. 28, 2022

Hi, what happens with bounce-mails that are processed by mailmans postfix instance? Jan 24 10:46:03 l01 postfix/lmtp[8432]: DF4AE600623: to=<company-newsletter-bounces(a)lists.company.tld>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.03, delays=0.01/0.01/0/0.01, dsn=2.0.0, status=sent (250 Ok) But the list-owner does not get any notification, nor do i see any bounce-information in the pistorious-gui. How are the bounce-mails handled? Thank you. Stefan

2 4

getting all registered users and their lists
by IOhannes m zmoelnig Jan. 27, 2022

Jan. 27, 2022

hi, TL;DR is there a scriptable way to get all users that have registered in my mailman3 (3.2.1) instance and which lists they are subscribed to (if any)? longer version: we are running Mailman3-3.2.1 as shipped with Debian/buster (i know that this is not the newest version; at this point, please refrain from asking me to upgrade my Debian installation or even to switch to a venv installation of mailman3: i'll eventually do that but right now i've gt a problem to solve :-)) a few weeks ago, we invited a number of people to join a new mailinglist via a link that points to the subscription interface of the list, e.g. <https://lists.example.com/postorious/lists/foo.lists.example.com/> now of course a number of these people had problems with the webinterface, confusing the big "Subscribe" button at the bottom of the page with the much smaller "Sign Up" button in the header (in German this button reads "Registrieren" which has a meaning that is pretty similar to "Subscribe"). people that "Signed up" typically do not understand that they have not been subscribed to any mailinglist (yet), wondering why they do not get any emails. at least this is what we suspect from feedback we got. to fix the situtation, i would like to check which users had this problem (and eventually contact them to explain the problem). for this i would like to get a listing of all users that are not subscribed to any mailinglist. i would also like to query, when a given user has signed up (so i can reduce the number of false positives) how would i do that? ideally i would rather not work on an SQL level. gfdmfas IOhannes

2 3

Inline display of attachments
by Axel Rau Jan. 26, 2022

Jan. 26, 2022

I have turned on HYPERKITTY_RENDER_INLINE_IMAGE and Archive Rendering mode set to Markdown text, but images in JPEG or PDF format are not displayed inline. Should this work or are my expectations to high? Thanks, Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius

3 2

django request error
by tibor.molnar＠waltoninstitute.ie Jan. 26, 2022

Jan. 26, 2022

I recently got postorius web interface stopped with an error, from web log: WARNING 2021-09-29 14:46:47,071 39320 django.request Not Found: /mailman//postorius/lists/ from website: This page either doesn't exist, or it moved somewhere else. I wonder what would be the source of this error / anyone else experienced this error since I haven't changed anything. Regards, Tibor

5 12

Held messages: Long time waiating for response of the Mailman API
by Stephan Krinetzki Jan. 25, 2022

Jan. 25, 2022

Hello, We are using Mailman 3.3.5 with Hyperkitty 1.3.5. Mailman 3 is installed in a venv and deployed using Apache and uwsgi. This works quite well so far, only withheld messages cause us a problem: If we try to approve them via Postorius, the message is delivered to the list immediately, but the success message in Postorius takes a long time - on average the process hangs for three minutes until the message is no longer displayed. We have already adjusted the timeout in gunicorn.cfg, but this does not improve the situation. Are there any tips on how we can speed up the REST API? Or is it even a configuration error? Greetings Stephan

2 3

Re: Hyperkitty 403 Forbidden Error
by Josef Dietl Jan. 23, 2022

Jan. 23, 2022

Dear all, Sorry for coming back to a topic that seems to be done for 18 months now. I'm staring at this issue for a few days now (on and off). But I still get these messages: Jan 19 22:43:27 2022 (149439) HyperKitty failure on https://lists.[...]/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) . and consequently, nothing ends up in the archive. I have checked (among others): - MAILMAN_ARCHIVER_FROM - doesn't make a difference. 127.0.0.1, external IP address, different orders, '*'. (Asterisk makes a difference, see at the bottom) - MAILMAN_ARCHIVER_KEY in mailman-web.py matches api_key in mailman-hyperkitty.cfg (except for the quotes). According to the editor's color coding, the quotes are "right", too. I have removed special characters to circumvent diverging treatment in different environments - I guess it doesn't matter, but wget --user restadmin --password [.] http://localhost:8001/3.1/lists works, too. - ACCOUNT_DEFAULT_HTTP_PROTOCOL = "https" (probably also doesn't matter I'm running a fresh package installation from Debian Bullseye with certificates from Certbot with nginx, so Certbot may have messed with my nginx config, but even that seems to be OK: Yes, Certbot has inserted http->https redirection, but I'd expect that a https base_url and ACCOUNT_DEFAULT_HTTP_PROTOCOL = "https" circumvents that. Mailman info says GNU Mailman 3.3.3 (Tom Sawyer) Python 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] . REST root url: http://localhost:8001/3.1/ Hyperkitty is 1.3.4, Postorious is 1.3.4, too. To provide all possible information, I'm also adding the nginx log that seems to correspond to that request (no other requests at that time, give or take five minutes): Yes, everything yields 403 response codes. [.] - - [19/Jan/2022:22:43:27 +0000] "GET /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&key=[.] HTTP/1.1" 403 175 "-" "python-requests/2.25.1" [.] - - [19/Jan/2022:22:43:27 +0000] "GET /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&msgid=AM0PR0 4MB478573911C2A81B8898527E6C2599%40AM0PR04MB4785.eurprd04.prod.outlook.com&k ey=[.] HTTP/1.1 " 403 175 "-" "python-requests/2.25.1" [.] - - [19/Jan/2022:22:43:28 +0000] "GET /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&msgid=AM0PR0 4MB478573911C2A81B8898527E6C2599%40AM0PR04MB4785.eurprd04.prod.outlook.com&k ey=[.] HTTP/1.1 " 403 175 "-" "python-requests/2.25.1" [.] - - [19/Jan/2022:22:43:28 +0000] "POST /hyperkitty/api/mailman/archive?key=[.] HTTP/1.1" 403 166 "-" "python-requests/2.25.1" [.] - - [19/Jan/2022:22:43:28 +0000] "POST /hyperkitty/api/mailman/archive?key=[.] HTTP/1.1" 403 166 "-" "python-requests/2.25.1" . repeated many times, there seems to be quite a few testmessages in the queue . [.] - - [19/Jan/2022:22:46:50 +0000] "GET /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&key=[.] HTTP/1.1" 403 175 "-" "python-requests/2.25.1" [.] - - [19/Jan/2022:22:46:50 +0000] "GET /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&msgid=AM0PR0 4MB4785430188B9C0E8DF248231C2599%40AM0PR04MB4785.eurprd04.prod.outlook.com&k ey=6xpENHLEHQ0kD53vXt5RpKzPDOsKbcN9 HTTP/1.1 " 403 175 "-" "python-requests/2.25.1" [.] - - [19/Jan/2022:22:46:50 +0000] "POST /hyperkitty/api/mailman/archive?key=[.] HTTP/1.1" 403 166 "-" "python-requests/2.25.1" . again repeated many times . [.] - - [19/Jan/2022:22:46:51 +0000] "GET /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&msgid=AM0PR0 4MB4785430188B9C0E8DF248231C2599%40AM0PR04MB4785.eurprd04.prod.outlook.com&k ey=[.] HTTP/1.1" 403 175 "-" "python-requests/2.25.1" I'd appreciate a new idea where I could look for clues. Thanks a lot, Josef

2 3

Help needed with email deliverability to our list
by Terry Earley Jan. 23, 2022

Jan. 23, 2022

We are looking to hire someone to help us with email deliverability. We are running MM3 Postorius Version 1.3.4. We are having too many bounces, causing cancellations. Our IP address is likely on one or more spam lists even though our list has never sent any spam and every post is moderated. We need help resolving all email deliverability issues. We are seeking professional help and we are willing to pay fair rates. Experts only please. Terry Earley FitEyes

1 0

Lost posting in archives
by Axel Rau Jan. 22, 2022

Jan. 22, 2022

I created a list, did migration from 2.1 and run update_index_one_list. Then I posted a test mail to the list and it got distributed and was seen in the archive. Now 2 days later it does no longer show up in the archive. What is going on here? May this have to do with HYPERKITTY_RENDER_INLINE_IMAGE which I have turned on meanwhile. Clueless, Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius

2 4

How to delete user completely?
by William Oliver Jan. 22, 2022

Jan. 22, 2022

I have installed mailman3 and it's up and running great. However, I noticed that, during a mass subscribe, I mis-typed an address, e.g. name(a)domain.ned rather than name(a)domain.net. I found how to unsubscribe the bad address, but I haven't found a "delete" option under Users or anywhere else. How to I purge a user from the users list? As a related question, in docs.mailman.org, I can find a list member's manual, but I can't seem to find an admin manual. Is there one? Thanks! billo

3 3

Speed/progress of update_index_one_list?
by Philip Colmer Jan. 21, 2022

Jan. 21, 2022

Yesterday, I ran "mailman-web update_index_one_list" against a mailing list. The command output "Indexing 328077 emails" and that is the last I've heard from it. The process is still running but, looking in ~mailman/web/logs, I can't see anything happening related to that list. Is there any way to determine how far this process has got, or what it is actually doing? (Without stopping it) For future indexing, what makes the most difference to the speed? Does it benefit from having multiple cores if I resize the AWS instance to a larger processor? What is the bottleneck for this process? Thank you. Regards Philip

4 7

No module named 'mailman3hyperkitty'
by Axel Rau Jan. 20, 2022

Jan. 20, 2022

Still trying to setup my 1st list. mailman-hyperkitty 1.2.0 is installed. Axel PS: Backtrace 16/Jan/2022:16:43:35 +0000] "GET /3.1/lists/mailman.lists.framail.de HTTP/1.1" 200 373 "-" "GNU Mailman REST client v3.3.3" [16/Jan/2022:16:43:35 +0000] "GET /3.1/lists/mailman.lists.framail.de/roster/owner?fields=email&fields=address&fields=self_link HTTP/1.1" 200 371 "-" "GNU Mailman REST client v3.3.3" [16/Jan/2022:16:43:35 +0000] "GET /3.1/lists/mailman.lists.framail.de/roster/moderator?fields=email&fields=address&fields=self_link HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.3" [16/Jan/2022:16:43:35 +0000] "GET /3.1/lists/mailman(a)lists.framail.de/config HTTP/1.1" 200 3011 "-" "GNU Mailman REST client v3.3.3" 2022-01-16 16:43:35 [FALCON] [ERROR] GET /3.1/lists/mailman.lists.framail.de/archivers => Traceback (most recent call last): File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/falcon/app.py", line 361, in __call__ responder(req, resp, **params) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailman/rest/lists.py", line 405, in on_get archiver_set = IListArchiverSet(self._mlist) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/zope/component/_api.py", line 152, in adapter_hook return sitemanager.queryAdapter(object, interface, name, default) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/zope/interface/registry.py", line 354, in queryAdapter return self.adapters.queryAdapter(object, interface, name, default) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailman/model/mailinglist.py", line 616, in __init__ for archiver in config.archivers: File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailman/config/config.py", line 280, in archivers archiver = call_name(class_path) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailman/utilities/modules.py", line 69, in call_name named_callable = find_name(dotted_name) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailman/utilities/modules.py", line 52, in find_name module = import_module(module_path) File "/usr/local/py_venv/mailman_33/lib/python3.9/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1030, in _gcd_import File "<frozen importlib._bootstrap>", line 1007, in _find_and_load File "<frozen importlib._bootstrap>", line 984, in _find_and_load_unlocked ModuleNotFoundError: No module named 'mailman3hyperkitty' --- PGP-Key: CDE74120 ☀ computing @ chaos claudius

3 6

Problem creating list members using REST API
by Stephen Daniel Jan. 19, 2022

Jan. 19, 2022

Mailman3 experts -- I am trying to subscribe a user to a mailing list via the REST API. This works: Posting to url http://localhost:8001/3.1/members POST payload: { "list_id": "<LISTID>", "subscriber": "d13b0bbb29844eb9af4b38dad7bb3707", } RESULT post of "http://localhost:8001/3.1/members" succeeds with code 202 This works does *not *work Posting to url http://localhost:8001/3.1/members POST payload: { "list_id": "<LISTID>", "subscriber": "d13b0bbb29844eb9af4b38dad7bb3707", "pre_approved": true } RESULT post of "http://localhost:8001/3.1/members" fails with code 500 Any suggestions? As best I can tell, inclusion of *any* boolean types in my JSON causes the error code 500. FWIW I am generating the JSON using go language's JSON package. I noticed in the API doc that the boolean values are represented as 'True' rather than 'true'. So I tried converting all instances of 'true' to 'True' in my encoded json. That produced an http 400 error, as it probably should. Thanks! -- Stephen

3 8

clone a list?
by Dave McGuire Jan. 18, 2022

Jan. 18, 2022

Hi folks. Is there a way to clone or duplicate a list in MM3, i.e. create a list with a different name but other settings etc being identical? Thanks, -Dave -- Dave McGuire, AK4HZ New Kensington, PA

2 2

Mirroring a mailman3 server
by Axel Rau Jan. 17, 2022

Jan. 17, 2022

Hi all, I have 2 list servers (lists4 and lists5) in an HA configuration. Both share a CNAME (lists.framail.de) in DNS. In case of failover, the postgresql server on the peer becomes master and the CNAME is updated to point at the peer. Both database servers are kept à jour by replication. What else must be synced (by rsync)? Currently (the CNAME points at mailman 2.1 server at the peer. While creating a domain, what should I enter into the fields? Mail Host lists.framail.de (currently lists5.lrau.net) Alias Domain listsl.framail.de Web Host lists.framail.de (currently lists5.lrau.net) Any help appreciated, Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius

2 3

REST API for "members" collection?
by Stephen Daniel Jan. 17, 2022

Jan. 17, 2022

Mailman3 People -- I am trying to manage subscriptions via the REST API. Most of my attempts at using the API work. For example, I can get the list of users: For example: http GET request "http://localhost:8001/3.1/users" returns 200 However, attempting to get the "members" collection fails. http GET request "http://localhost:8001/3.1/members" returns 400 The documentation here <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> suggests this should work. Any thoughts? Am I using the wrong URL to get the "members" collection? I also tried using the domain URL/members, but that returned a 404 error code. I've also tried posting a structure like this: { "list_id": "LISTNAME", "subscriber": "swd(a)pobox.com", "pre_verified": true, "pre_confirmed": true, "pre_Approved": true, "send_welcome_message": false, "delivery_mode": "regular", "delivery_status": "by_user" } to the members collection, in an attempt to create a subscription. That got an error code 500 Thanks! -- Stephen

1 1

EMWD Mailing Lists Down
by Sherry Xie Jan. 16, 2022

Jan. 16, 2022

Hi all, I am an EMWD Mailman 3 customer, and I recently realized my mailing lists are no longer working (the last email that went through was sent on December 25, 2021). Emails I send to the lists do not show up in archives or reach subscribers. It seems like others have had this issue before since ownership of the company was transferred following Brian Carpenter's passing – has anyone been able to get in touch with support or get their issues resolved? I've submitted a support ticket but have no idea if this is being monitored. I also have no way to contact the current management team, as only their names were announced in the November 5, 2021 email from Barbara Carpenter. Any help would be greatly appreciated – thanks in advance! Sherry

4 3

Question about adding addresses using the REST API
by Stephen Daniel Jan. 16, 2022

Jan. 16, 2022

Mailman3 experts -- It is clear from many aspects of the documentation that mailman3 may have addresses in its database that are not connected to any user. I would like to create such addresses using the REST API. The REST API documentation does not suggest this is possible, nor does trying an obvious POST request to the addresses collection work (returns a 405 error). The only way I've found to create addresses with the REST API is to create users. The only way I've found to create a standalone address (not linked to any user) is to create a user with that address, unlink the address, then delete the user. Is there a more straightforward way to just create an address with no user? Thanks! -- Stephen Daniel

3 5

nginx configuration on a multitasking server
by David Newman Jan. 16, 2022

Jan. 16, 2022

Couple of questions about the sample nginx configuration given in the venv doc and the Mailman Mailman Suite Documentation v. 3.3 PDF: server { listen 443 ssl default_server; listen [::]:443 ssl default_server; server_name MY_SERVER_NAME; location /static/ { alias /opt/mailman/web/static/; } location / { proxy_pass 127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } ssl_certificate /path-to-ssl-certs/cert.pem; ssl_certificate_key /path-to-ssl-certs/privkey.pem; } 1. At least on my system, the proxy_pass statement will only run without errors if I change this to a fully formed URL, e.g., 'proxy_pass http://127.0.0.1:8000'. Is this a typo in the docs? 2. What document root(s) and alias(es) to use for Postorius and Hyperkitty and the Django admin on a server that also runs other services (e.g., Postfix for non-list mail and Roundcubemail)? With MM2, I use location statements with their own root and aliases: location /mailman { root /usr/lib/cgi-bin; fastcgi_split_path_info (^/mailman/[^/]+)(/.*)$; fastcgi_pass unix:///var/run/fcgiwrap.socket; include /etc/nginx/fastcgi_params; fastcgi_param SCRIPT_FILENAME \ $document_root$fastcgi_script_name; fastcgi_param PATH_INFO $fastcgi_path_info; } location /images/mailman { alias /var/lib/mailman/icons; } location /icons { alias /var/lib/mailman/icons; } location /pipermail { alias /var/lib/mailman/archives/public; autoindex on; } What is the MM3 equivalent way to do this? I think root would be somewhere under /opt/mailman but don't know exactly where, or which locations to point to. Many thanks! dn

2 23

under which uid should uwsgi/manage.py run?
by Axel Rau Jan. 14, 2022

Jan. 14, 2022

My current setup has uid = www gid = www in uwsgi.ini For DB access, I’m using client certs, where the key is only readable for owner, so I have 2 cert locations. One is configured in settings per OPTIONS in DATABASES The other uses the default location .postgresql und the mailman home. Looking at var, I see: (mailman_33) [root@lists5 /usr/local/mailman3/var]# ls -l total 46 drwxr-xr-x 2 mailman www 2 13 Jan. 17:32 archives drwxr-xr-x 2 mailman www 2 13 Jan. 17:32 cache drwxr-xr-x 2 mailman www 2 13 Jan. 17:32 data drwxr-xr-x 2 root www 4 13 Jan. 17:32 etc drwxr-xr-x 3 mailman www 3 13 Jan. 22:22 lists drwxr-xr-x 2 mailman www 4 14 Jan. 10:02 locks drwxr-xr-x 2 mailman www 7 13 Jan. 17:32 logs -rw-rw---- 1 mailman www 6 13 Jan. 17:32 master.pid drwxr-xr-x 2 mailman www 2 13 Jan. 17:32 messages drwxr-xr-x 14 mailman www 14 13 Jan. 17:32 queue drwxr-xr-x 2 mailman www 2 13 Jan. 17:32 templates I could allow write access for group www, but I suspect other problems. What is the recommended setting? Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius

4 6

Issues with importing archives from a particular list
by Prasanth Nair Jan. 14, 2022

Jan. 14, 2022

Hello, We are trying to import archives from Mailman2 to Mailman3. For a particular list, it is not importing all of the messages. We can see that Mailman2 has archives from 2015 to 2022. But, it only imports messages from 2018 to 2022 to the Mailman3 server. It was not giving any errors while importing. All other lists are imported successfully. Any idea what was causing the problem? Kind regards, Prasanth

3 2

REST API authorization failed
by Axel Rau Jan. 13, 2022

Jan. 13, 2022

Hi all, I’m going to do a mailman2->3 migration in a FreeBSD jail. I installed mailman3 in an venv from pypi, along with nginx, uwsgi and exim. The above error happens when I try to open the base url of my server with a browser (is redirected to postorius/lists/) (no errors on admin/ and hyperkitty urls) Same passwords and users in mailman.cfg: [webservice] hostname: localhost port: 8001 use_https: no admin_user: restadmin admin_pass: ??? and in settings.py: MAILMAN_REST_API_URL = 'http://localhost:8001' MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = ??? Its a long password, created as secret key by manage.py Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius

4 8

One bounce, 5 bounce counts
by Henrik Rasmussen Jan. 13, 2022

Jan. 13, 2022

I recently upgraded Mailman to GNU Mailman 3.3.4 (Tom Sawyer) that once again handles bounces. Thank you. In my setup, Mailman is with Maxking's Docker image maxking/mailman-core:0.3, and a Postfix outside Docker handling incoming and outgoing mails. Since the upgrade some list administrators have expectedly complained about every time they reenable subscribers, they are disabled again. I have explained to them why they are disabled and why they may be disabled again when re-disabled. My problem, though, is that some subscribers may be disabled even they are able to receive mails (confirmed with sendmail -bv), and I have been looking at one subscriber in particular. 1. Can there be (i'm not saying there are, maybe it's my lack of knowledge) somthing regarding Mailman? 2. And what would the appropeiate per list bounce settings, if not default? Actual example: * Mailman sent seemly 6 mails to a member on January 6th. * I see one bouce message D1426CE22A in Postfix log that was delivered back to Mailman * I see that Mailman is counting the bounce score from 1 to 5, one at the time, but that was day after receiving the bounce, and no other mails have been sent to the user on the 7th nor received as bounce on the 7th. I suspect that it must have been in the Postfix queue until then, but I wonder why that could be - but could be. * The bounce would be in the Postfix queue until sent to Mailman and thus removed from the Postfix queue. == /var/log/maillog == Jan 3 09:05:42 lstapp01pl postfix/smtp[10293]: EA1CC73105: to=recipient(a)example.com<mailto:heidi.ryssel@regionh.dk>, relay=rghhehspamfw001.regionh.dk[185.211.204.236]:25, delay=2.2, delays=0.14/0.03/0.1/1.9, dsn=2.0.0, status=sent (250 Ok: queued as 16A9084006E) Jan 3 11:27:35 lstapp01pl postfix/smtp[27118]: 0AD2F73117: to=recipient(a)example.com<mailto:heidi.ryssel@regionh.dk>, relay=rghhehspamfw002.regionh.dk[185.211.204.237]:25, delay=0.79, delays=0.14/0.03/0.15/0.47, dsn=2.0.0, status=sent (250 Ok: queued as C2CCDF20052) Jan 6 09:09:45 lstapp01pl postfix/smtp[2132]: EFAA673126: to=recipient(a)example.com<mailto:heidi.ryssel@regionh.dk>, relay=rghhvhspamfw002.regionh.dk[185.211.204.239]:25, delay=0.31, delays=0.09/0.01/0.07/0.14, dsn=2.0.0, status=sent (250 Ok: queued as 38094120005E) Jan 6 09:10:41 lstapp01pl postfix/smtp[2132]: 33F6373126: to=recipient(a)example.com<mailto:heidi.ryssel@regionh.dk>, relay=rghhehspamfw001.regionh.dk[185.211.204.236]:25, delay=0.35, delays=0.08/0/0.06/0.21, dsn=2.0.0, status=sent (250 Ok: queued as 86A0B840075) Jan 6 13:37:31 lstapp01pl postfix/qmgr[28946]: D1426CE22A: from=recipient(a)example.com<mailto:heidi.ryssel@regionh.dk>, size=11551, nrcpt=1 (queue active) Jan 6 14:06:43 lstapp01pl postfix/smtp[16749]: 89A68D5699: to=recipient(a)example.com<mailto:heidi.ryssel@regionh.dk>, relay=rghhvhspamfw001.regionh.dk[185.211.204.238]:25, delay=0.35, delays=0.09/0/0.07/0.2, dsn=2.0.0, status=sent (250 Ok: queued as D97EC37C0072) Jan 6 15:04:23 lstapp01pl postfix/smtp[6124]: A46527312C: to=recipient(a)example.com<mailto:heidi.ryssel@regionh.dk>, relay=rghhehspamfw002.regionh.dk[185.211.204.237]:25, delay=0.65, delays=0.12/0.03/0.03/0.48, dsn=2.0.0, status=sent (250 Ok: queued as 44ABBF2008C) == /opt/mailman/var/logs/bounce.log == Jan 07 03:36:38 2022 (25) Member recipient(a)example.com<mailto:heidi.ryssel@regionh.dk> on list listname.lists.example.com, bounce score = 1. Jan 07 03:36:56 2022 (25) Member recipient(a)example.com<mailto:heidi.ryssel@regionh.dk> already scored a bounce on list listname.lists.example.com today. Jan 07 03:37:27 2022 (25) Member recipient(a)example.com<mailto:heidi.ryssel@regionh.dk> already scored a bounce on list listname.lists.example.com today. Jan 07 03:54:04 2022 (25) Member recipient(a)example.com<mailto:heidi.ryssel@regionh.dk> already scored a bounce on list listname.lists.example.com today. Jan 07 03:58:10 2022 (25) Member recipient(a)example.com<mailto:heidi.ryssel@regionh.dk> on list listname.lists.example.com, bounce score = 2. Jan 07 04:05:04 2022 (25) Member recipient(a)example.com<mailto:heidi.ryssel@regionh.dk> already scored a bounce on list listname.lists.example.com today. Jan 07 04:25:08 2022 (25) Member recipient(a)example.com<mailto:heidi.ryssel@regionh.dk> already scored a bounce on list listname.lists.example.com today. Jan 07 04:51:22 2022 (25) Member recipient(a)example.com<mailto:heidi.ryssel@regionh.dk> on list listname.lists.example.com, bounce score = 3. Jan 07 05:04:20 2022 (25) Member recipient(a)example.com<mailto:heidi.ryssel@regionh.dk> on list listname.lists.example.com, bounce score = 4. Jan 07 05:05:22 2022 (25) Member recipient(a)example.com<mailto:heidi.ryssel@regionh.dk> already scored a bounce on list listname.lists.example.com today. Jan 07 22:55:06 2022 (25) Member recipient(a)example.com<mailto:heidi.ryssel@regionh.dk> on list listname.lists.example.com, bounce score = 5. Jan 07 22:55:06 2022 (25) Disabling delivery for recipient(a)example.com<mailto:heidi.ryssel@regionh.dk> on list listname.lists.example.com by bounce Jan 07 22:55:06 2022 (25) Member recipient(a)example.com<mailto:heidi.ryssel@regionh.dk> on list listname.lists.example.com, bounce score 5 >= threshold 5, disabling delivery. Regards, Henrik Rasmussen

2 1

Time Zone Problem In Postorius
by Brian Carpenter Jan. 13, 2022

Jan. 13, 2022

I have the server TZ set to EST. I have the TZ for Postfix set to EST. I have the following set in my settings_local.py file: TIME_ZONE = 'America/New_York' USE_TZ = True However messages showing up in the pending moderation queue box shows UTC date. I am seeing this behavior in Affinity as well so I figured it is either a Mailman core setting or perhaps database? Can anyone shed light on that? Brian

5 6

Re: [Mailman-Users] Re: Member posting to a list but address not in membership list.
by Mark Sapiro Jan. 13, 2022

Jan. 13, 2022

On 1/12/22 7:42 PM, Adam Morris wrote: > Hi Mark, > I've looked in all these places and the address isn't anywhere. (please keep the thread on the list) Then the address that's posting isn't what you think it is or something in your installation is broken. As I said, it could be that Reply-To: or Sender: is the list member, but depending on list settings, these things get overwritten in mail from the list, so you can't really know. If something is broken, you need to discuss this with your hosting provider who, unfortunately, may be no help. Many, not all, cPanel hosts offer mailman because it comes with cPanel, but actually know nothing about Mailman. See https://wiki.list.org/DOC/Mailman%20and%20CPanel > On 13-January-2022 11:31, Mark Sapiro wrote: >> On 1/11/22 7:51 PM, Adam Morris wrote: >>> I have someone who is posting to a list I run. >>> I subscribed them originally but their address doesn't show up in the >>> list of members so I can't change moderation status etc. >>> Where else could I look to find their address? >> >> >> The first check on a post is if any of the address in From:, Reply-To: >> or Sender: headers or the envelope sender is a list member, i.e. in >> the web admin Membership List. If so, that member's moderation is >> applied. If not, the next check is if the From:the *_these_nonmembers >> lists under Privacy options... -> Sender filters and finally Privacy >> options... -> Sender filters -> generic_nonmember_action. >> >> If a post to the list is being accepted without being held for >> moderation, either some address in From:, Reply-To: or Sender: headers >> or the envelope sender is in the Membership List with `mod` unchecked, >> or the From: or possibly Sender: address is in accept_these_nonmembers >> or generic_nonmember_action is Accept. >> > > -- > > Adam Morris > Mobile: 0414 431105 > Email, iMessage & FaceTime > adam(a)damorris.com > -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Issues with international characters (replaced by ?) when mail is send as text/html
by Michal Soltys Jan. 12, 2022

Jan. 12, 2022

Hi, I have noticed that any mail send with text/html, e.g. with following headers: Content-Language: en-US-large Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit is slightly transformed by mailman3 - the body is put into its own part, but all the international letters are replaced by question marks. Having searched the list I tried: 1) adding following to mailman.cfg: [language.master] description: English (USA) charset: utf-8 enabled: yes [language.en] description: English (USA) utf8 charset: utf-8 enabled: yes 2) changing preferred language of a mailing list to something else via shell, e.g.: m.preferred_language = 'pl' 3) changed default_language to 'pl' in mailman.cfg 4) Ensured all relevant glibc locales are generated (not sure if that matters though in this case) None of this seems to have any positive result - all mails, whether under 'pl' or 'en' setting still get all non-ascii chars replaced with question marks (in html case, probably(?) in any case where it becomes multipart). Any ideas what to do so html mails are passed without filtering out their characters ? Do I have to recreate all mailing lists under new [language.en/master] settings ?

2 5

Mailman3 is wrongly display name a list member
by Allan Hansen Jan. 11, 2022

Jan. 11, 2022

All, I got an issue with one subscriber (multiple lists). When I subscribe 'A' <a(a)foo.com>, Mailman3 changes it to 'B' <a(a)foo.com>. I went into Django and added the name 'B' to the subscriber's account (the name was empty). I then unsubscribed <a(a)foo.com> from the lists and resubscribed 'A' <a(a)foo.com>. The subscription again lists as 'B' <a(a)foo.com>. This brings up a previous discussion of display names on this list, but I have not been able to find any solution to the need to change Mailman3's display names for a subscriber. It is beyond weird that unsubscribing, setting the account display name and resubscribing the member fishes back up the old and wrong display name. What can I do to help this member? Yours, Allan

3 5

Howto: Mass import of nonmembers in several lists?
by Paul Paulchen Jan. 11, 2022

Jan. 11, 2022

Hi MM3 community, got a, perhaps easy question. Following situation, got 8 lists and up to 20 nonmember users missing to the list. The massimport with postorius is only for members, as far as I can use it (Postorius Version 1.3.4). So without adding all nonmembers with postorius step by step 8x20 times, there is an easier way to do it. I thought so, because the import21 command did this as well when we migrated to mailman3. I read about the command "mailman addmembers" https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… I am guessing, that I need to create a file like in the example of the addmembers, adding all my nonmember users with their email addy. But how can I add/ tell the command in this massimport that the new members are nonmembers in the existing lists?! Hope I explained my case properly. I appreciate your responds! Thanks in advance. - Paul

2 2

Newbie hyperkitty question
by Stephen Daniel Jan. 11, 2022

Jan. 11, 2022

Mailman users -- I am setting up a new mailman3 installation, and this is my first experience with the suite. All of the software is up and running, but I cannot tell if hyperkitty is actually running. When I look at my test mailing list, two archive options are available, hyperkitty and "prototype", and both are enabled. I can see that my email is being archived, but I think "prototype" is what is doing the archiving. I see that a test message will end up in /opt/mailman/mm/var/archives/prototype/<LISTNAME>@<LISTDOMAIN.org>/new/164.... and nowhere else. This suggests that "prototype" is archiving, but hyperkitty is not. So, this opens up a raft of questions on hyperkitty: - How do I tell if hyperkitty is actually running? - Does hyperkitty have a web-UI for admins or users? How would I access it? - I can not find any documentation on hyperkitty, other than installation instructions and change logs. Does documentation exist? - How do I set policies on how long archives are kept? - Assuming I want to back up my archives, what do I need to back up? Thanks for your help! -- Stephen Daniel

3 5

Only held_messages for 1 (of 3) list has "Mailman REST API not available" message.
by Duane Raymond Jan. 10, 2022

Jan. 10, 2022

Hi everyone, Today my stable mailman3 server started having web access problems. It specifically applies to only one of three lists on the mailman server (one of the others use the same domain name) and only to the held_messages page as admin. It displays the "Mailman REST API not available..." message despite the other two lists displaying it fine. I've rebooted the server and mailman core, but the problem remains (which is what I've seen suggested on this forum for the same error message so far). I've been running a stable mailman3 server for the last 9 months and only updating the security patches for the the underling OS (Debian 10 with postgresql and nginx), I've encountered a problem that just seemed to appear today (wish no recent changes on the server). Any suggestions or diagnosis to resolve it? Duane

2 4

modify subscription page by mailinglist?
by Lars Schimmer Jan. 10, 2022

Jan. 10, 2022

Hi Is it (easy) possible to modify the subscription page individual per mailinglist? If so, since which version? And how? Is there a guide? Thank you. MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

3 4

Still unable to get mailman3 working on Ubuntu 20.04 LTS
by Michael Heseltine Jan. 10, 2022

Jan. 10, 2022

Hi all, after many more attempts, I've still failed to find any set of instructions that can install mailman3 on an Ubuntu 20.04 LTS server of mine. I've recently switched to a new server without any previous installation (apart from an apache web server) so that I can follow the instructions provided in https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 to the letter, if possible. But still, I run into an error I do not understand. I have followed the instructions until this point: > # pip install importlib_resources==1.1.0 > Once the above packages are installed run “mailman info” in your virtual environment. That will install Mailman core into your /opt/mailman/mm/var directory. (I had to add "apt install libmemcached-dev" to the instruction for "pip install psycopg2-binary" to succeed.) Then, I run "mailman info", but get an error message: > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/sqlalchemy/engine/default.py", line 508, in connect > return self.dbapi.connect(*cargs, **cparams) > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/psycopg2/__init__.py", line 122, in connect > conn = _connect(dsn, connection_factory=connection_factory, **kwasync) > sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "localhost" (::1), port 5432 failed: FATAL: password authentication failed > for user "mailman" > connection to server at "localhost" (::1), port 5432 failed: FATAL: password authentication failed for user "mailman" This suggests that the connection to postgresql fails, but if I test this using # psql --user mailman and type in the password listed in settings_local.py, I can login fine. I've also changed the port number in that configuration from '' to '2222', but the connection is still made to port 5432, which suggests to me that my call to mailman info uses another set of connection parameters provided elsewhere. Where can this be found? How will I be able to run "mailman info" w/o error and continue the installation as detailed in https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 ? Any help is appreciated. Happy new year, Michael.

4 25

Bulk changes to delivery mode and moderation action
by David Newman Jan. 8, 2022

Jan. 8, 2022

I fat-fingered a command in the Postorius UI and accidentally unsubcribed all members of a list. Oops. Have added them back using Mass operations/Mass subscribe but this raised three questions: 1. In Users/Members, moderation action for the newly resubscribed users shows as "None". Is there a method, either in the UI or the command line, to change this to "Default processing" for all users? 2. Although Delivery Mode shows as "Regular" for all users in Users/Members list, clicking on a member's name shows all options such as delivery status, delivery mode, etc., as undefined. Similar question: How to set subscriber options for all members in one go? 3. As a subscriber to this list, I received email notification that I'd been unsubscribed. Where is the control for enabling/disabling subscription notifications? Settings/Member Policy/Un-subscription Policy is set to Confirm, but I don't think that's relevant here since I unsubscribed users as the Django superuser. Thanks. dn, chastened

2 7

unwanted chunked delivery
by mm3-omf＠sh.werbittewas.de Jan. 7, 2022

Jan. 7, 2022

hello, we've a mailing-list with currently 81 recipients running with debian-dist mailman3 3.3.3-1. every post to this list will be chunked into one delivery with 60 recipients and one delivery with 21 recipients. we've searched a bit and found a config-option "max_recipients" for bulk-transfers, but we haven't set it and (as we understand the explaination for this option) then there should be no limit in one transfer to the MTA. nevertheless, we've tried to set it to a high value, but even this doesn't change anything in behaviour. any search for '60' within mailman3 gives no relevant results. could someone tell us, where the limit of 60 comes from and how we could change it to unlimited? thanks. omf

2 3

[Mailman-Users] Listservers currently hosted with EMWD - urgent request for assistance
by Stephen J. Turnbull Jan. 7, 2022

Jan. 7, 2022

Note: Reply-To set to mailman-users(a)mailman3.org. Please check that any replies are addressed to that list, and not mailman-users(a)python.org. Jonathan, FWIW, I haven't heard anything. I have 3 students submitting MS/PhD theses in less than (checks watch) 18 hours, but after that I'll see if I can find out anything. I wouldn't bet on it, though, as I don't think anyone here has a connection to the Carpenter family or whoever is left of the EMWD staff. I assume you have checked the emwd.com website? > We have our listservers hosted with EMWD which stopped working on > 23 December. What does "stopped working" mean? I assume that list traffic is no longer being forwarded to subscribers, but perhaps other services are working. It may help if you can answer the following questions. 1. Are you using the GNU Mailman-supplied Postorius/HyperKitty combination for administration and archiving, or EMWD's proprietary "Harmony" (Affinity/Empathy) platform? 2. Can you see archives (if any)? 3. Can you log in to the administrative interface? 4. Is mail to the lists being returned to sender, or just disappearing into the void? 5. You mention an automated response in a later message. Is that to an email you sent, or from a web-based issue-tracking system? What does it say about the current status of EMWD services, if anything? Regards, Steve > We have since found out the devastating news that > Brian Carpenter passed away last year. Brian was really helpful > when we moved our listservers from a legacy system to hosting on > the EMWD platform. My sincere condolences to his family and > friends. > > As we can no longer get a response from EMWD about our listserver issue I was wondering if any one else in this community could help. > > Many thanks. > > Jonathan > > Jonathan Ashby > ICT Strategic Communications Project Manager > Londonwide LMCs and Londonwide Enterprise Ltd > Working days: Tuesday and Wednesday > Direct dial: 020 3818 6228 > Mobile: 07768 109601 > Fax: 020 7383 7442 > Email: jonathan.ashby(a)lmc.org.uk > Web: www.lmc.org.uk > Twitter: @LondonwideLMCs > > > > ---------------------------- > Visit www.lmc.org.uk/coronavirus-covid-19 for the latest official resources and guidance on covid-19. > > Remember that you can use WhatsApp and FaceTime for online consultations as well as the usual online tools. > 🌲 Think of the environment. Do you really need to print this email? > This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please accept our apologies and notify the sender. > > The registered and office address for Londonwide Local Medical Committees Limited is: Tavistock House South, Tavistock Square, London WC1H 9LG. Registered in England No: 6391298. > > Londonwide Enterprise Limited is a wholly owned subsidiary of Londonwide Local Medical Committees Limited. Londonwide Enterprise Limited is registered at: Tavistock House South, Tavistock Square, London WC1H 9LG. Registered in England No. 6990874. Londonwide Enterprise Limited is registered as a Company Limited by Shares. VAT no: 130 1454 66. > > Londonwide Local Medical Committees Limited and Londonwide Enterprise Limited do not provide legal or financial advice and thereby excludes all liability howsoever arising in circumstances where any individual, person or entity has suffered any loss or damage arising from the use of information provided by Londonwide Local Medical Committees Limited and Londonwide Enterprise Limited in circumstances where professional legal or financial advice ought reasonably to have been obtained. > > Londonwide Local Medical Committees Limited and Londonwide Enterprise Limited provide guidance and support to GPs and practice teams in the Londonwide area. Additionally Londonwide Local Medical Committees Limited provides representation to GPs and practice teams in the Londonwide area. Londonwide Local Medical Committees Limited and Londonwide Enterprise Limited strongly advises individuals or practices to obtain independent legal or financial advice. > > ------------------------------------------------------ > Mailman-Users mailing list -- mailman-users(a)python.org > To unsubscribe send an email to mailman-users-leave(a)python.org > https://mail.python.org/mailman3/lists/mailman-users.python.org/ > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ > https://mail.python.org/archives/list/mailman-users@python.org/

2 2

Request for help with configuring "from" headers in mailman3 list
by Stephen Daniel Jan. 6, 2022

Jan. 6, 2022

Mailman3 users -- I am in the process of migrating a set of mailing lists from a very old privately operated server running mailman2 to a VM in Google's cloud (GCP) running mailman3. I have mailman3 up and running in GCP. However, VM's in GCP are not permitted to send emails. To work around this I configured postfix relay SMTP traffic through sendgrid.com. I chose Sendgrid because they offer a free service for low volume users. This works well for emails generated by the mailman3 system. However, it does not work for the list traffic itself. Sendgrid requires that the "From:" address on any email reference an authenticated domain. In the old mailman2 implementation, emails sent by mailman are listed as From: <human name via LISTNAME> LISTNAME(a)LISTDOMAIN.org Reply-to: <human name> sender(a)senderdomain.com (the original email's sender) Sendgrid would be happy with this, because LISTDOMAIN.org is a validated domain. However, in my mailman3 implementation, the From: header lists the original email's sender. Sendgrid rejects this because the original email's sender's address is not one of the validated domains. How do I configure mailman3 to generate headers in the same style as the old mailman2 implementation? Thanks! -- Stephen Daniel

2 2

Request for help debugging a hyperkitty connection issue
by Stephen Daniel Jan. 6, 2022

Jan. 6, 2022

Mailman folk -- I've recently completed a complete install of the mailman3 suite on a Debian VM in Google Cloud (GCP). I used the excellent directions given here: https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 Most things appear to work. Postorius is working, and I can create accounts, email lists, etc. I have two problems. One is with getting list mail out of GCP. I am working on that. The issue I don't know how to address is a problem with hyperkitty. Nothing is being archived. When I send an email through my test list, this message shows up in the mailman log: Jan 04 11:57:26 2022 (806) Exception in "hyperkitty" archiver Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connection.py", line 175, in _new_conn (self._dns_host, self.port), self.timeout, **extra_kw File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/util/connection.py", line 73, in create_connection for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM): File "/usr/lib/python3.7/socket.py", line 748, in getaddrinfo for res in _socket.getaddrinfo(host, port, family, type, proto, flags): socket.gaierror: [Errno -2] Name or service not known This triggers a bunch more tracebacks. Then I get this: Jan 04 11:57:27 2022 (797) Connection to HyperKitty failed: HTTPSConnectionPool(host='www.XXXXX.dev <http://www.xxxxx.dev/>', port=443): Max retries exceeded with url: /archives/api/mailman/archive (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f2114e14e10>: Failed to establish a new connection: [Errno -2] Name or service not known')) Jan 04 11:57:27 2022 (797) Exception in the HyperKitty archiver: HTTPSConnectionPool(host='www.XXXXX.dev <http://www.xxxxx.dev/>', port=443): Max retries exceeded with url: /archives/api/mailman/archive (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f2114e14e10>: Failed to establish a new connection: [Errno -2] Name or service not known')) Jan 04 11:57:27 2022 (797) Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connection.py", line 175, in _new_conn (self._dns_host, self.port), self.timeout, **extra_kw File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/util/connection.py", line 73, in create_connection for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM): File "/usr/lib/python3.7/socket.py", line 748, in getaddrinfo for res in _socket.getaddrinfo(host, port, family, type, proto, flags): socket.gaierror: [Errno -2] Name or service not known I think this second error is just mailman3 reporting that it had trouble with hyperkitty because of the first error. How can I get more information about what connection is being attempted when this failure occurs? Thanks! -- Stephen Daniel

2 2

Postorius & multi domain
by Gelpi Andrea Jan. 6, 2022

Jan. 6, 2022

Hi, on a fresh debian 10 (mail server) I added mailman3 with: apt-get install mailman3-full dpkg-reconfigure mailman3 dpkg-reconfigure mailman3-web The server name is webserver-A Then I log in in webserver-A/mailman3 as a superuser I created a domain for webserver-A and domain-A The I created a list-A Then I created a second domain for webserver-B and domain-B Then I added to apache config a virtual host for webserver-B I log in webserver-B as the some superuser of webserver-A and I created a list-B But when I list the lists I can see both under webserver-A and webserver-B. The some problem with archiving hyperkitty. I search internet for a while and I discovered that using FILTER_VHOST = True seems to solve the problem. >From posotrius config page: FILTER_VHOST Filter the list of available lists in Postorius and Hyperkitty depending on the domain they are being currently served from. Mailman 3 supports multiple domains in a single installation. But it doesn't work. I got err 500 form apache. Were can I find an explanation or a how to configure the system to have 2 webserver with different domains working on the some server as it was with mailman 2? P.S.: I upgrade postorius to V. 1.3.2 and djando V 2.2.12 using the packages in testing distribution. The debian 10 official postorius package is too old (1.2.24) and does not support FILTER_VHOST Thanks in advance - -- Gelpi ing. Andrea ************************************************** I documenti vitali dimostreranno la loro vitalitˆ spostandosi spontaneamente da dove li avevate lasciati a dove non riuscirete a trovarli. **************************************************

4 13

Hipperkitty failing to archive messages in a list
by Guillermo Hernandez (Oldno7) Jan. 6, 2022

Jan. 6, 2022

First of all, best wishes and Happy New Year for everybody. Two days ago I had to reinstall all mailman3 related apps in a mailman 3 server (I tried to upgrade just hipperkitty, but it went bad). At first, all seemed running as before, but I just noted that the messages are not being archived. I did not change any config. Now the log is showing ERROR 2022-01-03 12:22:15,654 7165 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-03 12:22:15,674 7165 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-03 12:22:15,791 7165 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-03 12:22:16,208 7165 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-04 11:44:55,644 30518 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header ERROR 2022-01-04 11:44:55,664 30518 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header ERROR 2022-01-04 11:44:56,478 30518 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header ERROR 2022-01-04 11:44:56,620 30518 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header ERROR 2022-01-04 11:44:56,647 30518 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header (it's a very low traffic list: just two messages in two days) I do believe I did the upgrade/reinstall procedure as in previous upgrades (using pip: it's a system wide installation, not using dockers or venv), but seems that I did something wrong The messages are being delivered normally, but it fails archiving Before I make a bigger hole for myself, where to look for? Versions installed: HyperKitty 1.3.5 mailman 3.3.5 mailman-hyperkitty 1.2.0 mailmanclient 3.3.3 postorius 1.3.6 uWSGI 2.0.19.1 Mailman Core Version GNU Mailman 3.3.5 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.7.9 (default, Nov 30 2020, 10:49:53) [Clang 10.0.1 (git@github.com:llvm/llvm-project.git llvmorg-10.0.1-0-gef32c611a -- ___________________________________________ 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 8

Re-enable member after bouce processed disable
by Henrik Rasmussen Jan. 5, 2022

Jan. 5, 2022

Recently I upgraded Mailman to GNU Mailman 3.3.4 (Tom Sawyer) (Postorius: 1.3.5 and HyperKitty: 1.3.4) which is now processing bounces. When a member have been disabled due to bounces, how is the member re-enabled? I would guess it would be under the "Users -> Members -> Member options -> Delivery status", but theses are both (Enabled and disabled) unchecked, not indicating whether or not the member is either or. How do I or the list admins re-enable a bounce-disabled member? Regards, Henrik

2 3

Healthchecks and Django
by Philip Colmer Jan. 5, 2022

Jan. 5, 2022

Hello We have a number of Mailman 3 servers running on AWS infrastructure. To help us maintain that, we're using Route 53 Health Checks to alert us when something stops responding. For the MM3 servers, we're probing "/mailman3/lists/". We've observed that when a server gets patched during a maintenance window, it will get rebooted and there is a phase where Django responds to web queries but the underlying MM3 services aren't quite in place yet. As a result, we then get emails from Django telling us about the service not being available. Given the number of AWS health checkers, that can result in quite a few emails ... Is there another URL we could use to check the health of a MM3 server without triggering the emails during service startup? Or, if not, is there a way of stopping Django from sending out the emails? We'd get alerted of a problem via AWS anyway, so I'm not too worried about not receiving the Django emails. Thank you. Philip

2 5

If you delete a list but not the HyperKitty archive
by Philip Colmer Jan. 5, 2022

Jan. 5, 2022

It seems that if you delete a list from the "Delete" option on a list's management page, the corresponding HyperKitty archive does not get deleted. That seems fair enough ... but now I wondering how HyperKitty manages visibility access to the archive when the list was private. HyperKitty certainly *seems* to have some knowledge of who was subscribed to a list as attempting to access a private archive with an account that wasn't subscribed prior to the list being deleted does deny access with "This mailing list is private. You must be subscribed to view the archives." But logging in as the server admin, going to the archive URL and then clicking on "Manage subscription" gives me a "Page not found" error ... which isn't too surprising as the list has been deleted. It suggests, though, that it isn't possible to manage access to the *archive* after the list has been removed. So ... should the archive be deleted when the list is deleted and it is a bug that it isn't? Or is it expected that access to the archive is "frozen" once a list is deleted? Many thanks. Philip

2 2

is there a mailman command/setting to periodically clean archives?
by William Oliver Jan. 4, 2022

Jan. 4, 2022

Thanks to everyone's help, mailman3 is up and running for me on two servers with three lists, and they all work as far as I can see. I'm sending out invitations to users tomorrow. Yayy. Up until today, I had been stuck using a plugin in Joomla, which was not the best solution. I'm tickled pink, and my users will be, too. Now I'm just playing and tinkering a bit. I'd like to delete all my archives that are more than a certain age, e.g. more than a week old. I can easily do that with a cron job, deleting old files in /opt/mailman/mm/var/archives/prototype/testlist(a)example.com/* which is, as far as I can see the only place archive emails live. However... I was wondering if there was some mailman command or config variable that would accomplish this without using cron. billo

3 4

Strange behaviour when SSL (https) is activated
by fr-mm3＠tourde.org Jan. 4, 2022

Jan. 4, 2022

Hi, I do a fresh install of Mailman3 and Mailman3-web on Debian 11 and all seems working fine using non-ssl access. But if I activate SSL on the web server, I'm unable to login. I go to the /admin, prompted for the user/pass, and got a Firefox error page saying "Échec de la connexion sécurisée". Main django account was created with: mailman-web createsuperuser --username XXXX --email xxxx(a)xxxx.xx extract of /var/log/mailman3/web/mailman-web.log : [pid: 103142|app: 0|req: 40/40] 192.168.200.252 () {48 vars in 1039 bytes} [Mon Jan 3 11:26:32 2022] GET /accounts/login/ => generated 9321 bytes in 37 msecs (HTTP/1.1 200) 7 headers in 429 bytes (1 switches on core 0) Mon Jan 3 11:26:40 2022 - uwsgi_response_write_headers_do(): Broken pipe [core/writer.c line 248] during POST /accounts/login/ (192.168.200.252) OSError: write error [pid: 103142|app: 0|req: 41/41] 192.168.200.252 () {54 vars in 1008 bytes} [Mon Jan 3 11:26:40 2022] POST /accounts/login/ => generated 0 bytes in 704 msecs (HTTP/1.1 302) 9 headers in 0 bytes (1 switches on core 1) All is working fine on non-ssl connection. Any hint appreciated ;)

3 5

Held for notification - runner exception: 'ascii' codec can't encode character
by Seth Seeger Jan. 3, 2022

Jan. 3, 2022

Hello all, Happy new year! I have a case where a user (set to be moderated), posts a message. She got the appropriate email back saying she was being held for moderation. However, the moderator did not get the email. I found the following block in mailman.log: Dec 28 19:37:44 2021 (33) Uncaught runner exception: 'ascii' codec can't encode character '\u2019' in position 5: ordinal not in range(128) Dec 28 19:37:44 2021 (33) Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/lib/python3.8/site-packages/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/python3.8/site-packages/mailman/runners/incoming.py", line 79, in _dispose process(mlist, msg, msgdata, start_chain) File "/usr/lib/python3.8/site-packages/mailman/core/chains.py", line 79, in process link.function(mlist, msg, msgdata) File "/usr/lib/python3.8/site-packages/mailman/chains/hold.py", line 234, in _process text = MIMEText(expand(template, mlist, substitutions), File "/usr/lib/python3.8/email/mime/text.py", line 42, in __init__ self.set_payload(_text, _charset) File "/usr/lib/python3.8/email/message.py", line 315, in set_payload payload = payload.encode(charset.output_charset) UnicodeEncodeError: 'ascii' codec can't encode character '\u2019' in position 5: ordinal not in range(128) Dec 28 19:37:44 2021 (33) SHUNTING: 1640720264.0541506+b139f885caa9444586b43093a09991b7c19581e6 There are two owners listed, one of them is also listed as the moderator. "mailman version" says: GNU Mailman 3.3.4 (Tom Sawyer) We are running from Docker. I can send you the pck file offline if that would help. Thank you, Seth

2 4

HyperKitty failure
by horvath.arpad.szfvar＠gmail.com Jan. 2, 2022

Jan. 2, 2022

Hi, I try to connect mailman3 to hyperkitty, but there is no success so far. You can see the details below. How can I solve the problem? As I have several domain name (like lists.xxx.hu, xxx.hu, yyy.hu) on the same server, so I guess localhost won't work. In mailman-hyperkitty.cfg there is a line: base_url: http://lists.xxx.hu/hyperkitty/ /etc/mailman3/mailman-web.py includes "*" in ALLOWED_HOSTS I have an error message in /var/log/mailman3/mailman.log Dec 30 21:41:23 2021 (126976) HyperKitty failure on http://lists.xxx.hu/hyperkitty/api/mailman/archive: (405) Dec 30 21:41:23 2021 (126976) Exception in the HyperKitty archiver: Dec 30 21:41:23 2021 (126976) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message raise ValueError(result.text) ValueError In /var/log/mailman3/web/mailman-web.log WARNING 2021-12-30 20:41:23,816 127032 django.request Method Not Allowed (GET): /hyperkitty/api/mailman/archive [pid: 127032|app: 0|req: 101/101] 109.230.236.204 () {38 vars in 592 bytes} [Thu Dec 30 20:41:23 2021] GET /hyperkitty/api/mailman/archive?key=lHzJB%2FzfSWUrbPKZ84JNSlLXHVyCDt8T => generated 0 bytes in 1 msecs (HTTP/1.1 405) 6 headers in 189 bytes (1 switches on core 0) WARNING 2021-12-30 20:41:23,854 127032 django.request Method Not Allowed (GET): /hyperkitty/api/mailman/archive On Debian 11, I have these packages ii mailman3 3.3.3-1 all Mailing list management system ii mailman3-full 3.3.3-1 all Full Mailman3 mailing list management suite (metapackage) ii mailman3-web 0+20200530-2 all Django project integrating Mailman3 Postorius and HyperKitty ii python3-django-mailman3 1.3.5-2 all Django library to help interaction with Mailman3 (Python 3 version) ii python3-mailman-hyperkitty 1.1.0-10 all Mailman3 plugin to archive emails with HyperKitty Thanks, Arpad

3 8

signup / registration error - permissions and cert chains
by David Newman Jan. 1, 2022

Jan. 1, 2022

I'd like for regular (non-admin) list subscribers to be able to manage their subscription preferences and view list archives. However, when new users attempt to create logins from the Postorius "Sign Up" page, the server returns the error pasted below, and displays a "server error" page to users. If I'm reading the error correctly, this is related to an inability to verify the cert chain. The /etc/mailman3/settings.py file points to the same cert and key files used by Nginx, Postfix, and Dovecot. Since TLS works OK with these other services, it appears the cert and key are valid. (Viewing the cert in a web browser also supports this.) The keyfile has 0400 permissions. I tried changing this to 0640 and making the keyfile owned by root:mailman. Even after restarting mailman3 and mailmanweb the same error occurs. (Permissions in the cert and key directories and above are not blocking access.) The etc/mailman3/settings.py file includes these settings: EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_PORT = 25 EMAIL_HOST_USER = 'dnewman(a)networktest.com' EMAIL_HOST_PASSWORD = 'wouldnt-you-like-to-know' EMAIL_USE_TLS = 'True' EMAIL_SSL_CERTFILE = '/etc/ssl/certs/myhost.crt' EMAIL_SSL_KEYFILE = '/etc/ssl/private/myhost.key' But this might only be for email, not Postorius/Django. I checked the Mailman Web docs and settings reference but didn't see anything relevant on either page. https://docs.mailman3.org/en/latest/config-web.html https://docs.mailman3.org/projects/mailman-web/en/latest/settings.html What additional configuration is needed to allow regular users to create and manage their own accounts? Thanks. dn ERROR 2021-12-30 16:03:53,787 436935 django.request Internal Server Error: /accounts/signup/ Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/venv/lib/python3.9/site-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/opt/mailman/venv/lib/python3.9/site-packages/django/utils/decorators.py", line 43, in _wrapper return bound_method(*args, **kwargs) File "/opt/mailman/venv/lib/python3.9/site-packages/django/views/decorators/debug.py", line 76, in sensitive_post_parameters_wrapper return view(request, *args, **kwargs) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/views.py", line 230, in dispatch return super(SignupView, self).dispatch(request, *args, **kwargs) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/views.py", line 74, in dispatch response = super(RedirectAuthenticatedUserMixin, self).dispatch( File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/views.py", line 204, in dispatch return super(CloseableSignupMixin, self).dispatch(request, *args, **kwargs) File "/opt/mailman/venv/lib/python3.9/site-packages/django/views/generic/base.py", line 97, in dispatch return handler(request, *args, **kwargs) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/views.py", line 102, in post response = self.form_valid(form) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/views.py", line 248, in form_valid return complete_signup( File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/utils.py", line 209, in complete_signup return perform_login( File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/utils.py", line 175, in perform_login send_email_confirmation(request, user, signup=signup, email=email) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/utils.py", line 346, in send_email_confirmation email_address.send_confirmation(request, signup=signup) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/models.py", line 62, in send_confirmation confirmation.send(request, signup=signup) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/models.py", line 169, in send get_adapter(request).send_confirmation_mail(request, self, signup) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/adapter.py", line 464, in send_confirmation_mail self.send_mail(email_template, emailconfirmation.email_address.email, ctx) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/adapter.py", line 136, in send_mail msg.send() File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/mail/message.py", line 284, in send return self.get_connection(fail_silently).send_messages([self]) File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/mail/backends/smtp.py", line 102, in send_messages new_conn_created = self.open() File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/mail/backends/smtp.py", line 67, in open self.connection.starttls(keyfile=self.ssl_keyfile, certfile=self.ssl_certfile) File "/usr/lib/python3.9/smtplib.py", line 772, in starttls context = ssl._create_stdlib_context(certfile=certfile, File "/usr/lib/python3.9/ssl.py", line 787, in _create_unverified_context context.load_cert_chain(certfile, keyfile) PermissionError: [Errno 13] Permission denied

3 6

multiple sites on a mailman3 server question
by William Oliver Dec. 29, 2021

Dec. 29, 2021

So, I have successfully installed mailman3 and it's working great. However, the way it works now, if someone goes to the domain website, he or she will get the mailman page. I'd prefer that it work something like: My www.example.com goes to a home page lists.example.com goes to the mailman3 page mail.example.com goes to a roundcube page I'm using nginx, and this is the first time I've set up an nginx server (I have traditionally done apache), and I'm still figuring out the syntax. My sites-available file is below, for the domain emergenus.com. The behavior I'm getting is that if I go to mail.emergenus.com, it still redirects to mail.emergenus.com/mailman3/lists, but gives a 404 page not found. If I go to lists.emergenus.com, it redirects to lists.emergenus.com/mailman3/lists and gives the nice postorius page, and works fine. So, I'm trying to figure out how to stop that redirect. When I look at my nginx access.log file for mail.emergenus.com, I see: 174.212.104.153 - - [28/Dec/2021:21:03:21 -0500] "GET /mailman3/lists/ HTTP/1.1" 404 188 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.93 Safari/537.36" Aha! says I. My ip address is 203.159.80.234, not 174.212.104.153. Thus, uwsgi (I think) is sneaking in there and taking over regardless of what I'm trying to do. Is there a way to tell mailman to only take over for lists.emergenus.com and not for www.emergenus.com or mail.emergenus.com? Here's my uwsgi.ini (without then env= PYTHONPATH change discussed in another thread: # /etc/mailman3/uwsgi.ini # [uwsgi] # Port on which uwsgi will be listening. http-socket = 0.0.0.0:8000 # If running uwsgi from the virtual environment ... virtualenv = /opt/mailman/venv/ module=mailman_web.wsgi:application # Add to python import path. pythonpath = /etc/mailman3/ # The default settings module. env = DJANGO_SETTINGS_MODULE=settings # Setup default number of processes and threads per process. master = true processes = 2 threads = 2 # Setup the django_q related worker processes. attach-daemon = /opt/mailman/venv/bin/mailman-web qcluster # Setup the request log. req-logger = file:/opt/mailman/web/logs/uwsgi.log # Log qcluster commands separately. logger = qcluster file:/opt/mailman/web/logs/uwsgi-qcluster.log log-route = qcluster uwsgi-daemons # Last log and it logs the rest of the stuff. logger = file:/opt/mailman/web/logs/uwsgi-error.log Here's my /etc/nginx/sites-enabled/emergenus.com looks like: server { root /var/www/html2; index index.html index.htm index.nginx-debian.html; server_name emergenus.com, mail.emergenus.com, www.emergenus.com; location /{ try_files $uri $uri/ =404; } ##### added 12/19 listen 443 ssl default_server; listen [::]:443 ssl default_server; ########## ssl_certificate /etc/letsencrypt/live/emergenus.com/fullchain.pem; # managed by Certbot ssl_certificate_key /etc/letsencrypt/live/emergenus.com/privkey.pem; # managed by Certbot include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot } server { root /var/www/html; index index.html index.htm index.nginx-debian.html; server_name lists.emergenus.com; location /{ proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; # proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Server $host; proxy_set_header X-Forwarded-Proto $scheme; proxy_redirect off; } listen 443 ssl ; listen [::]:443 ssl ; location /static/ { alias /opt/mailman/web/static/; } ########## ssl_certificate /etc/letsencrypt/live/emergenus.com/fullchain.pem; # managed by Certbot ssl_certificate_key /etc/letsencrypt/live/emergenus.com/privkey.pem; # managed by Certbot include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot } server { if ($host = mail.emergenus.com) { # return 301 https://$host$request_uri; return 301 https://mail.emergenus.com; } # managed by Certbot if ($host = www.emergenus.com) { return 301 https://$host$request_uri; } # managed by Certbot if ($host = lists.emergenus.com) { return 301 https://$host$request_uri; } # managed by Certbot listen 80 ; listen [::]:80 ; server_name www.emergenus.com lists.emergenus.com mail.emergenus.com emergenus.com; return 404; # managed by Certbot } Thanks billo

3 6

Question about lists and domains on Mailman 3
by Philip Colmer Dec. 29, 2021

Dec. 29, 2021

I've got a single server hosting multiple domains. I've got Apache working as the proxy in front of MM3. Regardless of whether I go to https://lists.domainA.org/mailman3/lists/ or https://lists.domainB.org/mailman3/lists/, Postorius lists ALL of the lists across both domains. Is there a way of configuring the system so that, if a user goes to "domain A", only the lists for that domain are listed? Thanks. Philip

2 2

slow restart time for mailmanweb
by David Newman Dec. 29, 2021

Dec. 29, 2021

Debian 11.2, Mailman 3.3.5, Python 3.9.2, MariaDB 10.5.12-0+deb11u1 On a Debian system running MariaDB, mailman3 restarts quickly but mailmanweb takes about 90 seconds: root@myhost # time systemctl restart mailmanweb real 1m30.156s user 0m0.013s sys 0m0.000s The daemon.log has a timeout error: Dec 28 12:16:01 myhost systemd[1]: Stopping GNU Mailman Web UI... Dec 28 12:16:03 myhost uwsgi[409333]: [uWSGI] getting INI configuration from /etc/mailman3/uwsgi.ini Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: State 'stop-sigterm' timed out. Killing. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 409333 (uwsgi) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418249 (uwsgi) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418250 (uwsgi) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418252 (sh) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418254 (mailman-web) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418258 (mailman-web) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418260 (mailman-web) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418261 (mailman-web) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418262 (mailman-web) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418263 (mailman-web) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418264 (mailman-web) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418265 (mailman-web) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418253 (uwsgi) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Main process exited, code=killed, status=9/KILL Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Failed with result 'timeout'. Dec 28 12:17:31 myhost systemd[1]: Stopped GNU Mailman Web UI. Here is /etc/systemd/system/mailmanweb.service file. [Unit] Description=GNU Mailman Web UI After=syslog.target network.target mariadb.service mailman3.service [Service] Environment="PYTHONPATH=/etc/mailman3/" User=mailman Group=mailman ExecStart=/opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini [Install] WantedBy=multi-user.target Starting with Debian 11, the MariaDB service is called mariadb and not mysqld or mysql. I tried substituting mysqld and mysql here and rerunning 'systemctl daemon-reload' each time, but restart times were similar, and also produced the same timeout error. And here is /etc/mailman3/uwsgi.ini: ##### [uwsgi] # Port on which uwsgi will be listening. http-socket = 0.0.0.0:8000 # If running uwsgi from the virtual environment ... virtualenv = /opt/mailman/venv/ module=mailman_web.wsgi:application # Add to python import path. pythonpath = /etc/mailman3/ # The default settings module. env = DJANGO_SETTINGS_MODULE=settings # Setup default number of processes and threads per process. master = true processes = 2 threads = 2 # Setup the django_q related worker processes. attach-daemon = /opt/mailman/venv/bin/mailman-web qcluster # Setup the request log. req-logger = file:/opt/mailman/web/logs/uwsgi.log # Log qcluster commands separately. logger = qcluster file:/opt/mailman/web/logs/uwsgi-qcluster.log log-route = qcluster uwsgi-daemons # Last log and it logs the rest of the stuff. logger = file:/opt/mailman/web/logs/uwsgi-error.log ##### What's causing the timeout, and what can I do to speed up restarts? Thanks. dn

4 9

per domain SITE_ID views?
by David Newman Dec. 29, 2021

Dec. 29, 2021

Using FILTER_VHOST, I have two domains set up and working with MM3, Postorius and Hyperkitty. However, because SITE_ID in settings.py points to one of the domains, that domain name always appears on Postorius and Hyperkitty pages. The FAQ says there's a way to edit the SITE_ID used by a domain: https://docs.mailman3.org/en/latest/faq.html#id2 But I think that's just for which SITE_ID is associated with each domain, and not what's displayed. I already have 'dom1.tld' and 'dom2.tld' set as the display names for each site (under Postorius/Domains/Edit or admin/Sites/Site). The issue is that Postorius and Hyperkitty show 'dom1.tld' for all pages, even those in dom2.tld. Presumably this is because of the SITE_ID value in settings.py. How to get the correct domain to appear on that domain's Postorius and Hyperkitty pages? Thanks. dn

2 2

Migrating to 3 - IsADirectoryError during hyperkitty_import
by horvath.arpad.szfvar＠gmail.com Dec. 28, 2021

Dec. 28, 2021

I tried to import an mbox using the command: sudo ./manage.py hyperkitty_import -l korus(a)lists.xxx.hu /var/lib/mailman/archives/private/korus.mbox I got the error message below, even if korus.mbox is a normal file (1.4GB large though). How can I import it without error? Importing from mbox file /var/lib/mailman/archives/private/korus.mbox to korus(a)lists.xxx.hu Traceback (most recent call last): File "/usr/share/mailman3-web/./manage.py", line 10, in <module> execute_from_command_line(sys.argv) File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 381, in execute_from_command_line utility.execute() File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 375, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 323, in run_from_argv self.execute(*args, **cmd_options) File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 364, in execute output = self.handle(*args, **options) File "/usr/lib/python3/dist-packages/hyperkitty/management/commands/hyperkitty_import.py", line 355, in handle importer.from_mbox(mbfile, report_name) File "/usr/lib/python3/dist-packages/hyperkitty/management/commands/hyperkitty_import.py", line 149, in from_mbox mbox = mailbox.mbox(mbfile) File "/usr/lib/python3.9/mailbox.py", line 850, in __init__ _mboxMMDF.__init__(self, path, factory, create) File "/usr/lib/python3.9/mailbox.py", line 584, in __init__ f = open(self._path, 'rb+') IsADirectoryError: [Errno 21] Is a directory: '/var/lib/mailman/archives/private/korus.mbox'

2 2

Migrating to 3 - email address
by horvath.arpad.szfvar＠gmail.com Dec. 28, 2021

Dec. 28, 2021

Hi All, I try to migrate my mailman2 listst to mailman3 based on this document https://docs.mailman3.org/en/latest/migration.html I'm on Debian 11 and using psql as datase for mailman3 and mailman3web. I try to run this command sudo -u list mailman import21 korus(a)lists.nospam.hu /var/lib/mailman/lists/korus/config.pck But I get the error message Error: No such list: korus(a)lists.nospam.hu The email I use is the command it exacttly the one we use to send email messages. What's wrong with it? Should I create the list in psql before I execute this command? Thanks, Arpad

2 1

Newbie question 2: Rewriting issue for bounced emails
by William Oliver Dec. 28, 2021

Dec. 28, 2021

I have installed mailman3 on a debian system with postfix and dovecot. I have gotten to the point that I can open the admin interface, set up domains and a mailinglist, and add users. I have subscribed two test users, one on the server and one on a different machine. Both got the confirmation email requests and the welcome messages. However, when I try to sent an email *to* the list from either account, I get the following error: This is the mail system at host mail.libertyfp.org. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system <"lmtp:[mail.libertyfp.org]:8024"@libertyfp.org> (expanded from <fplist(a)libertyfp.org>): unknown user: "lmtp:[mail.libertyfp.org]:8024@libertyfp.org" Apparently, fplist(a)libertyfp.org is getting rewritten to 8024(a)libertyfp.org. The only place where I have that number (that I know of) as a configuration is in mailman.cfg, where I have: [mta] verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1 incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: mail.libertyfp.org lmtp_port: 8024 smtp_host: mail.libertyfp.org smtp_port: 25 configuration: python:mailman.config.postfix recipient_delimiter = + unknown_local_recipient_reject_code = 550 owner_request_special = no Here's the last little bit of /etc/postfix/main.cf: # add to the end (add virtual users) # if specify multiple domains, specify comma or space separated virtual_mailbox_domains = libertyfp.org virtual_mailbox_base = /home/vmail virtual_mailbox_maps = hash:/etc/postfix/virtual-mailbox virtual_uid_maps = static:20000 virtual_gid_maps = static:20000 # mailman3 changes owner_request_special = no always_add_missing_headers = yes transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp #local_recipient_maps = # hash:/opt/mailman/mm/var/data/postfix_lmtp local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/opt/mailman/mm/var/data/postfix_lmtp relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains default_destination_recipient_limit = 30 default_destination_concurrency_limit = 15 virtual_alias_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp header_checks = regexp:/etc/postfix/header_checks Here's the bit in /etc/postfix/ mailman3 unix - - - - - lmtp -o lmtp_send_xforward_command=yes -o disable_dns_lookups=yes I don't think I have any mailman3 changes in /etc/dovecot/dovecot.conf Once again, any help would be appreciated. billo

2 17

Help with Newbie error -- I think I deleted my server
by William Oliver Dec. 25, 2021

Dec. 25, 2021

I have recently installed mailman3 on a Debian system with Posftix and Dovecot. I did it directly and did not use the docker setup. I managed to get it working to the point that I could send mail locally and outside my domain through mailman and log in as administrator. I decided to add a domain, but noticed on the form that the server was called "example.com." Clearly, I thought, I missed a configuration item here. I clicked on that, and it took me to a page where I could add servers. So, I added my real domain (libertyfp.org) It successfully added it, so I decided that I clearly didn't need "example.com" as a server, and deleted it using the same page. Immediately, I got an "internal server error" and have now lost all web interfaces. I tried restarting the daemons and rebooting the box, to no avail. The error message sent to my admin email is shown below. So... I have a couple of questions: 1) How can I set libertyfp.org as my server by use of a config file? 2) Failing that, how do a add "example.com" back, since I no longer have the web interface? I can't believe I did this. It took me a week to get this up and working, and I destroyed it in ten minutes after it was working. Any help would be appreciated. I suppose reinstalling will go much more quickly, since I know the mistakes I made over the past few days, but I really don't want to do that... Here's what it sends me: DoesNotExist at /mailman3/lists/ Site matching query does not exist. Request Method: GET Request URL: https://www.libertyfp.org/mailman3/lists/ Django Version: 3.0.14 Python Executable: /opt/mailman/venv/bin/uwsgi Python Version: 3.9.2 Python Path: ['/etc/mailman3/', '.', '', '/etc/mailman3', '/usr/lib/python39.zip', '/usr/lib/python3.9', '/usr/lib/python3.9/lib- dynload', '/opt/mailman/venv/lib/python3.9/site-packages'] Server time: Sat, 25 Dec 2021 04:14:00 +0000 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 (most recent call last): File "/opt/mailman/venv/lib/python3.9/site- packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/opt/mailman/venv/lib/python3.9/site- packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/opt/mailman/venv/lib/python3.9/site- packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/venv/lib/python3.9/site- packages/postorius/views/list.py", line 978, in list_index return render(request, template, File "/opt/mailman/venv/lib/python3.9/site- packages/django/shortcuts.py", line 19, in render content = loader.render_to_string(template_name, context, request, using=using) File "/opt/mailman/venv/lib/python3.9/site- packages/django/template/loader.py", line 62, in render_to_string return template.render(context, request) File "/opt/mailman/venv/lib/python3.9/site- packages/django/template/backends/django.py", line 61, in render return self.template.render(context) File "/opt/mailman/venv/lib/python3.9/site- packages/django/template/base.py", line 169, in render with context.bind_template(self): File "/usr/lib/python3.9/contextlib.py", line 117, in __enter__ return next(self.gen) File "/opt/mailman/venv/lib/python3.9/site- packages/django/template/context.py", line 246, in bind_template updates.update(processor(self.request)) File "/opt/mailman/venv/lib/python3.9/site- packages/django_mailman3/context_processors.py", line 32, in common context["site_name"] = get_current_site(request).name File "/opt/mailman/venv/lib/python3.9/site- packages/django/contrib/sites/shortcuts.py", line 13, in get_current_site return Site.objects.get_current(request) File "/opt/mailman/venv/lib/python3.9/site- packages/django/contrib/sites/models.py", line 58, in get_current return self._get_site_by_id(site_id) File "/opt/mailman/venv/lib/python3.9/site- packages/django/contrib/sites/models.py", line 30, in _get_site_by_id site = self.get(pk=site_id) File "/opt/mailman/venv/lib/python3.9/site- packages/django/db/models/manager.py", line 82, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/opt/mailman/venv/lib/python3.9/site- packages/django/db/models/query.py", line 415, in get raise self.model.DoesNotExist( Exception Type: DoesNotExist at /mailman3/lists/ Exception Value: Site matching query does not exist. Request information: USER: AnonymousUser GET: No GET data POST: No POST data FILES: No FILES data COOKIES: csrftoken = 'qklMdfLOyqa1TWm0b8nEHMFVBLaa0CgU2DXhSywjpgZMTnCSTNA4MkD4lGLB6z5N' META: CSRF_COOKIE = 'qklMdfLOyqa1TWm0b8nEHMFVBLaa0CgU2DXhSywjpgZMTnCSTNA4MkD4lGLB6z5N' CSRF_COOKIE_USED = True HTTP_ACCEPT = 'text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image /webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9' HTTP_ACCEPT_ENCODING = 'gzip, deflate, br' HTTP_ACCEPT_LANGUAGE = 'en-US,en;q=0.9' HTTP_CONNECTION = 'close' HTTP_COOKIE = 'csrftoken=qklMdfLOyqa1TWm0b8nEHMFVBLaa0CgU2DXhSywjpgZMTnCSTNA4MkD4lGLB 6z5N' HTTP_DNT = '1' HTTP_HOST = 'www.libertyfp.org' HTTP_SEC_FETCH_DEST = 'document' HTTP_SEC_FETCH_MODE = 'navigate' HTTP_SEC_FETCH_SITE = 'none' HTTP_SEC_FETCH_USER = '?1' HTTP_SEC_GPC = '1' HTTP_UPGRADE_INSECURE_REQUESTS = '1' HTTP_USER_AGENT = 'Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.93 Safari/537.36' HTTP_X_FORWARDED_FOR = '174.212.65.52' HTTP_X_FORWARDED_HOST = 'www.libertyfp.org' HTTP_X_FORWARDED_PROTO = 'https' HTTP_X_FORWARDED_SERVER = 'www.libertyfp.org' PATH_INFO = '/mailman3/lists/' QUERY_STRING = '' REMOTE_ADDR = '127.0.0.1' REQUEST_METHOD = 'GET' REQUEST_URI = '/mailman3/lists/' SCRIPT_NAME = '' SERVER_NAME = 'libertyfp.org' SERVER_PORT = '8000' SERVER_PROTOCOL = 'HTTP/1.0' uwsgi.core = 0 uwsgi.node = b'libertyfp.org' uwsgi.version = b'2.0.20' wsgi.errors = <_io.TextIOWrapper name=2 mode='w' encoding='UTF-8'> wsgi.file_wrapper = '' wsgi.input = <uwsgi._Input object at 0x7f8591167d90> wsgi.multiprocess = True 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', 'fp145(a)libertyfp.org'),)" ALLOWED_HOSTS = ['localhost', 'www.libertyfp.org', 'libertyfp.org', 'mail.libertyfp.org', 'list.libertyfp.org', '127.0.0.1'] 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 = PosixPath('/opt/mailman/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', 'compressor.filters.cssmin.rCSSMinFilter'], 'js': ['compressor.filters.jsmin.rJSMinFilter']} COMPRESS_JINJA2_GET_ENVIRONMENT = <function CompressorConf.JINJA2_GET_ENVIRONMENT at 0x7f859064d670> COMPRESS_MINT_DELAY = 30 COMPRESS_MTIME_DELAY = 10 COMPRESS_OFFLINE = False COMPRESS_OFFLINE_CONTEXT = {'STATIC_URL': '/static/'} COMPRESS_OFFLINE_MANIFEST = 'manifest.json' COMPRESS_OFFLINE_TIMEOUT = 31536000 COMPRESS_OUTPUT_DIR = 'CACHE' COMPRESS_PARSER = 'compressor.parser.AutoSelectParser' COMPRESS_PRECOMPILERS = "(('text/x-scss', 'sassc -t compressed {infile} {outfile}'), ('text/x-sass', 'sassc -t compressed {infile} {outfile}'))" COMPRESS_REBUILD_TIMEOUT = 2592000 COMPRESS_ROOT = '/opt/mailman/web/static' COMPRESS_STORAGE = 'compressor.storage.CompressorFileStorage' COMPRESS_TEMPLATE_FILTER_CONTEXT = {'STATIC_URL': '/static/'} COMPRESS_URL = '/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.postgresql_psycopg2', 'NAME': 'mailman', 'USER': 'mailman', 'PASSWORD': '********************', 'HOST': 'localhost', 'PORT': '5432', 'ATOMIC_REQUESTS': False, 'AUTOCOMMIT': True, 'CONN_MAX_AGE': 0, 'OPTIONS': {}, '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_EXCEPTION_REPORTER_FILTER = 'django.views.debug.SafeExceptionReporterFilter' DEFAULT_FILE_STORAGE = 'django.core.files.storage.FileSystemStorage' DEFAULT_FROM_EMAIL = 'mailman(a)libertyfp.org' DEFAULT_INDEX_TABLESPACE = '' DEFAULT_TABLESPACE = '' DISALLOWED_USER_AGENTS = [] EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_HOST_PASSWORD = '********************' EMAIL_HOST_USER = 'mailman(a)libertyfp.org' 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 = 420 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': '/opt/mailman/web/fulltext_index'}} HYPERKITTY_ENABLE_GRAVATAR = True 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'] 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'), ('uz', 'Uzbek'), ('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_HTTPONLY = False LANGUAGE_COOKIE_NAME = 'django_language' LANGUAGE_COOKIE_PATH = '/' LANGUAGE_COOKIE_SAMESITE = None LANGUAGE_COOKIE_SECURE = False 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.WatchedFileHandler', 'filename': '/opt/mailman/web/logs/mailmanweb.log', 'formatter': 'verbose'}, 'console': {'class': 'logging.StreamHandler', 'formatter': 'simple'}}, 'loggers': {'django.request': {'handlers': ['mail_admins', 'file'], 'level': 'ERROR', 'propagate': True}, 'django': {'handlers': ['file'], 'level': 'ERROR', 'propagate': True}, 'hyperkitty': {'handlers': ['file'], 'level': 'DEBUG', 'propagate': True}, 'postorius': {'handlers': ['console', 'file'], 'level': 'INFO'}}, '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')" 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:8000' PREPEND_WWW = False Q_CLUSTER = {'retry': 360, 'timeout': 300, 'save_limit': 100, 'orm': 'default'} ROOT_URLCONF = 'mailman_web.urls' SECRET_KEY = '********************' SECURE_BROWSER_XSS_FILTER = False SECURE_CONTENT_TYPE_NOSNIFF = True SECURE_HSTS_INCLUDE_SUBDOMAINS = False SECURE_HSTS_PRELOAD = False SECURE_HSTS_SECONDS = 0 SECURE_PROXY_SSL_HEADER = None SECURE_REDIRECT_EXEMPT = [] SECURE_REFERRER_POLICY = None SECURE_SSL_HOST = None SECURE_SSL_REDIRECT = False SERVER_EMAIL = 'root(a)localhost.local' 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 = {'openid': {'SERVERS': [{'id': 'yahoo', 'name': 'Yahoo', 'openid_url': 'http://me.yahoo.com'}]}, 'google': {'SCOPE': ['profile', 'email'], 'AUTH_PARAMS': {'access_type': 'online'}}, 'facebook': {'METHOD': 'oauth2', 'SCOPE': ['email'], 'FIELDS': ['email', 'name', 'first_name', 'last_name', 'locale', 'timezone'], 'VERSION': 'v2.4'}} 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 = '/opt/mailman/web/static' STATIC_URL = '/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 = False USE_X_FORWARDED_PORT = False WSGI_APPLICATION = 'mailman_web.wsgi.application' X_FRAME_OPTIONS = 'DENY' YEAR_MONTH_FORMAT = 'F Y'

2 4

Re: Mailing Lists
by Mark Sapiro Dec. 23, 2021

Dec. 23, 2021

On 12/23/21 3:09 PM, John McDonald via Mailman-users wrote: > I am responsible for the mailing list of a local church. Recently the church was moved to using Mailman for this. When a simple message is created and sent to the mailing list most email addresses received it correctly but those with an Outlook or Hotmail account received attachments and not the message. There are three attachments and one of them has to be opened to view the message. > > Am I missing some setting? First question. Is this Mailman 2.1 or Mailman 3? This list is for Mailman 3. The corresponding list for Mailman 2.1 is https://mail.python.org/mailman3/lists/mailman-users.python.org/ That said, your issue is because the list is adding a message footer (or possibly header or both) to the delivered message. This is discussed in the FAQ at https://wiki.list.org/x/4030707 That FAQ says there are Mailman configuration things you can do. Exactly what you do depends on the requirements of your list and whether this is Mailman 2.1 or Mailman 3. If you don't require that HTML or other non plain text parts be delivered, you can adjust content filtering to remove them and create a simple plain text message which won't have this problem. Or you can ensure that no message header/footer is added. How you do these things depends on your Mailman version. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 1

Re: Mailing Lists
by David Newman Dec. 23, 2021

Dec. 23, 2021

On 12/23/21 3:09 PM, John McDonald via Mailman-users wrote: > I am responsible for the mailing list of a local church. Recently the church was moved to using Mailman for this. When a simple message is created and sent to the mailing list most email addresses received it correctly but those with an Outlook or Hotmail account received attachments and not the message. There are three attachments and one of them has to be opened to view the message. > > Am I missing some setting? This is possibly unrelated to Mailman, and possibly happening because Outlook.com and Hotmail are both owned by Microsoft, and both are flagging your server as a spam source. You can verify this by checking your mail server's logs. Usually a big service like Hotmail or Gmail will embed a URL in the error message where you can go to apply to be whitelisted. If this is the problem, you may need to take additional steps (again outside of Mailman3) to be a good email server citizen, such as adding DKIM and SPF records in your domain's DNS. Unless you have both, Microsoft or Google may block your server. It might also be a Mailman problem, but since some subscribers do get postings, I'd start with this first. dn

2 1

Mailing Lists
by John McDonald Dec. 23, 2021

Dec. 23, 2021

I am responsible for the mailing list of a local church. Recently the church was moved to using Mailman for this. When a simple message is created and sent to the mailing list most email addresses received it correctly but those with an Outlook or Hotmail account received attachments and not the message. There are three attachments and one of them has to be opened to view the message. Am I missing some setting? John McDonald

1 0

Postorius fails to show list because of a large message being held
by Gilles Filippini Dec. 22, 2021

Dec. 22, 2021

Hi, Recently a member of one of our private lists sent a message with a picture attached. Because of the large message size (23MB) it was put into the moderation queue. But since then postorius fails to open the list's page with this error: Something went wrong Mailman REST API not available. Please start Mailman core. The database logs show that it processed a request related to the held message just before failing: LOG: statement: SELECT message.id AS message_id_1, message.message_id AS message_message_id, message.message_id_hash AS message_message_id_hash, message.path AS message_path FROM message WHERE message.message_id = '<CAEcCghAdp+20jiG19jNGX06xhJ-iYvZGyyV8b-toW7LqCSv5JQ(a)mail.gmail.com>' LIMIT 1 Mailman Core logs: [2020-07-14 10:41:21 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:49) [2020-07-14 10:41:21 +0000] [49] [INFO] Worker exiting (pid: 49) [2020-07-14 10:41:22 +0000] [50] [INFO] Booting worker with pid: 50 How should I proceed to unblock the situation? Thanks, _g.

4 7

apache2 security for mailman3 admin
by Lars Schimmer Dec. 22, 2021

Dec. 22, 2021

Hi, I know it is not the perfect place to ask, but if onyone has a good idea, example, I would be happy. I do run mailman3 with apache ProxyPass in front. I did set: <IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost </IfModule> as given as example to set it up. Now I want to limit the mailman3/admin area to a defined IP range. Anyone has a working example to limit only the /admin area to a IP range in Apache2, but everything else as it is now? Thank you, MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

2 1

list footer web customization procedure
by Philippe B Dec. 20, 2021

Dec. 20, 2021

I am new to Mailman 3 and I've been reading all the documentation that I could find, but I haven't been able to figure out how a list owner can use the web interface to customize the footer that appears at the end of each e-mail from the list. We're actually after something much simpler (in theory), which is to eliminate the built-in footer altogether for some of our lists. Could someone share the instructions for doing that? Thanks.

4 21

restricting public lists per virtual domain
by David Newman Dec. 17, 2021

Dec. 17, 2021

Can lists set to be viewable on the index page be limited to the virtual domain they are a part of? Let's say I have two virtual domains: lists.dom1.tld lists.dom2.tld Currently, if any list in either domain is set to be viewable on the index page, it's viewable in both domains, not just the one it's a part of. How to restrict access on a per-domain basis? I searched the archives and found something about disabling archives per domain [1], but that's a different question. This seems like a standard problem and may have been asked a different way before, and I may have missed it. Thanks in advance for config clues. dn [1] https://lists.mailman3.org/archives/search?mlist=mailman-users%40mailman3.o…

3 3

Strange problem in user lists
by Gelpi Andrea Dec. 16, 2021

Dec. 16, 2021

Hi, I have a strange problem in one list. when I add a memebr I use the form "Name Surname" <email(a)domain.tld> I cant' understand why, but I have two members with the wrong name. "A B" <C(a)dom.tld> "D E" <F(a)dom.tld> My problem is that A and B must be associated with F(a)dom.tld and vice-versa. I tried to delete the user member and recreate it, but it has always the wrong name. Is it possible to correct those errors? How? Thanks in advance -- Gelpi ing. Andrea -------------------------------------------------------------- It took the computing power of three C-64s to fly to the Moon. It takes a 486 to run Windows 95. Something is wrong here. --------------------------------------------------------------

2 1

File in /var/lib/mailman3/queue/bounces/
by Andreas Barth Dec. 12, 2021

Dec. 12, 2021

Hi, in my local installation there is a file in /var/lib/mailman3/queue/bounces/ since a couple of days. Any hint how to get rid of it? 'mailman unshunt' doesn't do it, but also, it's in queue/bounces and now queue/shunt. Andi

3 4

Hyperkitty - 'MySQL server has gone away'
by dancab＠caltech.edu Dec. 10, 2021

Dec. 10, 2021

I just deployed Mailman3 last night. This is the first error message I've encountered from Hyperkitty. It looks like a MySQL configuration issue. I've done some tuning to the wait/timeouts but I'm still getting the error message. I suspect the root cause is the size of the message. mailman qfile shows the message has 84746 lines and the .pck file is 6.9M. Let me know if there's more specific tuning that needs to be done to cover larger messages. My MySQL wait/timeouts are set as follows: MySQL [mysql]> SHOW VARIABLES LIKE "%timeout%"; +-----------------------------+----------+ | Variable_name | Value | +-----------------------------+----------+ | connect_timeout | 120 | | delayed_insert_timeout | 300 | | have_statement_timeout | YES | | innodb_flush_log_at_timeout | 1 | | innodb_lock_wait_timeout | 50 | | innodb_rollback_on_timeout | ON | | interactive_timeout | 28800 | | lock_wait_timeout | 31536000 | | net_read_timeout | 90 | | net_write_timeout | 90 | | rpl_stop_slave_timeout | 31536000 | | slave_net_timeout | 60 | | wait_timeout | 28800 | +-----------------------------+----------+ 13 rows in set (0.002 sec) MySQL [mysql]> SHOW VARIABLES LIKE "%wait%"; +---------------------------------------------------+----------+ | Variable_name | Value | +---------------------------------------------------+----------+ | innodb_lock_wait_timeout | 50 | | innodb_spin_wait_delay | 6 | | lock_wait_timeout | 31536000 | | performance_schema_events_waits_history_long_size | 0 | | performance_schema_events_waits_history_size | 0 | | wait_timeout | 28800 | +---------------------------------------------------+----------+ 6 rows in set (0.004 sec) ############################################## ####################### ERROR 2021-11-05 09:26:28,656 261 django.request Internal Server Error: /hyperkitty/api/mailman/archive Traceback (most recent call last): File "/opt/mailmanve/lib/python3.6/site-packages/django/db/backends/utils.py", line 86, in _execute return self.cursor.execute(sql, params) File "/opt/mailmanve/lib/python3.6/site-packages/django/db/backends/mysql/base.py", line 74, in execute return self.cursor.execute(query, args) File "/opt/mailmanve/lib/python3.6/site-packages/MySQLdb/cursors.py", line 206, in execute res = self._query(query) File "/opt/mailmanve/lib/python3.6/site-packages/MySQLdb/cursors.py", line 319, in _query db.query(q) File "/opt/mailmanve/lib/python3.6/site-packages/MySQLdb/connections.py", line 259, in query _mysql.connection.query(self, query) MySQLdb._exceptions.OperationalError: (2006, 'MySQL server has gone away') The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/opt/mailmanve/lib/python3.6/site-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/opt/mailmanve/lib/python3.6/site-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/opt/mailmanve/lib/python3.6/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailmanve/lib/python3.6/site-packages/django/views/decorators/http.py", line 40, in inner return func(request, *args, **kwargs) File "/opt/mailmanve/lib/python3.6/site-packages/hyperkitty/views/mailman.py", line 118, in _decorator return func(request, *args, **kwargs) File "/opt/mailmanve/lib/python3.6/site-packages/django/views/decorators/csrf.py", line 54, in wrapped_view return view_func(*args, **kwargs) File "/opt/mailmanve/lib/python3.6/site-packages/hyperkitty/views/mailman.py", line 164, in archive add_to_list(mlist_fqdn, msg) File "/opt/mailmanve/lib/python3.6/site-packages/hyperkitty/lib/incoming.py", line 153, in add_to_list email.save() File "/opt/mailmanve/lib/python3.6/site-packages/django/db/models/base.py", line 749, in save force_update=force_update, update_fields=update_fields) File "/opt/mailmanve/lib/python3.6/site-packages/django/db/models/base.py", line 787, in save_base force_update, using, update_fields, File "/opt/mailmanve/lib/python3.6/site-packages/django/db/models/base.py", line 890, in _save_table results = self._do_insert(cls._base_manager, using, fields, returning_fields, raw) File "/opt/mailmanve/lib/python3.6/site-packages/django/db/models/base.py", line 929, in _do_insert using=using, raw=raw, File "/opt/mailmanve/lib/python3.6/site-packages/django/db/models/manager.py", line 82, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/opt/mailmanve/lib/python3.6/site-packages/django/db/models/query.py", line 1204, in _insert return query.get_compiler(using=using).execute_sql(returning_fields) File "/opt/mailmanve/lib/python3.6/site-packages/django/db/models/sql/compiler.py", line 1394, in execute_sql cursor.execute(sql, params) File "/opt/mailmanve/lib/python3.6/site-packages/django/db/backends/utils.py", line 68, in execute return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/opt/mailmanve/lib/python3.6/site-packages/django/db/backends/utils.py", line 77, in _execute_with_wrappers return executor(sql, params, many, context) File "/opt/mailmanve/lib/python3.6/site-packages/django/db/backends/utils.py", line 86, in _execute return self.cursor.execute(sql, params) File "/opt/mailmanve/lib/python3.6/site-packages/django/db/utils.py", line 90, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/opt/mailmanve/lib/python3.6/site-packages/django/db/backends/utils.py", line 86, in _execute return self.cursor.execute(sql, params) File "/opt/mailmanve/lib/python3.6/site-packages/django/db/backends/mysql/base.py", line 74, in execute return self.cursor.execute(query, args) File "/opt/mailmanve/lib/python3.6/site-packages/MySQLdb/cursors.py", line 206, in execute res = self._query(query) File "/opt/mailmanve/lib/python3.6/site-packages/MySQLdb/cursors.py", line 319, in _query db.query(q) File "/opt/mailmanve/lib/python3.6/site-packages/MySQLdb/connections.py", line 259, in query _mysql.connection.query(self, query) django.db.utils.OperationalError: (2006, 'MySQL server has gone away')

1 1

Lookup Table Questions
by Peter Williams Dec. 8, 2021

Dec. 8, 2021

Hello, I am currently working on upgrading our Mailman system from Mailman 3.3.1 to Mailman 3.3.5. Our configuration utilizes containers that run on Alpine Linux. While working on updating the containers I noticed that the recent version of Alpine has dropped support for Berkeley DB lookup tables. Due to this change I think our only option is to switch over from using hash tables to regexp tables (or switch the OS the containers are running on). In addition, while I was working on the updates I realized that even though the Berkeley DB support has been dropped Mailman seems to work ok with the new default lookup table for Postfix on Alpine: LMDB. I was hoping to get a few answers to some of the questions I have with regards to the options we have moving forward. Any help is greatly appreciated! - The Mailman documentation notes that either hash or regexp tables are supported. Is it ok to use LMDB or will I run into issues at some point? - If LMDB tables are not a good idea to use, are there any drawbacks to switching over to regexp tables? My main concern is that we currently have 7000+ mailing lists, and I'm worried that switching over to regexp may result in slower lookups. I am also wondering if there are potential issues if the 'mailman aliases' command is run simultaneously alongside another 'mailman aliases' command. In the past it seems like the hash table was locked (which was good), and I'm not sure if this behavior is kept by moving over to regexp. This may be more of a Postfix question and I apologize in advance if I am asking the wrong mailing list for this. Thank you for any guidance you can provided with this and have a nice day, Peter

2 1

missing graphics in Postorius
by David Newman Dec. 8, 2021

Dec. 8, 2021

After installing MM3 on Debian 10 using the venv docs, no graphics appear in the admin or list pages, just broken links. The mailmanweb log has lines like this: ERROR 2021-12-07 06:04:10,002 18262 django.security.DisallowedHost Invalid HTTP_HOST header: '127.0.0.1'. You may need to add '127.0.0.1' to ALLOWED_HOSTS. which is odd because there is the line for "localhost" in settings.py, and /etc/hosts correctly ties this to 127.0.0.1. There are entries like this in /var/log/nginx/error.log saying the files just aren't there: 2021/12/06 22:00:30 [error] 18123#18123: *65 open() "/opt/mailman/web/static/postorius/img/mailman_logo_small_trans.png" failed (2: No such file or directory), client: x.x.x.x, server: somehost.example.com, request: "GET /static/postorius/img/mailman_logo_small_trans.png HTTP/2.0", host: "somehost.example.com", referrer: "https://somehost.example.com/mailman/lists/" (I've obfuscated names and addresses here, but "somehost.example.com" refers to a valid FQDN in the log.) I thought I'd followed all the venv docs, but the /opt/mailman/web/static/postorius directory doesn't exist. Did I miss something? Thanks. dn

2 3