- Mailman-users - lists.mailman3.org

Errors while importing mm2 list archives
by Odhiambo Washington 23 Dec '22

23 Dec '22

MM3-3.3.7, Hyperkitty-1.3.6 While importing, I encountered several of this error: <CUT> MySQLdb.OperationalError: (1366, "Incorrect string value: '\\xF0\\x9F\\x98\\x8A, ...' for column 'content' at row 1") The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/management/commands/hyperkitty_import.py", line 232, in from_mbox add_to_list(self.list_address, message) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/lib/incoming.py", line 153, in add_to_list email.save() File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/models/base.py", line 812, in save self.save_base( File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/models/base.py", line 863, in save_base updated = self._save_table( File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/models/base.py", line 1006, in _save_table results = self._do_insert( File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/models/base.py", line 1047, in _do_insert return manager._insert( File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/models/manager.py", line 85, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/models/query.py", line 1791, in _insert return query.get_compiler(using=using).execute_sql(returning_fields) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/models/sql/compiler.py", line 1660, in execute_sql cursor.execute(sql, params) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/backends/utils.py", line 67, in execute return self._execute_with_wrappers( File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/backends/utils.py", line 80, in _execute_with_wrappers return executor(sql, params, many, context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/backends/utils.py", line 89, in _execute return self.cursor.execute(sql, params) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/utils.py", line 91, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/backends/utils.py", line 89, in _execute return self.cursor.execute(sql, params) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/backends/mysql/base.py", line 75, in execute return self.cursor.execute(query, args) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/MySQLdb/cursors.py", line 206, in execute res = self._query(query) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/MySQLdb/cursors.py", line 319, in _query db.query(q) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/MySQLdb/connections.py", line 254, in query _mysql.connection.query(self, query) django.db.utils.OperationalError: (1366, "Incorrect string value: '\\xF0\\x9F\\x98\\x8A, ...' for column 'content' at row 1") </CUT> That occurred several times, but the import process went all the way, to 99% then came to the point below. Message 253d9d44-cc3e-fed1-144b-34da88c52b39(a)emailplus.org failed to import, skipping Computing thread structure Synchronizing properties with Mailman 904 emails left to refresh, checked 0 764 emails left to refresh, checked 0 Warming up cache Traceback (most recent call last): File "/opt/mailman/mm/venv/bin/django-admin", line 8, in <module> sys.exit(execute_from_command_line()) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line utility.execute() File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/management/__init__.py", line 440, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/management/base.py", line 402, in run_from_argv self.execute(*args, **cmd_options) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/management/base.py", line 448, in execute output = self.handle(*args, **options) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/management/commands/hyperkitty_import.py", line 411, in handle call_command("hyperkitty_warm_up_cache", list_address) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/management/__init__.py", line 198, in call_command return command.execute(*args, **defaults) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/management/base.py", line 448, in execute output = self.handle(*args, **options) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/management/commands/hyperkitty_warm_up_cache.py", line 53, in handle self.warm_up_mlist(mlist, options) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/management/commands/hyperkitty_warm_up_cache.py", line 61, in warm_up_mlist for thread in mlist.recent_threads: File "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/models/mailinglist.py", line 162, in recent_threads return self.cached_values["recent_threads"]() File "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/models/common.py", line 58, in __call__ return self.get_or_set(*args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/models/mailinglist.py", line 317, in get_or_set return [Thread.objects.get(pk=pk) for pk in thread_ids] File "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/models/mailinglist.py", line 317, in <listcomp> return [Thread.objects.get(pk=pk) for pk in thread_ids] File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/models/manager.py", line 85, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/models/query.py", line 650, in get raise self.model.DoesNotExist( hyperkitty.models.thread.Thread.DoesNotExist: Thread matching query does not exist. (venv) [mailman@gw ~/mm]$ Should I take it that the import was successful, or what should I do next? PS: This is the 1st run after installing MM3 on this server and the MM3 list hasn't gone live. So if anything, I am okay with doing what needs to be done and rerun the import. TIA -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 12

No Archives
by Odhiambo Washington 22 Dec '22

22 Dec '22

I am working on a migration from MM2 to MM3. My MM2 lists are domiciled at https://lists.kictanet.or.ke/ To work on the web UI for MM3, I created a subdomain - mm3-lists.kictanet.or.ke. I have mostly done everything, including importing the archives. However, when I access https://mm3-lists.kictanet.or.ke/archives/, it's all empty. However, when I visit https://mm3-lists.kictanet.or.ke/mailman3/lists/, I can see my list. In Postorius, the site name is lists.kictanet.or.ke (same with mail domain). I have SITE_ID = 3 in both settings*.py and have restarted both Apache and Gunicorn. Could this be due to the fact that I am accessing the site using a domain name different than what the actual site is? Or there is something minor I am missing? PS: I am wondering also why SITE_ID=3 when I only added one site, besides the default example.com. If need be, I am willing to blow away the whole virtualenv and start afresh. It's a good step towards mastering the installation of MM3 :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 2

message awaits moderator approval´
by Eggert Ehmke 21 Dec '22

21 Dec '22

When I send a mail to a list that exceeds the max size, I get the above answer. However, the moderator of that list does not get a message, and there is no entry in the list of hold back messages. This should be a configuration problem, on another list on the same server this works fine. I cannot find any differences in the settings.

2 4

Emergency moderation and clearing out a lot of held messages
by bob B 21 Dec '22

21 Dec '22

We had an issue where a program went rogue and sent out 30k email alerts to one of our lists, so now I have a few questions. When the issue happened I turned on emergency moderation and we have resolved the issue so.. 1. How do I easily delete 30k of held messages? It looks like the GUI only allows me to do 200 at a time? is there a way to flush all held messages easily? 2. When I enabled Emergency moderation, I expected it to stop notifying the admin on every held message, but it appears that is not the case? Also, does it reply to the sender of every held message when Emergency moderation is on? it seems like the steps are: turn on "Emergency moderation" turn OFF "Notify users of held messages" turn OFF "Admin immed notify"

6 28

SMTPNotSupportedError when requesting new password
by Eggert Ehmke 21 Dec '22

21 Dec '22

I get this error when a user tries to use the "forgot password" function in hyperkitty. Obviously the exception is thrown when the send_mail function is called in /opt/mailman/venv/lib/python3.9/site-packages/allauth/account/adapter.py In settings.py I have: EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_PORT = 25 EMAIL_HOST_USER = 'valid email' EMAIL_HOST_PASSWORD = 'valid password' What can I do to debug further?

2 2

MM3 List Templates
by Odhiambo Washington 21 Dec '22

21 Dec '22

I am reading https://wiki.list.org/DOC/Mailman%203%20installation%20experience regarding templates and I am confused about whether to treat the path /opt/mailman/mm/var/templates/*site*/en/ literally or even if that information is still relevant. I created the exact path and put those templates in there, but they do not show up on Postorius. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

1 1

Where do I find the bounced messages?
by Sörös Zoltán 20 Dec '22

20 Dec '22

Greetings, I am running several lists under mailman3. I am getting notifications about users being put on nomail because of their bounces - but I can find no way to actually see the bounced messages. Do mailman3 store the received bounces? Where? Is there any setting to forward these bounces to the list owner? Thanks in advance -- Sörös Zoltán E-mail: beer(a)filmjus.hu http://www.filmjus.hu/~beer/

2 1

Can "Pre Verified" set to yes by default?
by Alan So 20 Dec '22

20 Dec '22

We are a university with many departments & colleges owning their own mailing lists and they manage their members lists by themselves. The current (ours is 1.3.6) Postorius have a default of "Pre Verified" as "No" when doing mass subscription by the list admin. It sounds sensible if most people subscribe to the lists by themselves normally. But in our case, our departmental staff normally maintain their list of members and do not want their members need to do anything before they can be reachable from lists. However, some of our departmental staff sometimes forget to check the box "Pre Verified" when they refresh (actually delete all and subscribe all) list of members during term's start. This often lead to issue especially if the list they maintained have thousands of members. Our normal way to help them is to remove the list and create the list again so that the departmental staff do not need to discard the pending members one by one. This is already the best scenario if they know that it is the root cause. Since subscribing thousands of members normally will not have the normal UI page coming back (due to timeout), they often do not know that it is the cause of issue. If they repeat the steps to subscribe the members again, they will just not be able to get the job done but also make the system busier and they never know that it's already in the pending list. Is this possible to add default setting of Pre Verified during mass-subscription (for example settings.py) such that we can help them a bit? Thanks.

3 9

Broken web UI after upgrade
by Odhiambo Washington 17 Dec '22

17 Dec '22

After upgrading MM3 and running all the post-update tasks and even re-indexing all the posts, I have ended up with a somehow "broken" hyperkitty. The archives display on a browser six, to say the least. The site is public, so I can share the link: https://list.rc.org/archives/ What should I do in order to fix this? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

6 19

Slow and out-of-sequence delivery
by Gregg Roberts 17 Dec '22

17 Dec '22

Dear Mailman Supporters, I participate in a professional forum run on Mailman. It serves a small nonprofit mutual benefit organization with possibly fewer than 50 members. Messages that I post to the forum have been taking as long as 48 hours to come back to me. The issue is not new and AFAIK no one has been messing with the settings. But the issue seems to have been becoming more and more severe in recent weeks. Perhaps because of such delays, I also sometimes see responses to other posts before I see the original post. It takes extra time to understand the context when that happens. People's time gets wasted answering questions that have already been answered without their knowledge. It's just frustrating all around. The email address from which messages are sent is not in the list of email addresses maintained in the hosting account cPanel. There seems to be one by the name "relay" that is being used by Mailman. I actually don't know which version of Mailman is installed. I'm hoping it's the more recent of the two options so I optimistically joined this particular list. The hosting service tech support can't help because they can't see the forum email address or its logs. At least that's what they say. Tech-support also tells me that they routinely do load-balancing and the server should not be excessively busy. It should certainly not take 48 hours to send an email message to 50 recipients. It shouldn't even take more than an hour, because the system is set to send messages at least once per hour -- maybe even every 10 minutes -- and the whole queue should be able to be handled in one sending cycle ... right? A contract tech support guy has suggested that it might solve a problem if we started spending $100-$150 per month on a dedicated server. I think that is a wrongheaded suggestion. If the organization had thousands of members, it would make more sense. But throwing money at the problem if something is simply not set up right, or some critical file is corrupted, is not the right solution. Set the broken bone correctly first, THEN inject stimulants and send the player back out onto the field. :-) Thanks in advance for any help! Gregg Roberts http://legalsupport-sc.com Legal Support Services of Southern California 43430 E. Florida Ave #F-293 Hemet CA 92544 951-330-4450 The information contained in this e-mail message is privileged and confidential information, intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution of copy of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by telephone at 951-330-4450 or reply by e-mail and delete or discard this message.

2 2

Error while Approving a Post Through Email
by Alex A.J. 15 Dec '22

15 Dec '22

Hello, I have installed mailman3 (with postgresql) on Ubuntu 22.04 in a virtual environment. I can approve/discard posts from the Web UI, but when trying to approve a post through email (Approved header as the first line in reply), the following error is showing up in mailman.log: Dec 13 17:01:41 2022 (2677611) Uncaught runner exception: hash could not be identified Dec 13 17:01:41 2022 (2677611) Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/core/runner.py", line 179, in _one_iteration self._process_one_file(msg, msgdata) File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/core/runner.py", line 272, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/runners/command.py", line 214, in _dispose status = command.process( File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/commands/eml_confirm.py", line 67, in process return self.process_held( File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/commands/eml_confirm.py", line 104, in process_held approved = Approved().check(mlist, msg, msgdata) File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/rules/approved.py", line 143, in check is_valid, new_hash = config.password_context.verify(password, mpw) File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/utilities/passwords.py", line 61, in verify return self._context.verify_and_update(password, hashed) File "/opt/mailman/venv/lib/python3.10/site-packages/passlib/context.py", line 2422, in verify_and_update record = self._get_or_identify_record(hash, scheme, category) File "/opt/mailman/venv/lib/python3.10/site-packages/passlib/context.py", line 2031, in _get_or_identify_record return self._identify_record(hash, category) File "/opt/mailman/venv/lib/python3.10/site-packages/passlib/context.py", line 1132, in identify_record raise exc.UnknownHashError("hash could not be identified") passlib.exc.UnknownHashError: hash could not be identified Dec 13 17:01:41 2022 (2677611) SHUNTING: 1670931101.6040337+d5806b00b2b9d03f25db396639f66f3a26516178 Any ideas? Thanks Alex.

3 5

Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive
by Gordon Dickens 13 Dec '22

13 Dec '22

My mailman3 installation has now been up and running successfully for several weeks without any issues and then the following error message was emailed to me by my server. What's up with this error message and what do I need to do? Thanks, Gordon -------- Forwarded Message -------- Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive Date: Fri, 20 Nov 2020 01:25:41 -0000 From: [1]root(a)host2.mailhub4u.com To: [2]gordon(a)mailhub4u.com Internal Server Error: /mailman3/hyperkitty/api/mailman/archive OperationalError at /hyperkitty/api/mailman/archive (1366, "Incorrect string value: '\\xF0\\x9F\\xA4\\xA3\\xF0\\x9F...' for column `mailman3web`.`hyperkitty_email`.`content` at row 1") Request Method: POST Request URL: [3]http://localhost/mailman3/hyperkitty/api/mailman/archive?key=0123456 789abcdef0123456789ABCDEF Django Version: 1.11.29 Python Executable: /usr/bin/uwsgi-core Python Version: 3.7.3 Python Path: ['.', '', '/usr/lib/python37.zip', '/usr/lib/python3.7', '/usr/lib/python3.7/lib-dynload', '/usr/local/lib/python3.7/dist-packages', '/usr/lib/python3/dist-packages'] Server time: Fri, 20 Nov 2020 01:25:40 +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: File "/usr/lib/python3/dist-packages/django/db/backends/utils.py" in execute 64. return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/mysql/base.py" in execute 101. return self.cursor.execute(query, args) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in execute 250. self.errorhandler(self, exc, value) File "/usr/lib/python3/dist-packages/MySQLdb/connections.py" in defaulterrorhandler 50. raise errorvalue File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in execute 247. res = self._query(query) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in _query 411. rowcount = self._do_query(q) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in _do_query 374. db.query(q) File "/usr/lib/python3/dist-packages/MySQLdb/connections.py" in query 292. _mysql.connection.query(self, query) The above exception ((1366, "Incorrect string value: '\\xF0\\x9F\\xA4\\xA3\\xF0\\x9F...' for column `mailman3web`.`hyperkitty_email`.`content` at row 1")) was the direct cause of the following exception: File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 41. response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 187. response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 185. response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/decorators/http.py" in inner 40. return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/mailman.py" in _decorator 69. return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django/views/decorators/csrf.py" in wrapped_view 58. return view_func(*args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/mailman.py" in archive 115. add_to_list(mlist_fqdn, msg) File "/usr/lib/python3/dist-packages/hyperkitty/lib/incoming.py" in add_to_list 151. email.save() File "/usr/lib/python3/dist-packages/django/db/models/base.py" in save 808. force_update=force_update, update_fields=update_fields) File "/usr/lib/python3/dist-packages/django/db/models/base.py" in save_base 838. updated = self._save_table(raw, cls, force_insert, force_update, using, update_fields) File "/usr/lib/python3/dist-packages/django/db/models/base.py" in _save_table 924. result = self._do_insert(cls._base_manager, using, fields, update_pk, raw) File "/usr/lib/python3/dist-packages/django/db/models/base.py" in _do_insert 963. using=using, raw=raw) File "/usr/lib/python3/dist-packages/django/db/models/manager.py" in manager_method 85. return getattr(self.get_queryset(), name)(*args, **kwargs) File "/usr/lib/python3/dist-packages/django/db/models/query.py" in _insert 1079. return query.get_compiler(using=using).execute_sql(return_id) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py" in execute_sql 1112. cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py" in execute 64. return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/utils.py" in __exit__ 94. six.reraise(dj_exc_type, dj_exc_value, traceback) File "/usr/lib/python3/dist-packages/django/utils/six.py" in reraise 685. raise value.with_traceback(tb) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py" in execute 64. return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/mysql/base.py" in execute 101. return self.cursor.execute(query, args) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in execute 250. self.errorhandler(self, exc, value) File "/usr/lib/python3/dist-packages/MySQLdb/connections.py" in defaulterrorhandler 50. raise errorvalue File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in execute 247. res = self._query(query) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in _query 411. rowcount = self._do_query(q) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in _do_query 374. db.query(q) File "/usr/lib/python3/dist-packages/MySQLdb/connections.py" in query 292. _mysql.connection.query(self, query) Exception Type: OperationalError at /hyperkitty/api/mailman/archive Exception Value: (1366, "Incorrect string value: '\\xF0\\x9F\\xA4\\xA3\\xF0\\x9F...' for column `mailman3web`.`hyperkitty_email`.`content` at row 1") Request information: USER: AnonymousUser GET: key = '0123456789abcdef0123456789ABCDEF' POST: mlist = '[4]members(a)georgiajets.org' FILES: message = <InMemoryUploadedFile: message.txt ()> COOKIES: No cookie data META: CONTENT_LENGTH = '7720' CONTENT_TYPE = 'multipart/form-data; boundary=8da553dce5f76815f62f12a1b8c0efac' CONTEXT_DOCUMENT_ROOT = '/var/www/html' CONTEXT_PREFIX = '' DOCUMENT_ROOT = '/var/www/html' GATEWAY_INTERFACE = 'CGI/1.1' HTTP_ACCEPT = '*/*' HTTP_ACCEPT_ENCODING = 'gzip, deflate' HTTP_CONNECTION = 'keep-alive' HTTP_HOST = 'localhost' HTTP_USER_AGENT = 'python-requests/2.21.0' PATH = '/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin' PATH_INFO = '/hyperkitty/api/mailman/archive' QUERY_STRING = 'key=0123456789abcdef0123456789ABCDEF' REMOTE_ADDR = '127.0.0.1' REMOTE_PORT = '53006' REQUEST_METHOD = 'POST' REQUEST_SCHEME = 'http' REQUEST_URI = '/mailman3/hyperkitty/api/mailman/archive?key=0123456789abcdef012345678 9ABCDEF' SCRIPT_FILENAME = 'proxy:uwsgi://localhost//hyperkitty/api/mailman/archive' SCRIPT_NAME = '/mailman3' SERVER_ADDR = '127.0.0.1' SERVER_ADMIN = 'webmaster@localhost' SERVER_NAME = 'localhost' SERVER_PORT = '80' SERVER_PROTOCOL = 'HTTP/1.1' SERVER_SIGNATURE = '<address>Apache/2.4.38 (Debian) Server at localhost Port 80</address>\n' SERVER_SOFTWARE = 'Apache/2.4.38 (Debian)' uwsgi.core = 0 uwsgi.node = b'slc.mailhub4u.com' uwsgi.version = b'2.0.18-debian' wsgi.errors = <_io.TextIOWrapper name=2 mode='w' encoding='UTF-8'> wsgi.file_wrapper = '' wsgi.input = <uwsgi._Input object at 0x7f6a278df600> wsgi.multiprocess = False wsgi.multithread = True wsgi.run_once = False wsgi.url_scheme = 'http' 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', '[5]gordon(a)mailhub4u.com'),)" ALLOWED_HOSTS = ['*'] APPEND_SLASH = True AUTHENTICATION_BACKENDS = "('django.contrib.auth.backends.ModelBackend', 'allauth.account.auth_backends.AuthenticationBackend')" AUTH_PASSWORD_VALIDATORS = '********************' AUTH_USER_MODEL = 'auth.User' BASE_DIR = '/usr/share/mailman3-web' CACHES = {'default': {'BACKEND': 'django.core.cache.backends.locmem.LocMemCache'}} CACHE_MIDDLEWARE_ALIAS = 'default' CACHE_MIDDLEWARE_KEY_PREFIX = '********************' CACHE_MIDDLEWARE_SECONDS = 600 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_COMPRESSOR = 'compressor.css.CssCompressor' COMPRESS_CSS_FILTERS = ['compressor.filters.css_default.CssAbsoluteFilter'] COMPRESS_CSS_HASHING_METHOD = 'mtime' COMPRESS_DATA_URI_MAX_SIZE = 1024 COMPRESS_DEBUG_TOGGLE = None COMPRESS_ENABLED = True COMPRESS_JINJA2_GET_ENVIRONMENT = <function CompressorConf.JINJA2_GET_ENVIRONMENT at 0x7f6a2d586620> COMPRESS_JS_COMPRESSOR = 'compressor.js.JsCompressor' COMPRESS_JS_FILTERS = ['compressor.filters.jsmin.JSMinFilter'] COMPRESS_MINT_DELAY = 30 COMPRESS_MTIME_DELAY = 10 COMPRESS_OFFLINE = True COMPRESS_OFFLINE_CONTEXT = {'STATIC_URL': '/mailman3/static/'} COMPRESS_OFFLINE_MANIFEST = 'manifest.json' COMPRESS_OFFLINE_TIMEOUT = 31536000 COMPRESS_OUTPUT_DIR = 'CACHE' COMPRESS_PARSER = 'compressor.parser.AutoSelectParser' COMPRESS_PRECOMPILERS = "(('text/less', 'lessc {infile} {outfile}'), ('text/x-scss', 'sassc -t compressed {infile} {outfile}'), ('text/x-sass', 'sassc -t compressed {infile} {outfile}'))" COMPRESS_REBUILD_TIMEOUT = 2592000 COMPRESS_ROOT = '/var/lib/mailman3/web/static' COMPRESS_STORAGE = 'compressor.storage.CompressorFileStorage' COMPRESS_TEMPLATE_FILTER_CONTEXT = {'STATIC_URL': '/mailman3/static/'} COMPRESS_URL = '/mailman3/static/' COMPRESS_URL_PLACEHOLDER = '/__compressor_url_placeholder__/' COMPRESS_VERBOSE = False COMPRESS_YUGLIFY_BINARY = 'yuglify' COMPRESS_YUGLIFY_CSS_ARGUMENTS = '--terminal' COMPRESS_YUGLIFY_JS_ARGUMENTS = '--terminal' COMPRESS_YUI_BINARY = 'java -jar yuicompressor.jar' COMPRESS_YUI_CSS_ARGUMENTS = '' COMPRESS_YUI_JS_ARGUMENTS = '' CSRF_COOKIE_AGE = 31449600 CSRF_COOKIE_DOMAIN = None CSRF_COOKIE_HTTPONLY = False CSRF_COOKIE_NAME = 'csrftoken' CSRF_COOKIE_PATH = '/' CSRF_COOKIE_SECURE = False CSRF_FAILURE_VIEW = 'django.views.csrf.csrf_failure' CSRF_HEADER_NAME = 'HTTP_X_CSRFTOKEN' CSRF_TRUSTED_ORIGINS = [] CSRF_USE_SESSIONS = False DATABASES = {'default': {'ENGINE': 'django.db.backends.mysql', 'NAME': 'mailman3web', 'USER': 'mailman3web', 'PASSWORD': '********************', 'HOST': 'localhost', 'PORT': '', 'OPTIONS': {'init_command': "SET sql_mode='STRICT_TRANS_TABLES'"}, 'ATOMIC_REQUESTS': False, 'AUTOCOMMIT': True, 'CONN_MAX_AGE': 0, 'TIME_ZONE': None, 'TEST': {'CHARSET': None, 'COLLATION': None, 'NAME': None, 'MIRROR': None}}} DATABASE_ROUTERS = [] DATA_UPLOAD_MAX_MEMORY_SIZE = 2621440 DATA_UPLOAD_MAX_NUMBER_FIELDS = 1000 DATETIME_FORMAT = 'N j, Y, P' DATETIME_INPUT_FORMATS = ['%Y-%m-%d %H:%M:%S', '%Y-%m-%d %H:%M:%S.%f', '%Y-%m-%d %H:%M', '%Y-%m-%d', '%m/%d/%Y %H:%M:%S', '%m/%d/%Y %H:%M:%S.%f', '%m/%d/%Y %H:%M', '%m/%d/%Y', '%m/%d/%y %H:%M:%S', '%m/%d/%y %H:%M:%S.%f', '%m/%d/%y %H:%M', '%m/%d/%y'] DATE_FORMAT = 'N j, Y' DATE_INPUT_FORMATS = ['%Y-%m-%d', '%m/%d/%Y', '%m/%d/%y', '%b %d %Y', '%b %d, %Y', '%d %b %Y', '%d %b, %Y', '%B %d %Y', '%B %d, %Y', '%d %B %Y', '%d %B, %Y'] DEBUG = False DEBUG_PROPAGATE_EXCEPTIONS = False DECIMAL_SEPARATOR = '.' DEFAULT_CHARSET = 'utf-8' DEFAULT_CONTENT_TYPE = 'text/html' DEFAULT_EXCEPTION_REPORTER_FILTER = 'django.views.debug.SafeExceptionReporterFilter' DEFAULT_FILE_STORAGE = 'django.core.files.storage.FileSystemStorage' DEFAULT_FROM_EMAIL = '[6]postorius(a)host2.mailhub4u.com' DEFAULT_INDEX_TABLESPACE = '' DEFAULT_TABLESPACE = '' DISALLOWED_USER_AGENTS = [] EMAILNAME = 'host2.mailhub4u.com' EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_HOST_PASSWORD = '********************' EMAIL_HOST_USER = '' EMAIL_PORT = 25 EMAIL_SSL_CERTFILE = None EMAIL_SSL_KEYFILE = '********************' EMAIL_SUBJECT_PREFIX = '[Django] ' EMAIL_TIMEOUT = None EMAIL_USE_LOCALTIME = False EMAIL_USE_SSL = False EMAIL_USE_TLS = False FILE_CHARSET = 'utf-8' FILE_UPLOAD_DIRECTORY_PERMISSIONS = None FILE_UPLOAD_HANDLERS = ['django.core.files.uploadhandler.MemoryFileUploadHandler', 'django.core.files.uploadhandler.TemporaryFileUploadHandler'] FILE_UPLOAD_MAX_MEMORY_SIZE = 2621440 FILE_UPLOAD_PERMISSIONS = None FILE_UPLOAD_TEMP_DIR = None FILTER_VHOST = False FIRST_DAY_OF_WEEK = 0 FIXTURE_DIRS = [] FORCE_SCRIPT_NAME = None FORMAT_MODULE_PATH = None FORM_RENDERER = 'django.forms.renderers.DjangoTemplates' HAYSTACK_CONNECTIONS = {'default': {'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', 'PATH': '/var/lib/mailman3/web/fulltext_index'}} HOSTNAME = 'localhost.local' IGNORABLE_404_URLS = [] INSTALLED_APPS = "('hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount')" 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'), ('ia', 'Interlingua'), ('id', 'Indonesian'), ('io', 'Ido'), ('is', 'Icelandic'), ('it', 'Italian'), ('ja', 'Japanese'), ('ka', 'Georgian'), ('kk', 'Kazakh'), ('km', 'Khmer'), ('kn', 'Kannada'), ('ko', 'Korean'), ('lb', 'Luxembourgish'), ('lt', 'Lithuanian'), ('lv', 'Latvian'), ('mk', 'Macedonian'), ('ml', 'Malayalam'), ('mn', 'Mongolian'), ('mr', 'Marathi'), ('my', 'Burmese'), ('nb', 'Norwegian Bokmål'), ('ne', 'Nepali'), ('nl', 'Dutch'), ('nn', 'Norwegian Nynorsk'), ('os', 'Ossetic'), ('pa', 'Punjabi'), ('pl', 'Polish'), ('pt', 'Portuguese'), ('pt-br', 'Brazilian Portuguese'), ('ro', 'Romanian'), ('ru', 'Russian'), ('sk', 'Slovak'), ('sl', 'Slovenian'), ('sq', 'Albanian'), ('sr', 'Serbian'), ('sr-latn', 'Serbian Latin'), ('sv', 'Swedish'), ('sw', 'Swahili'), ('ta', 'Tamil'), ('te', 'Telugu'), ('th', 'Thai'), ('tr', 'Turkish'), ('tt', 'Tatar'), ('udm', 'Udmurt'), ('uk', 'Ukrainian'), ('ur', 'Urdu'), ('vi', 'Vietnamese'), ('zh-hans', 'Simplified Chinese'), ('zh-hant', 'Traditional Chinese')] LANGUAGES_BIDI = ['he', 'ar', 'fa', 'ur'] LANGUAGE_CODE = 'en-us' LANGUAGE_COOKIE_AGE = None LANGUAGE_COOKIE_DOMAIN = None LANGUAGE_COOKIE_NAME = 'django_language' LANGUAGE_COOKIE_PATH = '/' LOCALE_PATHS = [] LOGGING = {'version': 1, 'disable_existing_loggers': False, 'filters': {'require_debug_false': {'()': 'django.utils.log.RequireDebugFalse'}}, 'handlers': {'mail_admins': {'level': 'ERROR', 'filters': ['require_debug_false'], 'class': 'django.utils.log.AdminEmailHandler'}, 'file': {'level': 'INFO', 'class': 'logging.handlers.RotatingFileHandler', 'filename': '/var/log/mailman3/web/mailman-web.log', 'formatter': 'verbose'}, 'console': {'class': 'logging.StreamHandler', 'formatter': 'simple'}}, 'loggers': {'django.request': {'handlers': ['mail_admins', 'file'], 'level': 'INFO', 'propagate': True}, 'django': {'handlers': ['file'], 'level': 'INFO', 'propagate': True}, 'hyperkitty': {'handlers': ['file'], 'level': 'INFO', 'propagate': True}, 'postorius': {'handlers': ['file'], 'level': 'INFO', 'propagate': True}}, 'formatters': {'verbose': {'format': '%(levelname)s %(asctime)s %(process)d %(name)s %(message)s'}, 'simple': {'format': '%(levelname)s %(message)s'}}} LOGGING_CONFIG = 'logging.config.dictConfig' LOGIN_REDIRECT_URL = 'list_index' LOGIN_URL = 'account_login' LOGOUT_REDIRECT_URL = None LOGOUT_URL = 'account_logout' MAILMAN_ARCHIVER_FROM = "('127.0.0.1', '::1')" 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')" MIDDLEWARE_CLASSES = ['django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware'] MIGRATION_MODULES = {} MONTH_DAY_FORMAT = 'F j' NUMBER_GROUPING = 0 PASSWORD_HASHERS = '********************' PASSWORD_RESET_TIMEOUT_DAYS = '********************' POSTORIUS_TEMPLATE_BASE_URL = '[7]http://localhost/mailman3/' PREPEND_WWW = False Q_CLUSTER = {'timeout': 300, 'save_limit': 100, 'orm': 'default', 'poll': 5} ROOT_URLCONF = 'urls' SECRET_KEY = '********************' SECURE_BROWSER_XSS_FILTER = False SECURE_CONTENT_TYPE_NOSNIFF = False SECURE_HSTS_INCLUDE_SUBDOMAINS = False SECURE_HSTS_PRELOAD = False SECURE_HSTS_SECONDS = 0 SECURE_PROXY_SSL_HEADER = None SECURE_REDIRECT_EXEMPT = [] SECURE_SSL_HOST = None SECURE_SSL_REDIRECT = False SERVER_EMAIL = '[8]root(a)host2.mailhub4u.com' 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_SECURE = False SESSION_ENGINE = 'django.contrib.sessions.backends.db' SESSION_EXPIRE_AT_BROWSER_CLOSE = False SESSION_FILE_PATH = None SESSION_SAVE_EVERY_REQUEST = False SESSION_SERIALIZER = 'django.contrib.sessions.serializers.PickleSerializer' SETTINGS_MODULE = 'settings' SHORT_DATETIME_FORMAT = 'm/d/Y P' SHORT_DATE_FORMAT = 'm/d/Y' SIGNING_BACKEND = 'django.core.signing.TimestampSigner' SILENCED_SYSTEM_CHECKS = [] SITE_ID = 1 SOCIALACCOUNT_PROVIDERS = {} STATICFILES_DIRS = '()' STATICFILES_FINDERS = "('django.contrib.staticfiles.finders.FileSystemFinder', 'django.contrib.staticfiles.finders.AppDirectoriesFinder', 'compressor.finders.CompressorFinder')" STATICFILES_STORAGE = 'django.contrib.staticfiles.storage.StaticFilesStorage' STATIC_ROOT = '/var/lib/mailman3/web/static' STATIC_URL = '/mailman3/static/' TEMPLATES = [{'BACKEND': 'django.template.backends.django.DjangoTemplates', 'DIRS': [], 'APP_DIRS': True, 'OPTIONS': {'context_processors': ['django.template.context_processors.debug', 'django.template.context_processors.i18n', 'django.template.context_processors.media', 'django.template.context_processors.static', 'django.template.context_processors.tz', 'django.template.context_processors.csrf', 'django.template.context_processors.request', 'django.contrib.auth.context_processors.auth', 'django.contrib.messages.context_processors.messages', 'django_mailman3.context_processors.common', 'hyperkitty.context_processors.common', 'postorius.context_processors.postorius']}}] TEST_NON_SERIALIZED_APPS = [] TEST_RUNNER = 'django.test.runner.DiscoverRunner' THOUSAND_SEPARATOR = ',' TIME_FORMAT = 'P' TIME_INPUT_FORMATS = ['%H:%M:%S', '%H:%M:%S.%f', '%H:%M'] TIME_ZONE = 'UTC' USE_ETAGS = False USE_I18N = True USE_L10N = True USE_THOUSAND_SEPARATOR = False USE_TZ = True USE_X_FORWARDED_HOST = True USE_X_FORWARDED_PORT = False WSGI_APPLICATION = 'wsgi.application' X_FRAME_OPTIONS = 'SAMEORIGIN' YEAR_MONTH_FORMAT = 'F Y' References 1. mailto:root@host2.mailhub4u.com 2. mailto:gordon@mailhub4u.com 3. http://localhost/mailman3/hyperkitty/api/mailman/archive?key=0123456789abcd… 4. mailto:members@georgiajets.org 5. mailto:gordon@mailhub4u.com 6. mailto:postorius@host2.mailhub4u.com 7. http://localhost/mailman3/ 8. mailto:root@host2.mailhub4u.com

6 28

import an mm3 hyperkitty archive
by Eggert Ehmke 09 Dec '22

09 Dec '22

I was able to export the archive of my old mm3 installation in hyperkitty. However, I seem to be blind when looking for hyperkitty_import in the documentation. Where to start?

3 4

What is this EMail trying to tell me
by Martin Lorenz 09 Dec '22

09 Dec '22

Since I rebootet my VPS yesterday I get tons of these and can't find out what's wrong. Please help. -------- Weitergeleitete Nachricht -------- Betreff: [Django] ERROR (EXTERNAL IP): Service Unavailable: /mailman3/lists/ku-venne-2020.list.poc.im/ Datum: Fri, 09 Dec 2022 04:58:15 -0000 Von: django(a)poc.im An: root@localhost Service Unavailable: /mailman3/lists/ku-venne-2020.list.poc.im/ Report at /mailman3/lists/ku-venne-2020.list.poc.im/ Service Unavailable: /mailman3/lists/ku-venne-2020.list.poc.im/ Request Method: GET Request URL: http://list.holoclan.de/mailman3/lists/ku-venne-2020.list.poc.im/ Django Version: 3.0.14 Python Executable: /opt/mailman/venv/bin/uwsgi Python Version: 3.9.2 Python Path: ['.', '', '/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: Fri, 9 Dec 2022 04:58:15 +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') Request information: USER: AnonymousUser GET: No GET data POST: No POST data FILES: No FILES data COOKIES: No cookie data META: HTTP_ACCEPT = '*/*' HTTP_ACCEPT_CHARSET = 'utf-8;q=0.7,iso-8859-1;q=0.2,*;q=0.1' HTTP_CONNECTION = 'close' HTTP_HOST = 'list.holoclan.de' HTTP_USER_AGENT = 'Mozilla/5.0 (compatible; DotBot/1.2; +https://opensiteexplorer.org/dotbot; help(a)moz.com)' HTTP_X_FORWARDED_FOR = '216.244.66.197' HTTP_X_FORWARDED_HOST = 'list.holoclan.de' HTTP_X_FORWARDED_PROTO = 'http' PATH_INFO = '/mailman3/lists/ku-venne-2020.list.poc.im/' QUERY_STRING = '' REMOTE_ADDR = '127.0.0.1' REQUEST_METHOD = 'GET' REQUEST_URI = '/mailman3/lists/ku-venne-2020.list.poc.im/' SCRIPT_NAME = '' SERVER_NAME = 'arda.holoclan.de' SERVER_PORT = '8000' SERVER_PROTOCOL = 'HTTP/1.0' uwsgi.core = 1 uwsgi.node = b'arda.holoclan.de' 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 0x7f8d77ae15f0> wsgi.multiprocess = True wsgi.multithread = True wsgi.run_once = False wsgi.url_scheme = 'http' 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', 'root@localhost'),)" ALLOWED_HOSTS = ['localhost', '127.0.0.1', 'list.holoclan.de', 'list.poc.im', 'list.lorenz.im'] 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 0x7f8d816d30d0> COMPRESS_MINT_DELAY = 30 COMPRESS_MTIME_DELAY = 10 COMPRESS_OFFLINE = True COMPRESS_OFFLINE_CONTEXT = {'STATIC_URL': '/static/'} COMPRESS_OFFLINE_MANIFEST = 'manifest.json' COMPRESS_OFFLINE_MANIFEST_STORAGE = 'compressor.storage.OfflineManifestFileStorage' 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': 'mailmanweb', '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)list.poc.im' 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 = '' 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': '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 = 'django(a)poc.im' 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 1

About mailman-core service upgrade adaptation
by 朱超 08 Dec '22

08 Dec '22

When i upgrade mailman-core from 3.2.2 to 3.3.7, I find some change in table, for example: hyperkitty_email、hyperkitty_thread、member、openid_openidnonce、openid_openidstore， The community have some tools to help me to upgrade?

2 1

Problems after update to mailman 3.3.7
by Guillermo Hernandez (Oldno7) 07 Dec '22

07 Dec '22

I've getting the most strange behaviour after update to last releases. In one of my mailman3 servers, the messages doesnt reach for some lists (the five last ones) the update have not showed any error but in the var/data for the lmtp and vmap postfix files mailman does not create aliases for that last 5 lists. Any message addressed to them is returned with a "no such user" error. If I create a new list the system or restart mailman runners it shows this error: Generating MTA alias maps /usr/local/lib/python3.9/site-packages/pymysql/connections.py:799: UserWarning: Previous unbuffered result was left incomplete warnings.warn("Previous unbuffered result was left incomplete") I did a CHECK TABLE on mailinglists table but all seems ok. I tried reinstalling PyMySQL, but has no effect. (well, I tried reinstalling all) It seems to me that something is preventing creation of that aliases, an then the that last five lists are unreachable. I have no clue of what to do now and I'm driving crazy. Some direction to look for will be much apreciated. Thanks in advance. P.S.: I can access via postorius/hyperkitty to the archives of the lists that are unreacheable. -- ___________________________________________ 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.

3 5

Strange messages after upgrading Mailman3
by Allan Hansen 06 Dec '22

06 Dec '22

Hi all, I have been getting a few of these messages after my Mailman 3 was upgraded: "The content of this message was lost. It was probably cross-posted to multiple lists and previously handled on another list." The messages appear to come from list members and are distributed to the relevant lists, but with nothing of the original contents. They have appeared on different lists with, apparently different senders (unless spoofed). Other messages are going through the system unchanged. Anyone has any ideas? Yours, Allan

2 5

Issues encountered while upgrading to 3.3.7
by Odhiambo Washington 05 Dec '22

05 Dec '22

Hello everyone, I am starting a new thread on this so that the issues I encountered do not get mixed up with the other discussions. Over the weekend I upgraded an MM3 installation to the latest versions of the components. I started off by creating a new venv, installing and then migrating the configurations and the scripts. In the end, I ended up with MM3 Core ==3.3.7, postorius==1.3.7, HyperKitty==1.3.6, django==4.1.3. 1. SQLAlchemy - At the stage where one runs 'mailman info', I encountered the first error: : sqlalchemy.exc.NoSuchModuleError: Can't load plugin: sqlalchemy.dialects:postgres This is solved by a change in mailman.cfg so that the URI starts with postgresql:// instead of postgres://. SQLAlchemy used to accept both but has removed support for the postgres name. <https://github.com/sqlalchemy/sqlalchemy/issues/6083#issuecomment-801478013> 2. Django==4.x At the point of running the post-update processes, particularly the "migrate" bit, I got the following error: : ImportError: cannot import name 'url' from 'django.conf.urls' (/opt/mailman/mm/venv/lib/python3.9/site-packages/django/conf/urls/__init__.py) I understand this is a consequence of the django.conf.urls.url() having been deprecated starting version 3 and has been removed in version 4 of Django. https://docs.djangoproject.com/en/4.1/releases/4.0/#features-removed-in-4-0 The upgrade process seems to have brought in the newer version of Django because now I have 4.1.3 up from 3.x If anyone wants, I found an elaborate explanation at https://bobbyhadz.com/blog/python-importerror-cannot-import-name-url-from-d… . My Google-fu found suggestions that in urls.py, I should import re_path and use it, or alias it for url for the migrate to work. The solution I used was to alias url to re_path, but I am considering just doing away with url altogether. Not sure which is the better option between using re_path or path. So here is the patch I have used: (venv) mailman@lists:~/mm$ diff -u urls.py.bak urls.py --- urls.py.bak 2022-12-03 12:20:28.028090659 +0300 +++ urls.py 2022-12-03 12:36:20.298875624 +0300 @@ -17,7 +17,8 @@ # Postorius. If not, see <http://www.gnu.org/licenses/>. -from django.conf.urls import include, url +from django.conf.urls import include +from django.urls import re_path as url from django.contrib import admin from django.urls import reverse_lazy from django.views.generic import RedirectView 3. The last issue that I encountered is one I kind of solved, but completely don't understand the consequences of the solution I applied: /opt/mailman/mm/bin/django-admin migrate <CUT> System check identified some issues: WARNINGS: django_mailman3.MailDomain: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the DjangoMailman3Config.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. django_mailman3.Profile: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the DjangoMailman3Config.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Attachment: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Email: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Favorite: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.LastView: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.MailingList: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Profile: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Tag: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Tagging: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Thread: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.ThreadCategory: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Vote: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. postorius.EmailTemplate: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the PostoriusConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount </CUT> Here again, Google-fu came to the rescue. I added the following line to settings_local.py and the warnings were suppressed. DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' I need to understand how this affects everything and how this is likely to impact the functionality of MM3. What is the proper solution for this? And should it be django.db.models.BigAutoField or django.db.models.AutoField? Which is which? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 5

Handling of spam
by Eggert Ehmke 05 Dec '22

05 Dec '22

I have a mailing list that is open to nonmembers. Sometimes we get spam on that list. I have a working spamassassin/amavis spam filter on the system. Now comes the strange part: sometimes a spam message is put into a multi-part message and forwarded to the list owner (me). This multi-part message contains the message marked as spam, but is not marked as spam itself. The origin of those message is the bounces address of the list. So my first question is: where can those messages be generated? I can provide the message header, but it would contain a lot of details of my server. Cheers, Eggert

2 1

Is there an easy way to set Reply-To to a lists owner?
by Martin Lorenz 04 Dec '22

04 Dec '22

Hi again, now, that Mailman3 is running smoothly I have a new question. We have a bunch of lists, which are only used for spreading news. Now the admin of theses lists (who happens to be my wife) asked me, if it was possible to change the settings such that all replys to one of these lists can only be sent to herself (i.e. the owner address) instead of being held for moderation. I thought of setting Reply-To to something like <list-owner> by "simply" entering a Variable into this field, instead of using the admins/owners literal email-address. Is this possible? Or is there another way of achieving the goal? TNX Greetings Martin

2 1

Weird startup problem after upgrade
by Odhiambo Washington 03 Dec '22

03 Dec '22

I am facing an odd situation in which MM3 doesn't start successfully on reboot, but I can start it manually. This is a venv install. This started after I did an upgrade (pip install --upgrade mailman postorius hyperkitty mailman-hyperkitty) followed by the requisite collectstatic|compress|compilemessages|migrate post-update commands. Secondly, it appears that the upgrade did NOT change the versions for the upgraded components - postorius=1.3.6, hyperkitty=1.3.5, Mailman Core Version=3.3.5. I was expecting the version to all bump up to the latest. Thanks in advance for any insights into what could be causing this. wash@lists:~$ systemctl status mailman3 × mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; vendor preset: enabled) Active: failed (Result: timeout) since Fri 2022-12-02 18:58:13 EAT; 9s ago CPU: 25.241s Dec 02 18:58:12 lists mailman[1637]: File "/opt/mailman/mm/venv/lib/python3.10/site-packages/mailman/core/runner.py", line 114, in signal_handler Dec 02 18:58:12 lists mailman[1639]: for atexit_call in reversed(_threading_atexits): Dec 02 18:58:12 lists mailman[1639]: File "/opt/mailman/mm/venv/lib/python3.10/site-packages/mailman/core/runner.py", line 114, in signal_handler Dec 02 18:58:12 lists mailman[1637]: raise RunnerInterrupt Dec 02 18:58:12 lists mailman[1639]: raise RunnerInterrupt Dec 02 18:58:12 lists mailman[1637]: mailman.interfaces.runner.RunnerInterrupt: Dec 02 18:58:12 lists mailman[1639]: mailman.interfaces.runner.RunnerInterrupt: Dec 02 18:58:13 lists systemd[1]: mailman3.service: Failed with result 'timeout'. Dec 02 18:58:13 lists systemd[1]: Failed to start GNU Mailing List Manager. Dec 02 18:58:13 lists systemd[1]: mailman3.service: Consumed 25.241s CPU time. root@lists:/home/wash# systemctl status mailman3 × mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; vendor preset: enabled) Active: *failed (Result: timeout) since Fri 2022-12-02 18:58:13 EAT; 53s ago* CPU: 25.241s Dec 02 18:58:12 lists mailman[1637]: File "/opt/mailman/mm/venv/lib/python3.10/site-packages/mailman/core/runner.py", line 114, in signal_handler Dec 02 18:58:12 lists mailman[1639]: for atexit_call in reversed(_threading_atexits): Dec 02 18:58:12 lists mailman[1639]: File "/opt/mailman/mm/venv/lib/python3.10/site-packages/mailman/core/runner.py", line 114, in signal_handler Dec 02 18:58:12 lists mailman[1637]: raise RunnerInterrupt Dec 02 18:58:12 lists mailman[1639]: raise RunnerInterrupt Dec 02 18:58:12 lists mailman[1637]: mailman.interfaces.runner.RunnerInterrupt: Dec 02 18:58:12 lists mailman[1639]: mailman.interfaces.runner.RunnerInterrupt: *Dec 02 18:58:13 lists systemd[1]: mailman3.service: Failed with result 'timeout'.Dec 02 18:58:13 lists systemd[1]: Failed to start GNU Mailing List Manager.Dec 02 18:58:13 lists systemd[1]: mailman3.service: Consumed 25.241s CPU time.* root@lists:/home/wash# cd /opt/mailman/mm/var/logs/ root@lists:/opt/mailman/mm/var/logs# ls -al total 104948 drwxr-xr-x 2 mailman mailman 4096 Dec 2 18:56 . drwxr-xr-x 12 mailman mailman 4096 Dec 2 18:58 .. -rw-r--r-- 1 mailman mailman 7720631 Dec 2 18:52 access.log -rw-rw---- 1 mailman mailman 1514 Nov 28 05:58 bounce.log -rw-rw---- 1 mailman mailman 0 Aug 15 16:56 debug.log -rw-r--r-- 1 mailman mailman 497 Dec 2 18:56 error.log -rw-rw---- 1 mailman mailman 99339919 Dec 2 18:58 mailman.log -rw-r--r-- 1 mailman mailman 0 Dec 2 18:53 mailmansuite.log -rw-rw---- 1 mailman mailman 0 Aug 15 16:56 plugins.log -rw-rw---- 1 mailman mailman 374961 Dec 2 18:56 smtp.log root@lists:/opt/mailman/mm/var/logs# less error.log root@lists:/opt/mailman/mm/var/logs# cd ../locks/ root@lists:/opt/mailman/mm/var/locks# ls -al total 8 drwxr-xr-x 2 mailman mailman 4096 Dec 2 18:58 . drwxr-xr-x 12 mailman mailman 4096 Dec 2 18:58 .. root@lists:/opt/mailman/mm/var/locks# systemctl start mailman3 root@lists:/opt/mailman/mm/var/locks# systemctl status mailman3 ● mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2022-12-02 19:00:15 EAT; 11s ago Process: 2395 ExecStart=/opt/mailman/mm/bin/mailman start (code=exited, status=0/SUCCESS) Main PID: 2397 (python3) Tasks: 18 (limit: 4550) Memory: 791.9M CPU: 21.440s CGroup: /system.slice/mailman3.service ├─2397 /opt/mailman/mm/venv/bin/python3 /opt/mailman/mm/venv/bin/master -C /opt/mailman/mm/mailman.cfg ├─2398 /opt/mailman/mm/venv/bin/python3 /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=archive:0:1 ├─2399 /opt/mailman/mm/venv/bin/python3 /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=bounces:0:1 ├─2400 /opt/mailman/mm/venv/bin/python3 /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=command:0:1 ├─2401 /opt/mailman/mm/venv/bin/python3 /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=in:0:1 ├─2402 /opt/mailman/mm/venv/bin/python3 /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=lmtp:0:1 ├─2403 /opt/mailman/mm/venv/bin/python3 /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=nntp:0:1 ├─2404 /opt/mailman/mm/venv/bin/python3 /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=out:0:1 ├─2405 /opt/mailman/mm/venv/bin/python3 /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=pipeline:0:1 ├─2406 /opt/mailman/mm/venv/bin/python3 /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=rest:0:1 ├─2407 /opt/mailman/mm/venv/bin/python3 /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=retry:0:1 ├─2408 /opt/mailman/mm/venv/bin/python3 /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=task:0:1 ├─2409 /opt/mailman/mm/venv/bin/python3 /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=virgin:0:1 ├─2410 /opt/mailman/mm/venv/bin/python3 /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=digest:0:1 ├─2423 /opt/mailman/mm/venv/bin/python3 /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=rest:0:1 └─2424 /opt/mailman/mm/venv/bin/python3 /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=rest:0:1 Dec 02 19:00:13 lists systemd[1]: Starting GNU Mailing List Manager... Dec 02 19:00:14 lists mailman[2395]: Starting Mailman's master runner Dec 02 19:00:14 lists mailman[2395]: Generating MTA alias maps *Dec 02 19:00:14 lists systemd[1]: mailman3.service: Can't open PID file /opt/mailman/mm/var/master.pid (yet?) after start: Operation not permitted* Dec 02 19:00:15 lists systemd[1]: Started GNU Mailing List Manager. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 4

Permission denied for fulltext_index
by Jan Eden 01 Dec '22

01 Dec '22

Hi, when trying to reattach a message thread in the Hyperkitty web interface, the following error occurs: > Internal Server Error: /archives/list/testlist(a)lists.eden.one/thread/T6MCILAVQYV5QIOGHJB3JNJ26Z7E2Z35/reattach-suggest > > PermissionError at /archives/list/testlist(a)lists.eden.one/thread/T6MCILAVQYV5QIOGHJB3JNJ26Z7E2Z35/reattach-suggest > [Errno 13] Permission denied: 'fulltext_index' The error occurs while haystack attempts to create a directory – > File "/opt/mailman/venv/lib/python3.10/site-packages/haystack/backends/whoosh_backend.py", line 412, in search > self.setup() > File "/opt/mailman/venv/lib/python3.10/site-packages/haystack/backends/whoosh_backend.py", line 133, in setup > os.makedirs(self.path) > File "/usr/lib/python3.10/os.py", line 225, in makedirs > mkdir(name, mode) > > Exception Type: PermissionError at /archives/list/testlist(a)lists.eden.one/thread/T6MCILAVQYV5QIOGHJB3JNJ26Z7E2Z35/reattach-suggest > Exception Value: [Errno 13] Permission denied: 'fulltext_index' > Raised during: hyperkitty.views.thread.reattach_suggest > Request information: > USER: mailman – but the existing directory /opt/mailman/fulltext_index (and its contents) are readable and writeable by mailman:mailman: > drwxrwxr-x 2 mailman mailman 4096 Nov 27 08:00 fulltext_index/ > > -rw-rw-r-- 1 mailman mailman 4473 Nov 27 08:00 _MAIN_65.toc > -rw-rw-r-- 1 mailman mailman 15456 Nov 27 08:00 MAIN_bc0cs2aohovftat6.seg > -rw-rw-r-- 1 mailman mailman 15454 Nov 27 06:00 MAIN_brbo8i8edmlz0za4.seg > -rw-rw-r-- 1 mailman mailman 15462 Nov 27 07:00 MAIN_ewnemc7lsnodd3y7.seg > -rw-rw-r-- 1 mailman mailman 157324 Nov 27 04:00 MAIN_qag60g1rrumshtc2.seg > -rw-rw-r-- 1 mailman mailman 15459 Nov 27 05:00 MAIN_w6e0ohurasusy61d.seg > -rwxrwxr-x 1 mailman mailman 0 Nov 24 16:00 MAIN_WRITELOCK* I fail to see where haystack tries (and fails) to create the directory. FWIW, deleting threads is not a problem. Thanks, Jan

2 10

Mailman web interface / uwsgi
by Jan Eden 28 Nov '22

28 Nov '22

Hi, I followed the installation instructions at https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…, which thankfully shielded me from configuring the Django applications for the web interface manually. All Django applications (postorius, hyperkitty, haystack etc) are loaded via mailman_web/settings/base.py, which is in turn referenced by the top-level settings file in /etc/mailman3. uwsgi is linked to mailman_web via /etc/mailman3/uwsgi.ini. So far, so good. I do not want to dive into the interaction between the various components and just want to switch from a http socket (http-socket = 0.0.0.0:8000) to a file socket (socket = /opt/mailman/mm/var/mailman.sock). After making this change in /etc/mailman3/uwsgi.ini, I applied it in the nginx proxy configuration proxy_pass http://127.0.0.1:8000; → proxy_pass http://unix:/opt/mailman/mm/var/mailman.sock; and received an error message (as expected): 2022/11/25 18:39:12 [error] 2978606#2978606: *3 upstream prematurely closed connection while reading response header from upstream, client: 37.201.155.65, server: lists.eden.one, request: "GET /mailman3/lists/ HTTP/2.0", upstream: "http://unix:/opt/mailman/mm/var/mailman.sock:/mailman3/lists/", host: "lists.eden.one" There are obviously a couple of places where the http-socket on port 8000 is referenced (e.g. mailman_web/settings/mailman.py, /opt/mailman/mm/hyperkitty.cfg). Is there an overview of the required changes when using a different (file) socket? Related question: My own (much simpler) Django applications use the following (e.g. in mysite_nginx.conf): upstream django { server unix:///private/tmp/mysite.sock; } location / { uwsgi_pass django; } instead of the "http://unix:/..." notation I tried for Mailman above. Is there any difference between the upstream/uwsgi_pass combination and the proxy_pass variant? Thanks, Jan

3 8

Default list styles
by Jan Eden 27 Nov '22

27 Nov '22

Hi, the list creation web interface offers three list styles (announce, ordinary, ordinary w/ private archive). When selecting the announce style, I would expect a different default message acceptance setting for members (i.e. reject), because this is how an announce list should work. In practice, a list created with the announce style is configured just as an ordinary mailing list (as far as I can see in the web interface, and according to the handling of a test message sent by a regular member of an announce list). What am I missing here? - Jan

2 1

Mailman3 not able to deliver emails sent through list, but moderation notifications
by Daniel Böhmer 27 Nov '22

27 Nov '22

Hello Mailman users, I've been using Mailman2 for 10+ years and have recently upgraded to Debian Buster with Mailman3. I've tried to setup Mailman3 similarly but it fails to deliver emails sent through a list. I do receive all moderation notifications at the same time. During startup /var/log/mailman3/mailman.log receives: > Cannot connect to SMTP server localhost on port 25 but I've made sure postfix is listening on *:25 for both IPv4 and IPv6. When sending a message to a list the same file receives: > Nov 25 11:38:14 2022 (70371) ACCEPT: <MESSAGEID@HOST> (message ID and host redacted) and nothing else happens: no more log messages, Postfix logs the email sent TO Mailman but doesn't log anything about emails sent BY Mailman. If Mailman fails to send emails via Postfix I'd expect it to log error messages but it doesn't seem to do so. I found this article stating the the SMTP error message might be misleading: https://blog.tfiu.de/mailman3-cannot-connect-to-smtp-server-localhost-on-po… How to further debug this? What could be wrong with my Mailman3 instance and how to fix it? Kind regards Daniel Böhmer

3 5

MTA authentication and smtpd_sender_login_maps
by Jan Eden 25 Nov '22

25 Nov '22

Hi, I installed Mailman3 successfully and would like to change the default smtp settings to an authenticated connection (smtp_user, smtp_pass). But my Postfix configuration restricts sending messages via the smtpd_sender_login_maps directive (which points to a hashed file I created years ago) and correctly refuses connections for messages with the test mailing list's From header. I obviously do not want to add an entry to the map file for each mailing list created by someone on the server. Is there a way to programmatically create a sender login map with Mailman? Thanks, Jan

2 2

Hyperkitty no longer archiving
by Hirayama, Pat 23 Nov '22

23 Nov '22

Greetings, A couple of months ago, I needed to move the Mailman3 server I inherited from one AWS account to another AWS account. This necessitated a change in the IP address of instance hosting the docker containers that comprise my mailman3 server. I thought I had updated the IP address wherever it needed to be, but I suppose I've missed something, because hyperkitty has not been archiving any messages. (Most of my lists don't archive, so it took a while before someone noticed). When I look at /opt/mailman/var/archives/hyperkitty/spool, I see messages dating back over the past couple of months waiting to be archived. So, they don't appear to be lost (and things are being mailed out normally). The thing is, the IP addresses of the docker containers haven't changed with respect to docker networking. docker networking ------------------------ docker host 172.31.0.1 mailman-core 172.31.0.3 mailman-nginx 172.31.0.5 mailman-postfix 172.31.0.4 mailman-django-uwsgi 172.31.0.2 settings_local.py: MAILMAN_ARCHIVER_FROM = ('172.18.8.14', '172.31.0.1', '172.31.0.2', '172.31.0.3', '172.31.0.4', '172.31.0.5', '127.0.0.1', '::1') During troubleshooting, I added 172.18.8.14 (new IP of the webserver), but that didn't seem to help. It seems like I added one of the docker addresses that was missing .... but again, that doesn't seem to have fixed the issue. mailmansuite.log is full of: ERROR 2022-11-22 00:25:40,365 7 hyperkitty.views.mailman Access to the archiving API endpoint was forbidden from IP 172.31.0.1, your MAILMAN_ARCHIVER_FROM setting may be misconfigured ERROR 2022-11-22 00:25:40,399 7 hyperkitty.views.mailman Access to the archiving API endpoint was forbidden from IP 172.31.0.1, your MAILMAN_ARCHIVER_FROM setting may be misconfigured Any suggestions as to where I might look for a solution, or what setting I need to change? Thanks! -p Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering Fred Hutchinson Cancer Center O 206.667.4856 phirayam(a)fredhutch.org<mailto:phirayam@fredhutch.org>

4 12

Upgrading a Ubuntu Mailman 3 Installation
by Allan Hansen 21 Nov '22

21 Nov '22

Dear Mailman 3 wizards, Several years ago I tried upgrading to Mailman 3 (I did install Mailman 2), but quickly ran into a thicket too complex for me to get out of. Two others - way more experienced than me at system-level manipulations - tried as well but did not succeed. Brian Carpenter of EMWD installed the system seemingly effortlessly, and seemingly overnight. We had a good relationship, and I was a beta site for his new product, SAAS. Brian also did the system MM3 upgrades as they appeared and would check that all was well a couple of times a year. Unfortunately, and I respect that, the current management at EMWD "don't provide working hands service for foreign Mailman 3 installations." I do not dare touch it, based on my earlier attempts with the installation. With Brian's passing I'm thus faced with a system that has no capable system support (I manage the lists, not the core). I have 50+ lists with 10000+ subscription total, and a lot of people depend on this tool. (It's a non-profit organization). So, I'm interesting in hiring someone for part-time, occasional work (a few times a year). Update MM3 as new versions are made available. Diagnose and fix the system if anything goes awry. I will pay you, as I did Brian, out of my own pocket, for your time. Yours, Allan Hansen

2 1

Migrating to mailman-web and Ubuntu 22.04
by Andrew Hodgson 16 Nov '22

16 Nov '22

Hi. For various reasons I want to migrate to a larger host running Ubuntu 22.04. I have set up the various packages ok and as part of the migration I want to use mailman-web instead of mailman-suite which is an older setup. I have instructions for Mailman-web for setting up Uwsgi but I would prefer to keep Gunicorn working as per the instructions here: DOC/Mailman 3 installation experience - Mailman Wiki (list.org)<https://wiki.list.org/DOC/Mailman%203%20installation%20experience> Has anyone done this before? Thanks. Andrew.

3 5

New Mailman Core Release
by Mark Sapiro 15 Nov '22

15 Nov '22

We are pleased to announce the release of Mailman core 3.3.7. It is published to PyPI and you can find links to all the PyPI projects: https://docs.mailman3.org/en/latest/ The change log is at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… - please note the `BREAKING CHANGE` documented there and due to our now using SQLAlchemy >-1.4. Finally, the minimum Python version required is 3.7 although, 3.9 is recommended if you are doing a new install for longest support. 3.10 is supported for Django apps, but Mailman Core is missing that due to one of the core dependencies (aiosmtpd) not supporting 3.10 yet. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Do not display any lists on index the page (/postorius/lists/) by default (when you create the list it defaults to Hide) - Debian package install
by daniel.botting＠codethink.co.uk 11 Nov '22

11 Nov '22

Hi all, I am currently in the process of moving from mailman 2.1 to mailman 3, the basic functions are completed (mailing list and archiving). On our current mailman 2.1 install it advises there are no publicly advertised lists, when I visit mailman3-list.domain/postorius/lists/ I see all the lists that have been created, I require them not to be displayed. I know when you create a list you can on the 'Advertise this list' line select 'Hide this list in list index', but I would like it to default to this in case somebody forgets to select it. I am not a Python expert, though from the description at the top of the below file and the contents further down it looks like you are defining in base.py and then in default.py you are using what was defined, a class of 'Private' which should cause the lists not to be advertised, but they are? File: /usr/ib/python3/dist-packages/mailman/styles/base.py class Private: """Settings for private mailing lists.""" def apply(self, mailing_list): mlist = mailing_list mlist.advertised = False <-------------- mlist.archive_policy = ArchivePolicy.private mlist.subscription_policy = SubscriptionPolicy.confirm_then_moderate File: /usr/lib/python3/dist-packages/mailman/styles/default.py class PrivateDefaultStyle( Identity, BasicOperation, Bounces, Private, Discussion, Moderation): """Style for mailing-lists with private archives.""" name = 'private-default' description = _('Discussion mailing list style with private archives.') def apply(self, mailing_list): """See `IStyle`.""" Identity.apply(self, mailing_list) BasicOperation.apply(self, mailing_list) Bounces.apply(self, mailing_list) Private.apply(self, mailing_list) Discussion.apply(self, mailing_list) Moderation.apply(self, mailing_list) I added the below to /etc/mailman3/mailman.cfg: [styles] # The default style to apply if nothing else was requested. The value is the # name of an existing style. If no such style exists, no style will be # applied. default: private-default I took 'private-default' from /usr/lib/python3/dist-packages/mailman/styles/default.py, this means now when a new list is created the List style is 'Discussion mail list style with private archives so it is not displayed when you are logged out at /hyperkitty. Many thanks Daniel

1 0

Re: MM3.3 ignores
by Axel Rau 08 Nov '22

08 Nov '22

Am 08.11.2022 um 09:14 schrieb Axel Rau <Axel.Rau(a)chaos1.de>: > Am 08.11.2022 um 08:11 schrieb Mark Sapiro <mark(a)msapiro.net <mailto:mark@msapiro.net>>: > > > What is /var/templates now? I.e., is it a symlink to /usr/local/mailman3/var/templates? what does `ls -l /var/templates` (no slash at the end) show? > It does not exist. No directory, no link. Maybe I remember it wrong. Axel PS: Can I send posts with attachments to this list? My last posting didn’t make it. --- PGP-Key: CDE74120 ☀ computing @ chaos claudius --- PGP-Key: CDE74120 ☀ computing @ chaos claudius

2 1

MM3.3 ignores
by Axel Rau 08 Nov '22

08 Nov '22

Hi all, mm 3.3.5 started to complain: - - - File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailman/config/config.py", line 142, in load self.push(filename, user_config.read()) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailman/config/config.py", line 148, in push self._post_process() File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailman/config/config.py", line 160, in _post_process self.ensure_directories_exist() File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailman/config/config.py", line 253, in ensure_directories_exist makedirs(directory) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailman/utilities/filesystem.py", line 69, in makedirs os.makedirs(path, mode) File "/usr/local/py_venv/mailman_33/lib/python3.9/os.py", line 225, in makedirs mkdir(name, mode) PermissionError: [Errno 13] Permission denied: '//var/templates‘ - - - part from mailman.cfg: - - - [paths.dev] var_dir: $cfg_file/../.. [paths.here] var_dir: $cwd/var [paths.fhs] bin_dir: /usr/local/bin var_dir: /var/lib/mailman queue_dir: /var/spool/mailman log_dir: /var/log/mailman lock_dir: /var/spool/lock/mailman etc_dir: /usr/local/etc ext_dir: /usr/local/etc/mailman.d pid_file: /var/run/mailman/master.pid [paths.home] var_dir: /usr/local/mailman3 - - - var subdirectory: - - - (mailman_33) [root@lists5 /usr/local/py_venv/mailman_33]# ls -l /usr/local/mailman3/var/ total 62 drwxr-xr-x 3 mailman mailman 3 18 Jan. 2022 archives drwxr-xr-x 2 mailman mailman 2 18 Jan. 2022 cache drwxr-xr-x 2 mailman mailman 2 18 Jan. 2022 data drwxrwx--- 2 mailman mailman 4 2 Feb. 2022 etc drwxr-xr-x 6 mailman mailman 6 19 Jan. 2022 lists drwxr-xr-x 2 mailman mailman 2 5 Nov. 17:48 locks drwxr-xr-x 2 mailman mailman 7 18 Jan. 2022 logs drwxr-xr-x 155 mailman mailman 155 24 Okt. 09:09 messages drwxr-xr-x 3 root mailman 3 14 Juni 17:57 old_templates drwxr-xr-x 14 mailman mailman 14 18 Jan. 2022 queue drwxr-xr-x 3 mailman mailman 3 18 Jan. 2022 templates # ls -ld /usr/local/mailman3 drwxr-xr-x 11 mailman mailman 24 24 März 2022 /usr/local/mailman3 - - - I’m confused with the layout (and I dont like var stuff not in var). I have no layout set. Why does it not see /usr/local/mailman3/var/templates ? Any help apprecaiated Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius

5 5

Imported archives MM2 to MM3
by Mark Dale 04 Nov '22

04 Nov '22

Hi I've just migrated a list from MM 2.1.39 to MM 3.3 (Debian). Following the guide at: https://docs.mailman3.org/en/latest/migration.html Importing the config went fine and all is well with that. The import of the archive appeared to go well (notes below) as did the rebuilding of the index. However, the archives show up empty on the list's webpage. I don't know what I should be looking for to fix this, so any pointers would be great. Thanks. //////////////////////////////////////// Migrate the list archives ========================= # python3 /usr/share/mailman3-web/manage.py hyperkitty_import -l LISTNAME@DOMAIN ./LISTNAME.mbox Importing from mbox file ./LISTNAME.mbox to LISTNAME@DOMAIN Computing thread structure Synchronizing properties with Mailman 33 emails left to refresh, checked 0 Warming up cache The full-text search index is not updated for this list. It will not be updated by the 'minutely' incremental update job. To update the index for this list, run the Django admin command with arguments 'update_index_one_list leden(a)vereniging.tropischebossen.nl'. //////////////////////////////////////// Rebuild the index: ======================== # python3 /usr/share/mailman3-web/manage.py update_index_one_list LISTNAME@DOMAIN Indexing 646 emails

1 1

Re: No DBA password when installing Mailman3 with remote database server
by Markus Ludwig Grandpré 04 Nov '22

04 Nov '22

Dear Mr. Turnbull, dear blackout69, thank you very much for your answers. Below this text you will find a brief documentation how I finally managed to install mailman3 and mailman3web packages under Debian 11 with a remote PostGreSQL server v10.22. Maybe there is a more elegant way to install both packages correctly, but AFAIK any solution will be only a workaround for the main problem, that the DBA's password is usually unknown during the whole installation process if you use a remote database server that is run by another staff team. Best regards, Markus ------------ 8< ------------ Mailman3 installation ===================== 1. Installation mailman3 2. Installation mailman3web 3. Integration in boot sequence 1. Installation mailman3 ------------------------ Once the remote database server has been set up with databases mailman3 and mailman3web and with a database user mailman3 that has access to both databases, create database mailman3; create database mailman3web; create user mailman3 with encrypted password 'streng_geheim'; grant all privileges on database mailman3 to mailman3; grant all privileges on database mailman3web to mailman3; the package mailman3 can be installed: # apt install mailman3 To avoid the DBA password prompt that ususally cannot be answered if the database server is run by another team, the installation tool dbconfig-common should be omitted: * Configure database for mailman3 with dbconfig-common? No The mailman3 package will be installed without errors. The configuration of the database connection can be done in file /etc/mailman3/mailman.cfg: ... class: mailman.database.postgresql.PostgreSQLDatabase ... url: postgres://mailman3:<secret>@<host>:<port>/mailman3 At this point the required tables have not yet been created in the database. Therefore, the mailman3 package should be configured again: # dpkg-reconfigure mailman3 Because the database mailman3 already exists on the database server, it does not need to be recreated using dbconfig-common: * Reinstall database for mailman3? No * Add the HyperKitty configuration to mailman.cfg? No Also moving the HyperKitty configuration to /etc/mailman3/mailman.cfg is not necessary at this time. After dpkg-reconfigure has finished, all necessary tables do now exist in the database mailman3: mailman3=> \dt List of relations Schema | Name | Type | Owner --------+--------------------+-------+---------- public | _request | table | mailman3 public | acceptablealias | table | mailman3 public | address | table | mailman3 public | alembic_version | table | mailman3 ... An initial start of the service mailman3 shows no errors: # systemctl start mailman3 # systemctl status mailman3 ● mailman3.service - mailman3 server. Loaded: loaded (/lib/system/system/mailman3.service; enabled; vendor default: enabled) Active: active (running) since Thu 2022-11-03 10:10:29 CET; 11min ago. ... 2. Installing mailman3-web -------------------------- Once the mailman3 package is installed, package mailman3-web can be installed: # apt install mailman3-web This time you should not do the installation process without the help of the installation tool dbconfig-common: * Configure database for mailman3 with dbconfig-common? Yes * Database type to be used by mailman3-web: pgsql * Host name of the PostgreSQL database server for mailman3-web: new host * Host running the PostgreSQL server for mailman3-web: <remote host> * PostgreSQL application password for mailman3-web: <secret> * Password confirmation: <secret> Even if the DBA password prompt cannot be answered: Create configuration file /etc/dbconfig-common/mailman3-web.conf with new version Password for user postgres: ?????? the dbconfig-common tool should be used again: * Next step for database installation: retry * Configure database for mailman3-web with dbconfig-common? Yes * Connection method for PostgreSQL database of mailman3-web: TCP/IP * Host name of the PostgreSQL database server for mailman3-web: <remote host> * Port number for the PostgreSQL service: 5432 * Method for authenticating the PostgreSQL administrator: password * Method for authenticating PostgreSQL user: password * PostgreSQL database name for mailman3-web: mailman3web * PostgreSQL username for mailman3-web: mailman3 * PostgreSQL application password for mailman3-web: <secret> * Password confirmation: <secret> * Name of the database's administrative user: postgres * Password of your database's administrative user: sldjkfhskldfjhyxlökcjy The prompt for the DBA password cannot be answered correctly again, therefore "ignore" should now be the best choice for the further course of the installation process: * Next step for database installation: ignore * Password of your database's administrative user: sldjkfhskldfjhyxlkcylö An error does occur now because the database user mailman3 can not be created: ... Password for user postgres: unable to connect to postgresql server. error encountered creating user: psql: error: fe_sendauth: no password supplied ... But this error doesn't matter, because the database user mailman3 does already exist and the installation process of the package mailman3web will nevertheless be finished completely. A look into file /etc/mailman3/mailman-web.py shows that dbconfig-common has entered the database connection to the database server correctly, too: DATABASES = { 'default': { 'ENGINE': 'django.db.backends.postgresql_psycopg2', 'NAME': 'mailman3web', 'USER': 'mailman3', 'PASSWORD': '<secret>', 'HOST': '<remote host>', 'PORT': '', <--- missing? 'OPTIONS': { }, } } Also all required tables have been created in the database mailman3web during the installation process: mailman3web=> \dt List of relations Schema | Name | Type | Owner --------+-----------------------------------+-------+---------- public | account_emailaddress | table | mailman3 public | account_emailconfirmation | table | mailman3 public | auth_group | table | mailman3 public | auth_group_permissions | table | mailman3 public | auth_permission | table | mailman3 ... The initial start of the service mailman3-web shows no errors: # systemctl start mailman3-web # systemctl status mailman3-web ● mailman3-web.service - Mailman3-web uWSGI service. Loaded: loaded (/lib/system/system/mailman3-web.service; enabled; vendor default: enabled). Active: active (running) since Thu 2022-11-03 10:42:30 CET; 11min ago ... 3. Intergration in boot sequence -------------------------------- Finally, the two services mailman3 and mailman3-web can be included in the boot sequence: # systemctl enable mailman3 Synchronize the state of mailman3.service with the SysV service script with /lib/systemd/systemd-sysv-install. Runs: /lib/systemd/systemd-sysv-install enable mailman3 # systemctl enable mailman3-web Synchronize the status of mailman3-web.service with the SysV service script using /lib/systemd/systemd-sysv-install. Runs: /lib/systemd/systemd-sysv-install enable mailman3-web ------------ >8 ------------ On 01.11.22 08:10, Stephen J. Turnbull wrote: > blackout69 writes: > > > For mailman3 > > sudo dpkg-reconfigure mailman3 > > > > For mailman3-web > > sudo dpkg-reconfigure mailman3-web > > I guess those will work too as long as the users and databases have > been created. But they'll still fail at the first step without that > (and they might fail anyway if checking for the existence of those > users and databases involves logging in to the database as the admin > user). > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, Tel: ++49 7531 88 4342

3 2

Moderate first postings of new members
by c.buhtz＠posteo.jp 03 Nov '22

03 Nov '22

Hi, I'm looking for a feature but not sure if I missed it or if it isn't really there. By default, I accept all messages of list members without moderating them. What I want is that I would like to moderate the messages of new subscribed members until I set them to auto-accept all messages. I want to see what a new member is posting before it is send/accepted to the list. Is this possible? Kind Christian

3 3

Mailman upgrade results in page not found error
by Andrew Hodgson 03 Nov '22

03 Nov '22

Hi. Just doing the Mailman suite upgrade on my small installation I use for test purposes. Steps include: Run backup script Stop services Mv venv venv-old python3 -m venv --system-site-packages --symlinks venv source venv/bin/activate pip install -U pip pip install mailman mailman-hyperkitty hyperkitty postorius whoosh deactivate ./bin/Django-admin collectstatic ./bin/Django-admin migrate At this step I got an error regarding the import of URLs, a quick Google suggested this was because the new venv has upgraded to Django 4.0. I downloaded the urls.py from the mailman-web Git repo (I should migrate to this at some point I know) and replaced my version with this one. This allowed the migrate to run correctly. Once services were up everything worked as expected except for the web page. If you go to https://lists.hodgsonfamily.org you get a Postorius page not found error, however if you click on the Mailman logo you get to the correct place. I think this is a problem with the new urls.py I downloaded, what is the best way to restore the old behaviour of having https://lists.hodgsonfamily.org going to the correct place? Urls.py: # -*- coding: utf-8 -*- # Copyright (C) 1998-2016 by the Free Software Foundation, Inc. # # This file is part of Postorius. # # Postorius is free software: you can redistribute it and/or modify it under # the terms of the GNU General Public License as published by the Free # Software Foundation, either version 3 of the License, or (at your option) # any later version. # # Postorius is distributed in the hope that it will be useful, but WITHOUT # ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or # FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for # more details. # # You should have received a copy of the GNU General Public License along with # Postorius. If not, see http://www.gnu.org/licenses/. from django.conf.urls import include from django.contrib import admin from django.urls import path, reverse_lazy from django.views.generic import RedirectView urlpatterns = [ path( '', RedirectView.as_view(url=reverse_lazy('list_index'), permanent=True), ), path('mailman3/', include('postorius.urls')), path('archives/', include('hyperkitty.urls')), path('', include('django_mailman3.urls')), path('accounts/', include('allauth.urls')), path('admin/', admin.site.urls), ] Thanks. Andrew.

3 3

How to add new lists?
by fstltna＠yahoo.com 03 Nov '22

03 Nov '22

I have been able to get the web interface up and the default "mailman@" address is there and appears in the list of lists, but when I add a list from the command line with a command like "mailman create foo(a)ourlists.gameplayer.club" it does not return a error and using "mailman lists" lists it as existing. However there is no new entries in the /etc/aliases file and the new list doesn't appear in the web interface... Any ideas?

2 1

Adding list via web form
by fstltna＠yahoo.com 03 Nov '22

03 Nov '22

Trying to add a list using the web form but I get this: "Error: You are not authorized to create new mailing lists". Do I need to log in somewhere? I thought I was logged in as admin but maybe not?

2 1

Start a new thread and Reply buttons don't work on web interface
by mcashdollar＠anl.gov 01 Nov '22

01 Nov '22

Hi, I'm planning on upgrading some of our mailing lists from Mailman 2 to Mailman 3. I setup a test server to try Mailman 3. I notice that when I go to "Archives" in the web interface and choose "Start a new thread" or "Reply" to post a message on my test list, it says successful, but the message never shows up. Looking at the logs, I don't see any errors. I can see the HTTP POST in the log and it seems like everything works: [pid: 70249|app: 0|req: 41/93] 127.0.0.1 () {46 vars in 1223 bytes} [Tue Nov 1 21:03:25 2022] POST /archives/list/discuss(a)lists.chicagohpc.org/message/ATXUU5VT NBT6TIF72T7WNNHDIJNOROIF/reply => generated 949 bytes in 104 msecs (HTTP/1.0 200) 8 headers in 258 bytes (1 switches on core 1) I'm using nginx as the http server. location / { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /static/ { alias /opt/mailman/web/static/; autoindex off; } Does anyone have an idea of why posting messages from the web interface never shows up? I turned on all the debug logs but can't find an error. Thanks

2 1

No DBA password when installing Mailman3 with remote database server
by Markus Ludwig Grandpré 01 Nov '22

01 Nov '22

Dear Mailman3 list, I try to install the Mailman3 software 3.3.3-1 on a Debian 11 system with a remote Postgres database server. During the installation process dpkg is asking for the DBA password that our DBA team would not provide to me. So what can I do? Best regards, Markus -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, Tel: ++49 7531 88 4342

4 5

about the last upgrade, one more thing about urls.py
by Guillermo Hernandez (Oldno7) 31 Oct '22

31 Oct '22

I forgot to mention that I found one error in the last upgrade procedure in the migrate part. It is about the urls.py file. It's about the import from django.conf.urls the "url", that now is inexistent. After searching around, I've edited urls.py like below. That saved me from modifying more things in that file. ### from django.conf import settings ### mod. 30/10/22 ###from django.conf.urls import include, url from django.conf.urls import include from django.urls import re_path as url ##### -- ___________________________________________ 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.

1 0

after last upgrade I've got a CSRF failed verification
by Guillermo Hernandez (Oldno7) 31 Oct '22

31 Oct '22

I did upgrade one of my mailman3 server after Abhilasj announcement: "I am pleased to announce several new releases for GNU Mailman project. 1. Mailman Core 3.3.6 1 <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.…> 2. Postorius 1.3.7 2 <https://docs.mailman3.org/projects/postorius/en/latest/news.html#section-2> 3. Hyperkitty 1.3.6 [3] 4. Mailmanclient 3.3.4 [4] 5. Django-mailman3 1.3.8 [5]" I did it via pip and all seems to be working, but when I try to discard or accept any message via postorius it shows a Forbidden 403 error CSRF verification failed. In my settings.py I have commented out these variables: # Other security settings # SECURE_SSL_REDIRECT = True # If you set SECURE_SSL_REDIRECT to True, make sure the SECURE_REDIRECT_EXEMPT # contains at least this line: # SECURE_REDIRECT_EXEMPT = [ # "archives/api/mailman/.*", # Request from Mailman. # ] # SESSION_COOKIE_SECURE = True # SECURE_CONTENT_TYPE_NOSNIFF = True # SECURE_BROWSER_XSS_FILTER = True # CSRF_COOKIE_SECURE = True # CSRF_COOKIE_HTTPONLY = True # X_FRAME_OPTIONS = 'DENY' I've been messing with them whith no results. It's like it lacked some value in some template... Can someone, please, point me in the right direction? Thanks in advance -- ___________________________________________ 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 7

Re: Problems after Upgrade
by Mark Sapiro 31 Oct '22

31 Oct '22

On 10/30/22 17:37, Jeff Steele wrote: > Thanks Mark, > > I was able to fix this problem easily by modifying: > > mailman3/lib/python3.8/site-packages/compressor/management/commands/compress.py > > to change the line: > > Command.requires_system_checks = None > > to > > Command.requires_system_checks = [] > > Now, bin/mailman-web compress runs but outputs: > > CommandError: Compressor is disabled. Set the COMPRESS_ENABLED setting or use --force to override. > > which I guess is fine. If you want to do off line compression which is a good thing, you need to set ``` COMPRESS_ENABLED = True ``` in your Django settings. I recently added this and also a note about CSRF_TRUSTED_ORIGINS to https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Problems after Upgrade
by Jeff 31 Oct '22

31 Oct '22

Hello, I tried to upgrade to the latest mailman3 version using the following command: pip install -U mailman postorius django-mailman3 hyperkitty mailman-web mailmanclient There didn’t appear to be any problems with this step and I’ve since run it again a few times and only see that the requirements have been satisfied. When first running the command: mailman-web migrate I received several errors dealing with search_text in the package compressor (at least that’s as best as I remember, I wasn’t taking notes). I fixed these manually by changing it to search_str. Eventually "mailman-web migrate” started working and has subsequently worked. When I run the command: mailman-web compress I get the following error: traceback (most recent call last): File "bin/mailman-web", line 8, in <module> sys.exit(main()) File "/usr/local/mailman3/lib64/python3.8/site-packages/mailman_web/manage.py", line 37, in main execute_from_command_line(sys.argv) File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line utility.execute() File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management/__init__.py", line 440, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management/__init__.py", line 279, in fetch_command klass = load_command_class(app_name, subcommand) File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management/__init__.py", line 49, in load_command_class return module.Command() File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management/base.py", line 274, in __init__ raise TypeError("requires_system_checks must be a list or tuple.") TypeError: requires_system_checks must be a list or tuple. I have not been able to fix this and would appreciate any assistance. When I run the command: bin/mailman-web collectstatic It asks me yes or no continue and when I enter “yes” it displays the following which I assume means it worked: 372 static files copied to '/usr/local/mailman3/web/static', 38 unmodified Starting mailman3 seems to work by the status message shows the following: systemctl status -l mailman3 ... Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: return function(args[0], config.db.store, *args[1:], **kws) Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: File "/usr/local/mailman3/lib64/python3.8/site-packages/mailman/model/bounce.py", line 259, in send_warnings_and_remove Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: self._send_warnings() Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: File "/usr/local/mailman3/lib64/python3.8/site-packages/mailman/database/transaction.py", line 85, in wrapper Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: return function(args[0], config.db.store, *args[1:], **kws) Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: File "/usr/local/mailman3/lib64/python3.8/site-packages/mailman/model/bounce.py", line 310, in _send_warnings Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: member.address, Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: File "/usr/local/mailman3/lib64/python3.8/site-packages/mailman/model/member.py", line 121, in address Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: return (self._user.preferred_address Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: AttributeError: 'NoneType' object has no attribute 'preferred_address' lines 13-35/35 (END) I have been receiving admin requests to approve messages. But, I can’t approve them because of the following issue: Starting mailman-web seems to work as expected with no errors. However, when I try to login to the web interface, I get a HTML page with the following error: init__() got an unexpected keyword argument 'providing_args' Request Method: GET Request URL: http://lists.crestwood-dc.org/accounts/login/?next=/mailman3/lists/crestwoo… Django Version: 4.1.2 Exception Type: TypeError Exception Value: __init__() got an unexpected keyword argument 'providing_args' Exception Location: /usr/local/mailman3/lib64/python3.8/site-packages/compressor/signals.py, line 4, in <module> Raised during: allauth.account.views.LoginView Python Executable: /usr/local/mailman3/bin/uwsgi Python Version: 3.8.13 As a result, I cannot login and approve posts. I would greatly appreciate any assistance with these issue. Thanks much!

2 2

Mailman3-core rest failure
by Jacob Sievert 30 Oct '22

30 Oct '22

Hello, since our last update from python 3.6 to python 3.9 our mailman server returns the following errors if we try to access the list via postorius. [29/Oct/2022:13:25:25 +0200] "GET /3.1/lists/XXX.XXX.XX/archivers HTTP/1.1" 500 38 "-" "GNU Mailman REST client v3.3.4" I tried to set the logging to a more verbose state but couldn't get a better message yet. If somebody knows what went wrong, that would be great. regards Jacob

2 3

Adding users
by horvath.arpad.szfvar＠gmail.com 30 Oct '22

30 Oct '22

Hi, I've tried to add new members to the mailing list, but I failed even if I tried 3 ways: - manage.py shell - invitation letter - sending a letter to subscribe. I try to solve it with the Python shell now. Based on this site: https://docs.mailman3.org/projects/mailman/en/latest/build/lib/mailman/mode… I tried this one from Debian bash command line, but there is an error message, as you can see at the end. # pwd /usr/share/mailman3-web # ./manage.py shell In [1]: from mailman.interfaces.usermanager import IUserManager In [2]: from zope.component import getUtility In [3]: user_manager = getUtility(IUserManager) --------------------------------------------------------------------------- ComponentLookupError Traceback (most recent call last) <ipython-input-3-9500ce4250f0> in <module> ----> 1 user_manager = getUtility(IUserManager) /usr/lib/python3/dist-packages/zope/component/_api.py in getUtility(interface, name, context) 167 if utility is not None: 168 return utility --> 169 raise ComponentLookupError(interface, name) 170 171 def queryUtility(interface, name='', default=None, context=None): ComponentLookupError: (<InterfaceClass mailman.interfaces.usermanager.IUserManager>, '') What do I wrong. Should I stop all my mailman processes first? Thanks, Arpad

2 4

restriction on attrs?
by Stephen J. Turnbull 27 Oct '22

27 Oct '22

Hi, I'm working with a frozen requirements.txt for a full Mailman 3 install (BigCorp QA stuff), and trying to decide whether it's worth fighting BigCorp QA to update it to the recent releases. The previous test install pulled in attrs 22.1.0, but now mailman-3.3.6 restricts attrs<21.3. I can't find any documentation for this change, which Mark made in a change d0595dec76 that's documented to be about lmtp and smtp. What's going on with this change? Steve

3 3

New Mailman Releases
by Abhilash Raj 27 Oct '22

27 Oct '22

Hi, I am pleased to announce several new releases for GNU Mailman project. 1. Mailman Core 3.3.6 [1] 2. Postorius 1.3.7 [2] 3. Hyperkitty 1.3.6 [3] 4. Mailmanclient 3.3.4 [4] 5. Django-mailman3 1.3.8 [5] All the releases are published to PyPI and you can find links to all the PyPI projects: https://docs.mailman3.org/en/latest/ A full list of changelogs are available below: [1]: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… [2]: https://docs.mailman3.org/projects/postorius/en/latest/news.html#section-2 -- Something weird is going on with the page missing the bullets. [3]: https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-6 [4]: https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… [5]: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst Finally, the minimum Python version required is 3.7 although, 3.9 is recommended if you are doing a new install for longest support. 3.10 is supported for Django apps, but Mailman Core is missing that due to one of the core dependencies not support 3.10 yet (aiosmtpd). Thanks to all the contributors for making this release possible and apologies on my end for delayed releases. If you find any issues, you can report them at the respective bug tracker for the projects. The links to issue trackers are available here: https://docs.mailman3.org/en/latest/ -- thanks, Abhilash Raj (maxking)

2 4

Sanity check of upgrade procedure
by David Newman 27 Oct '22

27 Oct '22

The other day Abhilash posted here that updated releases are available. I rarely upgrade my Mailman3 server running in a venv on Debian 11. But when I have there was previously an issue with mistune, requiring commands like this (run as mailman in a venv): pip install -U mailman postorius django-mailman3 hyperkitty mailman-web uwsgi pip install wheel mailman pymysql mysqlclient pip install mistune==2.0.0rc1 mailman-web migrate mailman-web compress mailman-web collectstatic mailman-web compilemessages For these new releases, is that mistune step still needed? Thanks! dn

2 4