- Mailman-users - lists.mailman3.org

Must every Moderator/Admin be member of a list to be able to use Postorius?
by mm3-omf＠sh.werbittewas.de Jan. 31, 2023

Jan. 31, 2023

we're using debian/devuan with distribution-mailman3 and tried to add admin/mod for a list, but if logging in as this user, there's no item to manage the list at all. do we have to add this user as member of this list? (that wouldn't be nice, because the user doesn't want to get normal Mails from List, but only admin-Mails) regards omf

2 1

Language switch
by Massimiliano Paragnani Jan. 30, 2023

Jan. 30, 2023

Hi, I can't set other languages in MM3 web. I did it https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/model/docs… I tried to add language cose in settings_local.py and in mailman.cfg but nothing happens How can I do?

2 1

New Installation of MM3 is not archiving
by Onyeibo Oku Jan. 30, 2023

Jan. 30, 2023

Greetings, I finally completed installation of Mailman 3 following the instructions here: https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu… I got a lot of support from this mailing-list too and I am mighty grateful for that. My new MM3 instance does not seem to be archiving. List subscribers are currently sending and receiving mails on their subscribed lists. However, none of the correspondence is showing up at https://mailing-list-site.tld/archives/. That page shows a listing of the active mailing-lists with '0 participants' and '0 discussions'. Whereas, those lists contain mails. How do I troubleshoot this?

2 1

About to Install MM3 -- Seeking clarification
by Onyeibo Oku Jan. 30, 2023

Jan. 30, 2023

Good Morning Everyone, I installed and managed mailman 2 for about two years. I am now ready to try Mailman 3. The documentation for version 2 was lucid and this forum was quite helpful in the past. Now I'd like to proceed with installating MM3 but I doubt my understanding of the docs. It seems to assume that users will know what to do. Okay, don't laugh! I just want to be sure what I am doing. Does the following sequence resemble the proper steps? 1. Download the source from a git repo (I understood that one) 2. Create a virtual environment (venv perhaps ... not stated explicitly) 3. activate the virtual environment 4. from the git project root, run: ./mailman start I know, its stupid. I had to ask. It would really build my confidence someone would confirm the above steps or counter then with something very explicit. What about process ownership? Do I need to have a unix mailman user? What else do I need to get mailman up and running before proceeding to configuration. Ahaa! I perused the config docs a bit. Where can I find the .cfg file? I hope these questions are not too annoying. Regards Onyeibo

6 46

long time user of mailman 2, new to docker-mailman and docker
by pjbondi＠systemdatabase.com Jan. 29, 2023

Jan. 29, 2023

Hello to all: I'm getting this stack trace with the following redacted settings. # ALLOWED_HOSTS * # DEBUG True # HYPERKITTY_API_KEY llllllllllllllllllllllllllllllllllllllllllllllllll # MAILMAN_ADMIN_EMAIL xxxxxxx(a)yyyyyyyyyyyyyy.com # MAILMAN_HOSTNAME mailman-web # MM_HOSTNAME yyyyyyyyyyyyyy.ca # MTA postfix # SECRET_KEY kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk # SERVE_FROM_DOMAIN yyyyyyyyyyyyyy.ca # SMTP_HOST smtp-relay.sendinblue.com # SMTP_HOST_PASSWORD pppppppppppppppp # SMTP_HOST_USER xxxxxxx(a)yyyyyyyyyyyyyy.com # SMTP_PORT 587 # SMTP_USE_TLS True # [very long startup snipped] Applying postorius.0001_initial... OK Applying postorius.0002_auto_20160210_0721... OK Applying postorius.0003_drop_addressconfirmationprofile... OK Applying postorius.0004_create_email_template... OK Applying postorius.0005_auto_20180707_1107... OK Applying postorius.0006_auto_20180711_1359... OK Applying postorius.0007_auto_20180712_0536... OK Applying postorius.0008_auto_20190310_0717... OK Applying postorius.0009_auto_20190508_1604... OK Applying postorius.0010_auto_20190821_0621... OK Applying postorius.0011_auto_20191109_1219... OK Applying postorius.0012_auto_20200420_2136... OK Applying postorius.0013_auto_20201116_0058... OK Applying sessions.0001_initial... OK Applying sites.0002_alter_domain_unique... OK Setting systemdatabase.ca as the default domain ... Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3.8/site-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) sqlite3.OperationalError: no such table: django_site The above exception was the direct cause of the following exception: Traceback (most recent call last): File "manage.py", line 10, in <module> execute_from_command_line(sys.argv) File "/usr/lib/python3.8/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line utility.execute() File "/usr/lib/python3.8/site-packages/django/core/management/__init__.py", line 375, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/lib/python3.8/site-packages/django/core/management/base.py", line 323, in run_from_argv self.execute(*args, **cmd_options) File "/usr/lib/python3.8/site-packages/django/core/management/base.py", line 364, in execute output = self.handle(*args, **options) File "/usr/lib/python3.8/site-packages/django/core/management/commands/shell.py", line 86, in handle exec(options['command']) File "<string>", line 1, in <module> File "/usr/lib/python3.8/site-packages/django/db/models/query.py", line 741, in update rows = query.get_compiler(self.db).execute_sql(CURSOR) File "/usr/lib/python3.8/site-packages/django/db/models/sql/compiler.py", line 1471, in execute_sql cursor = super().execute_sql(result_type) File "/usr/lib/python3.8/site-packages/django/db/models/sql/compiler.py", line 1142, in execute_sql cursor.execute(sql, params) File "/usr/lib/python3.8/site-packages/django/db/backends/utils.py", line 67, in execute return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/usr/lib/python3.8/site-packages/django/db/backends/utils.py", line 76, in _execute_with_wrappers return executor(sql, params, many, context) File "/usr/lib/python3.8/site-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3.8/site-packages/django/db/utils.py", line 89, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/usr/lib/python3.8/site-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3.8/site-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) django.db.utils.OperationalError: no such table: django_site

1 0

Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/search
by Dave Hall Jan. 29, 2023

Jan. 29, 2023

Hello, Please pardon a slightly off-topic comment, but I would like to highlight a part of Odhiambo's post. Heavily nested inline replies also reflect the issue I wish to comment on, so I'm not going to. Granted, I am a slow learner, and perhaps already so mixed up after reading > the myriad HOWTOs for > installing MM3 that are available online. I am tempted to say there are > many like me who are likely to > miss "where to obtain" other settings from. and > Is it possible to modify the documentation to somehow make it obvious (in a > language that a layman can easily understand, I have seen this with several open source projects lately. There's no big picture, just 'hundreds' of cross-linked little bits of disjointed information that almost seem like documentation for individual modules. I once joined a large commercial project for a major US computer company (sorry, I won't share details). They were quite proud of their extensive documentation. The docs for their equivalent of the kernel syscall interface, when printed (two-sided) and stacked, would easily approach 2 meters tall. Yet, every bit of it was incomprehensible unless and until you called the developer and had them explain it to you. The problem that we all have, us humans, is that when we are very familiar with something, like the code we've been working on, it is very hard to describe its purpose to somebody who knows nothing about it. ("It's obvious to me, so it should be obvious to you."). So, a challenge for us all: When writing and reviewing your documentation, imagine that you're explaining your whole project face-to-face to your grandmother, or to anybody who never learned to program. From experience I promise that it's easy once you get the hang of it. Thank you and sorry for the speech. -Dave -- Dave Hall Binghamton University On Sat, Jan 28, 2023 at 2:54 AM Odhiambo Washington <odhiambo(a)gmail.com> wrote: > On Fri, Jan 27, 2023 at 9:34 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > On 1/27/23 05:53, Odhiambo Washington wrote: > > > On Mon, Jan 23, 2023 at 11:48 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > >> > > >> Note that when following > > >> https://docs.mailman3.org/en/latest/install/virtualenv.html you > create > > >> /etc/mailman3/settings.py and it contains > > >> ``` > > >> from mailman_web.settings.base import * > > >> from mailman_web.settings.mailman import * > > >> ``` > > >> to establish a base set of settings that can be augmented or > overridden > > >> in /etc/mailman3/settings.py. mailman_web.settings.mailman in turn > > contains > > >> ``` > > >> HAYSTACK_CONNECTIONS = { > > >> 'default': { > > >> 'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', > > >> 'PATH': "fulltext_index", > > >> ``` > > >> which is a relative path for fulltext_index and may need to be set to > an > > >> absolute path. > > >> > > > > > > Mi Mark, > > > > > > I have read this page - > > > https://docs.mailman3.org/en/latest/install/virtualenv.html and > further > > - > > > > > > https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-config > > > - without clicking any external links. > > > I still don't see the HAYSTACK_CONNECTIONS in the settings.py included > > on > > > that page. > > > I am missing something obvious, no? > > > > > > Please reread what I wrote above. HAYSTACK_CONNECTIONS is not in the > > suggested settings.py but it is in mailman_web.settings.mailman and is > > imported by the suggested settings.py. > > > I have reread what you wrote now and I'm beginning to get the hang of this > method. > My observation is that it can only be _obvious_ to someone very familiar > with Python config > to decipher that *additional* settings *that can be augmented or > overridden > in /etc/mailman3/settings.py* can be obtained from: > /PATH-TO/mailman_web/settings/{base|mailman}.py after they have noticed > these two lines in > the sample settings given in /etc/mailman3/settings.py: > > from mailman_web.settings.base import *from > mailman_web.settings.mailman import * > > [At first instance, it is not obvious that mailman_web.settings.base and > mailman_web.settings.mailman are > actually paths in Python - which magically translates to > mailman_web/settings/base.py and mailman_web/settings/mailman.py] > Granted, I am a slow learner, and perhaps already so mixed up after reading > the myriad HOWTOs for > installing MM3 that are available online. I am tempted to say there are > many like me who are likely to > miss "where to obtain" other settings from. > For example, my mind all along has been tuned to having a settings_local.py > for overriding the settings.py. > However, with this particular documentation, it would appear that > everything is intended to just go into /etc/mailman3/settings.py. > > Is it possible to modify the documentation to somehow make it obvious (in a > language that a layman can easily understand, > that those two "import *" _DO establish a base set of settings that can be > augmented or overridden in /etc/mailman3/settings.py_ > and that those settings are in what file(s) ? > > I am not saying @Johannes Rohr <johannes(a)rohr.org> is a layman like me, > but > I think that is what hit him. > > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) > _______________________________________________ > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to kdhall(a)binghamton.edu >

2 1

EMWD/Affinity/Empathy in 2023
by jaboyib556＠v3dev.com Jan. 29, 2023

Jan. 29, 2023

Hi all, We're exploring Mailman 3 and the custom interfaces provided by EMWD's Affinity and Empathy look very interesting: https://www.mailmanhost.com/affinity-mailman/ However, I saw reports of EMWD being a one-man show and the owner sadly passing away in 2021; but I've also seen threads here referring to the Affinity and Empathy projects in 2022. It wasn't clear to me if EMWD is still an active business and Affinity and Empathy are still active offerings. Does anyone here have any direct contact/relationship/experience with EMWD/Affinity/Empathy following the owner's passing? Or knowledge of any other offerings publicly available today that are similar to Affinity/Empathy? Thanks!

3 3

Can't see held messages
by Massimiliano Paragnani Jan. 27, 2023

Jan. 27, 2023

Hi everybody, I've a new installation in my own vps. Everything works if I set "Deliver immediately" but if I turn on the "hold for moderation" I can't see the mails in web interface and I can't confirm the delivery or discard. What information do you need to help me?

1 1

MM attaches mime-attachments to mail as text file since update to 3.3.8
by Stefan Bauer Jan. 25, 2023

Jan. 25, 2023

Dear Users & Developers, we're running MM3 on Ubuntu 22 and used the venv-installation method. Last week we updated via¹ to Mailman Core-Version GNU Mailman 3.3.8 (Tom Sawyer) Mailman Core API-Version 3.1 Mailman Core Python-Version 3.10.6 (main, Nov 14 2022, 16:10:14) [GCC 11.3.0] and now mailman attaches mime-attachments to email as text-files. That breaks many mails in our environment. For example: Now we have attachments like smime.p7s + ATT000001.txt as well as what looks like MM footers "mailing list --- test@domain ... To unsubscripbe send an email to ..." How can we get the "old" processing back? Thank you alot. Stefan

3 5

Localisation of web interface gone after OS upgrade
by Johannes Rohr Jan. 20, 2023

Jan. 20, 2023

Dear all, I just upgraded our server from Ubuntu 20.04 to 22.04. Mailman is installed in virtualenv, so it shouldn't be affected by the upgrade. Am I right about that? However, the strange thing is that most, albeit not all of the localisation is gone, the web interface is now mostly in English. Still, I reinstalled venv, mailman and hyperkitty, but no change. I also re-ran the four commands * mailman-web migrate * mailman-web collectstatic * mailman-web compress * mailman-web compilemessages just to be sure, but that didn't change things either. Is there something in Ubuntu 22.04 that kills the localisation? Thanks! Johannes

1 1

Updated script for checking and fixing mbox files.
by Mark Sapiro Jan. 20, 2023

Jan. 20, 2023

Mailman 2.1 has a cleanarch script for checking mbox files for unescaped `From `lines in message bodies and optionally fixing them. For some time, there has been a stand-alone python3 version of this script at https://www.msapiro.net/scripts/cleanarch3 (mirrored at https://fog.ccsf.edu/~msapiro/scripts/cleanarch3) I have just updated this script to check and optionally fix bad Date: headers. I have also added it at https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/contrib/clea… for the next release. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 3

Using it with the "smtp2go" email relay service that has special deliverability rules
by golden_rock＠hotmail.com Jan. 19, 2023

Jan. 19, 2023

Hi, Smtp2Go relay service enforces a few rules for deliverability: The From: address domain has to be verified in smtp2go The sender envelope address also has to be verified in smtp2go So emails sent by mailman don't get relayed because mailman sets From: to be the original sender of the message, and it means anyone that wants to send to the list would have to approve themselves with smtp2go first, which is not workable. To make it work, I would have to have something like: Sender: bounce-address(a)lists.mailman3.org - untouched From: original.sender@gmail.com@lists.mailman3.org - change #1 having the From address to be From the list Reply-To: original.sender(a)gmail.com - change #2 - if someone replies Then smtp2go will send the email. I looked in the settings and I didn't find a readily available option to do that. I'm new to customizing mailman3 , but have been using it in production for a little more than 1 year. I've seen other software do the solution proposed above, namely DIvi contact forms set the "From" to be something @website.com and the Reply-To: as the form submitter. I am told that the standards is moving away from forging the DATA From: that doesn't have a predictable domain, and instead put the variable email address in Reply-To, for things like contact forms or automated sending. Can someone guide me on where I could start looking?

2 1

Permission Error with /var
by Tibor Molnar Jan. 19, 2023

Jan. 19, 2023

Hi guys, During the build of mailman3 I run in to few permission errors but there is one I have got stuck with, and you may be able to help me with this. I'm following this guide https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10. var_dir: /opt/mailman/mm/var configs: /opt/mailman/mm OS: Debian 10 I'm using virtual env When try start mailman core PermissionError: [Errno 13] Permission denied: '//var/templates' total 48 drwxrwxrwx 12 mailman mailman 4096 Jan 17 11:28 . drwxr-xr-x 7 mailman mailman 4096 Jan 17 17:19 .. drwxr-xr-x 2 mailman mailman 4096 Jan 17 11:10 archives drwxr-xr-x 2 mailman mailman 4096 Jan 17 11:10 cache drwxr-xr-x 2 mailman mailman 4096 Jan 17 11:10 data drwxr-xr-x 2 mailman mailman 4096 Jan 17 11:28 etc drwxr-xr-x 2 mailman mailman 4096 Jan 17 11:10 lists drwxr-xr-x 2 mailman mailman 4096 Jan 17 15:54 locks drwxr-xr-x 2 mailman mailman 4096 Jan 17 14:19 logs drwxr-xr-x 2 mailman mailman 4096 Jan 17 11:10 messages drwxr-xr-x 14 mailman mailman 4096 Jan 17 11:10 queue drwxr-xr-x 2 mailman mailman 4096 Jan 17 16:07 templates all owned by mailman. what are hey suppose to be owned by if not mailman? Regards, Tibor

3 4

hello， Discussion on how to subscribe to the mailing list
by 朱超 Jan. 18, 2023

Jan. 18, 2023

Hi, When I subscribe the email list in Subscription Policy is confirm, Some problems happen in here： 1.Some mail mua reject send the confirm the message, because the length of recipient is too long. for exmaple: requirements-confirm+9605556e0b35a5da280c1de0d34a3e6f770f8ea5@domain, and the mail mua reject to modify about this. 2.It is inconvenient for users to use. Many people will mistakenly think that after clicking the subscribe button, it will be successful, and they will not process the email. Regarding the discussion on the subscription method of the mailing list, should we consider optimizing the subscription method of the mailing list, for example: 1. use the method of sending a verification code to subscribe by email，When you receive the verification code sent by the mailing list and fill it in again, you can subscribe successfully。 2. use the email to send a connection to confirm the subscription，People click the link to be redirected to a confirmation page to subscribe to the email。

4 12

mailman-web causing constant 100% cpu load of mysqld
by Johannes Rohr Jan. 16, 2023

Jan. 16, 2023

Dear all, with mailmanweb running, the CPU load of mysqld constantly hovers around 100% In /var/log/mysql/errors.log I see repeatedly: 2023-01-13 17:22:42 27198 [Warning] Aborted connection 27198 to db: 'mailman_core' user: 'mailman' host: 'localhost' (Got an error reading communication packets) 2023-01-13 17:27:43 29621 [Warning] Aborted connection 29621 to db: 'mailman_core' user: 'mailman' host: 'localhost' (Got an error reading communication packets) This also seems to affect other services such as dovecot which rely on mysql and at times can't connect to it. Does anyone have a suggestion what to do about this? Cheers, Johannes

2 1

Error Logging - what changed with the New Year releases?
by Odhiambo Washington Jan. 15, 2023

Jan. 15, 2023

Apart from all the defaults in settings.py (derived from gitlab), I also have this line: LOGGING['handlers']['file']['filename'] = '/opt/mailman/mm/var/logs/mailmanweb.log' Before the New Year releases of MM3, I used to get errors written to this file. Not anymore after I updated to the New Year releases. Another thing that I have realized is that prior to the New Year releases, I would get an error logged to that file and also mailed to me. I don't think that I have changed anything in settings,py related to logging. I have been trying to get signup with Twitter working. This used to generate an error that was both logged and emailed, but that isn't happening anymore. I have enabled other social auth providers (in settings.py) which I haven't configured in the admin panel. I expect that tying to use these on Postorius would generate an error that is logged and mailed to admin, but that too is not happening. Just checking out what might have changed - or if I am going nuts :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 5

Moderation request reminders
by Allan Hansen Jan. 14, 2023

Jan. 14, 2023

Hi all, I and my moderators are getting daily moderation request reminders. Is there a way to set them to be weekly instead? I looked around in the UI for it but did not see it. It started with my latest server upgrade. As list owner I get 50+ of these messages every morning and my modertors each get only one, but don't like it. I still don't see a link for my moderators to see the membership lists even though the lists are set to allow it. Is that among the planned bug fixes? Yours, Allan

2 1

Cross-List and Domain based sender whitelisting ( accept_these_nonmembers )
by Patrick Brückner Jan. 13, 2023

Jan. 13, 2023

Hi everyone, one of our servers that was running a mailman2 instance just crashed this afternoon, so we decided to take the leap and migrate to 3, and I have to say it worked pretty well, the lists seem to be back. What I can't seem to find is the option to whitelist senders based on a domain AND on membership on a different list. The lists are operated for a smallish university and all the professors need to be allowed to send to the students list, without being member of that list. That was possible with mailman2 by just whitelisting the university domain. Also, in the past we allowed all members of the all-students list to post to any of the dorm-lists (this is mainly used for party announcements so it is not a must have), but I wanted to ask anyways, if there was a chance to allow this feature again. According to the docs, the accept_these_nonmembers option exists (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) but none of my lists have that set after the migration - the field is not even there when accessing the REST API. Do I need to enable something? Has that feature been added just recently, and we are missing out (since we are using the apt packages from ubuntu)? Thanks in advance, Patrick

4 7

About the sender of the mailing list receiving an auto-reply email
by 朱超 Jan. 13, 2023

Jan. 13, 2023

Hi, When I use the mailing list to send emails, I receive an automatic reply email, Is there a better way to block similar automatic reply emails? From: Tom

2 1

Error from - /opt/mailman/mm/bin/django-admin runjobs hourly
by Odhiambo Washington Jan. 12, 2023

Jan. 12, 2023

I have received the following error message from the hourly cron run: <quote> /opt/mailman/mm/bin/django-admin: line 7: 7475 Killed django-admin $@ </quote> I have looked at my log files, but could not find any clue. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 1

mailman.log file owned by 'list' user
by Mike Wertheim Jan. 12, 2023

Jan. 12, 2023

I'm on Debian 11, trying to troubleshoot an installation of Mailman 3.3.3 that was done by someone else. Mailman is running as a non-privileged (non-root) user called 'xyz'. On the day that Mailman was installed, that non-privileged 'xyz' user was able to execute mailman commands successfully to create, view and modify lists. A couple of days later, when the 'xyz' user tried running those same mailman commands, they failed with this error: PermissionError: [Errno 13] Permission denied: '/var/log/mailman3/mailman.log' Doing "ls -l" on the file /var/log/mailman3/mailman.log showed this: -rw-r----- 1 list list 0 Jan 6 00:00 /var/log/mailman3/mailman.log When I did a 'ps' command, I saw that all of the mailman processes are running as user 'xyz'. No processes were running as the user 'list'. It seems that some process is rotating the mailman.log file at midnight, and the newly-created mailman.log is being owned by user 'list'. Can anyone explain why this is happening, and how to fix it?

4 3

Re: Docker or virtualenv?
by J.Schulz Jan. 10, 2023

Jan. 10, 2023

For Docker: just use the README on https://github.com/maxking/docker-mailman ; this should be enough for a basic setup. Eventually, you'll need to add some things to core/mailman-extra.cfg : ___ [mailman] site_owner: help(a)elternserver.de SMTP_MAX_RCPTS = 1 VERP_CONFIRMATIONS = Yes VERP_PASSWORD_REMINDERS = Yes VERP_PERSONALIZED_DELIVERIES = Yes VERP_DELIVERY_INTERVAL = 1 # [devmode] # enabled: yes # recipient: you(a)somewhere.com # # extra local settings for mailmen [mta] # NullMTA is just implementing the interface and thus satisfying Mailman # without doing anything fancy # outgoing: mailman.mta.null.NullMTA smtp_user: your_auth@your_MTA smtp_pass: supersecretpassword smtp_verify_hostname: yesorno smtp_secure_mode: starttls # or whatever # [logging.debug] [logging.smtp] level: warn ___ also, web/settings_local.py needs tweaking in some cases; the DJANGO_ALLOWED_HOSTS come from my docker-compose.yml ---- import os # see https://github.com/maxking/docker-mailman/issues/548 django_allowed_hosts = os.environ.get('DJANGO_ALLOWED_HOSTS') if django_allowed_hosts: ALLOWED_HOSTS = django_allowed_hosts.split(':') MAILMAN_WEB_SOCIAL_AUTH = [] SOCIALACCOUNT_PROVIDERS = { } DEBUG = False # see https://gitlab.com/mailman/mailman/-/issues/957 DEFAULT_AUTO_FIELD='django.db.models.AutoField' HAYSTACK_CONNECTIONS = { 'default': { 'ENGINE': 'xapian_backend.XapianEngine', 'PATH': "/opt/mailman-web-data/fulltext_index", }, } ----- Am 10.01.23 um 09:11 schrieb Odhiambo Washington: > Hi Jörg, > > Kindly share the link to the HOWTO, which you use to setup everything. > I just need to test. Perhaps I can use docker on Windows, no? > > On Mon, Jan 9, 2023 at 8:58 PM Jörg Schulz <info(a)joergschulz.de> wrote: > > I have a successful installation using docker, just updated to the > most > recent version - it runs along quite some other docker containers, so > there is a benefit when I want to switch machines. > > Am 07.01.23 um 12:02 schrieb Odhiambo Washington: > > On Sat, Jan 7, 2023 at 1:54 PM Johannes Rohr <johannes(a)rohr.org> > wrote: > > > >> I wanted to say "I have now chosen virtualenv". Sorry for the > confusion. > >> > > I have never tried docker, but soon I will. Just for the kicks. > > > > > > > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

1 0

SPF check fails for lists subdomain
by Jan Eden Jan. 9, 2023

Jan. 9, 2023

Hi, my question is not related to Mailman directly, apologies for using this list. I configured the DNS records for my base domain and my lists subdomain identically (the DMARC policy records are also identical, but not listed here): MX @ mail.eden.one TXT @ "v=spf1 mx ~all" MX lists mail.eden.one TXT lists "v=spf1 mx ~all" A mail 123.123.123.123 But both Yahoo and Google report different SPF results for the two domains: <policy_published> <domain>eden.one</domain> <adkim>s</adkim> <aspf>s</aspf> <p>quarantine</p> <pct>75</pct> </policy_published> <record> <row> <source_ip>123.123.123.123</source_ip> <count>3</count> <policy_evaluated> <disposition>none</disposition> <dkim>pass</dkim> <spf>pass</spf> </policy_evaluated> </row> <policy_published> <domain>lists.eden.one</domain> <adkim>s</adkim> <aspf>s</aspf> <p>quarantine</p> <pct>75</pct> </policy_published> <record> <row> <source_ip>123.123.123.123</source_ip> <count>2</count> <policy_evaluated> <disposition>none</disposition> <dkim>pass</dkim> <spf>fail</spf> </policy_evaluated> </row> What could possibly cause this difference? The SPF test also fails for a different base domain with the same MX and SPF records. - Jan

3 8

Out there plugin idea for tech cost sponsorship
by Steven Clift EDem Jan. 8, 2023

Jan. 8, 2023

After spending 20 years running a non-profit that hosted email lists for local communities as my day job, that's now all volunteer as I run a startup. Figuring out how to raise money to cover server costs without selling out our members with targeted social media advertising, was a continuous challenge. Anyway, today I am still involved in efforts to route around digital ad behemoths, but I a trying to help small businesses and shop for good brands gain new customers. So here is the question - do you think a Mailman add-on/plugin/module/whatever you'd call it that allowed list admins to reward their new subscribers to email lists with custom themed "for good" discounts would be of interest to many??? Normally, we (GoodCarts) reward people post-checkout with discounts in reciprocity powered circles of online stores. Stores essentially grow together by sharing customers instead of bidding against each other. The way I could see working with email list providers is basically adding an affiliate marketing style commission where purchases with post-subscription rewards would go to the partner based on results. When we go from hundreds of brand members to thousands and add in a "buy local" or brands by theme/values/impact, in theory my non-profits local online community forums could mission align by offering discounts to locally owned businesses. Our view is that exclusive discounts as rewards post transaction (purchase, email list subscription, volunteer sign-up, event registration, online petition signature, etc.) is far better than plastering ads everywhere. Anyway, I'd be curious if you think idea might have legs with Mailman list hosts/admins??? Nothing urgent, just a Saturday morning think different idea. Steven Clift

2 1

Footer broken after migration. Where can I fix it?
by Johannes Rohr Jan. 7, 2023

Jan. 7, 2023

Dear all, after importing the lists from mailman2, almost everything works great, but the footer templates appear broken. Mails sent out contain the line %(web_page_url)slistinfo/%(_internal_name)s So clearly the old templates are not getting explanded. However, when I look in the web interface unter "templates", there is nothing there. Where are these legacy footers stored? In the DB, the table "postorius_emailtemplate" is empty. Thanks! Johannes

2 2

Docker or virtualenv?
by Johannes Rohr Jan. 7, 2023

Jan. 7, 2023

Dear all, I have noticed that Ubuntu's current LTS no longer contains packages for mailman2 and its mailman3 packages are incomplete. So, prior to upgrading the server, I will have to migrate from mailman2 / distro packages to mailman3 installed either in virtualenv or docker. I have got zero experience with virtualenv and some experience with Docker. Overall, the docker method looks easier. Is docker the default method by now? Thanks! Johannes

7 13

virtual_alias_domains
by Johannes Rohr Jan. 6, 2023

Jan. 6, 2023

Dear all, I have to set up mailman3 in an environment where postfix uses virtual alias domains. This is described in https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… I don't understand, though, what I need to do to have mailman generate $PREFIX/var/data/postfix_vmap I have tried to follow the instructions at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/model/docs… with the purpose of setting an alias domain. However, things go sideways quickly: >>> from mailman.interfaces.domain import IDomainManager >>> from zope.component import getUtility >>> manager = getUtility(IDomainManager) Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/opt/mailman/venv/lib/python3.8/site-packages/zope/component/_api.py", line 165, in getUtility raise ComponentLookupError(interface, name) zope.interface.interfaces.ComponentLookupError: (<InterfaceClass mailman.interfaces.domain.IDomainManager>, '') >>> So, something is missing. But, being a complete python layman, I do not know what and how I fix it. Can someone give me a headsup? That would be greatly appreciated! Johannes

1 1

hyperkitty installation: Unclear instructions
by Johannes Rohr Jan. 6, 2023

Jan. 6, 2023

Dear all, I just installed mailman and mailman3-web in virtualenv as described in https://docs.mailman3.org/en/latest/install/virtualenv.html Next I moved on to set up hyperkitty as described in https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html. I got confused by the instructions: "Install the code Install the HyperKitty package and its dependencies with the following commands: sudo python setup.py install" Obviously this is a python script in a package that has to be downloaded from somewhere. Why? Doesn't the command pip install mailman-web mailman-hyperkitty already do the job? Apparently, there is a second way of installing hyperkitty, using virtualenv, where you have to check out the code from gitlab and install from there. However, this still doesn't look right, as hyperkitty apparently can also be installed through pip install hyperkitty But then, hyperkitty seems to be already have been pulled in by mailman-web, looking at its dependencies. If that's the case, then neither the instructions at https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html nor those at https://docs.mailman3.org/projects/hyperkitty/en/latest/development.html are correct. Can someone enlighten me on what the canonical way is of installing and setting it up in virtualenv? Thanks a lot in advance! Johannes

2 6

Re: Configure MM3 with separate IMAP Mailserver
by Clemens Leider Jan. 2, 2023

Jan. 2, 2023

Hi Mark, much appreciated! This is for sending messages, right? How about the recieving part…I read different things around that i need multiple mailboxes created, postfix installed, relays, ASMTPDirect etc…can you guide me a bit here, please? I havent found that one instruction that would solve this for me until now. Would just like to avoid to have to administer my own mailserver locally, if i have a perfectly configured one with my provider. CL

2 1

Extracting mailing list users
by Jan Eden Jan. 2, 2023

Jan. 2, 2023

Hi, I would like to export users of my mailing lists including their full name (if present). The export button in Postorius creates a CSV with addresses only, and the tool bin/list_members mentioned in the [Mailman 2 FAQ] does not seem to be available in Mailman 3. I have full access to the server/database, so scraping the web interface with [Mark's script] seems unneccessary. Is there an SQL statement (or an equivalent of bin/list_members) to extract the data? Thanks, Jan [Mailman 2 FAQ]: https://wiki.list.org/DOC/How%20do%20I%20extract%20%28export%29%20a%20list%… [Mark's script]: https://www.msapiro.net/scripts/mailman-subscribers3.py

6 19

Configure MM3 with separate IMAP Mailserver
by clemens.leider＠gmail.com Jan. 2, 2023

Jan. 2, 2023

Dear all, we have managed to setup MM3 following the docker Installation concept/Tutorial. So far so good. However now i am struggeling with connecting to MTA. We are using imap server of our hosting provider.how to integrate that properly? Google was not too much of help unfortunately…looking for some tutorial or howto/step by step if possible. Thanks in advance CL

2 1

Web UI setup
by Lars Bjørndal Dec. 31, 2022

Dec. 31, 2022

Thanks a lot for all your valuable help! I've followed the guide at <https://docs.mailman3.org/en/latest/install/virtualenv.html> I need to run mailman 2 and mailman 3 in parallel until I've migrated all lists, on several domains. I created the file /etc/httpd/conf.d/mailman3.conf with the content <VirtualHost *:80> ErrorLog logs/mailman3-error_log CustomLog logs/mailman3-access_log common RewriteEngine on RewriteCond %{HTTPS} off [NC] RewriteRule ^/mailman3(/.*) https://%{HTTP_HOST}/mailman3$1 [L,R=permanent] </VirtualHost> <VirtualHost *:443> ErrorLog logs/mailman3-error_log CustomLog logs/mailman3-access_log common include conf.d/certref.inc SSLEngine on </VirtualHost> <location /mailman3> ProxyPass http://localhost:8000 </location> The idea is to prepare mailman3 for several virtual domains. When I connect to lamasti.net/mailman3, the title is example.com. How can I change that? Thanks Lars

2 1

Apache
by Lars Bjørndal Dec. 31, 2022

Dec. 31, 2022

I have already Apache installed and running for mailman2 and other resources. How do I serve mailman3 from Apache for the respective domains? Thanks in advance Lars

3 3

Early release of mailman 3.3.8 possible?
by Torge Riedel Dec. 31, 2022

Dec. 31, 2022

Dear list / devs, is it possible to release 3.3.8 early? As far as I can see it is a prereq for my planned upgrade of the server from Ubuntu LTS 20.04 to Ubunto LTS 22.04. I use MySQL in my setup (own installation in venv), so my installation is affected by #1044, which is closed in 3.3.8 Also Ubuntu LTS 22.04 comes with Python 3.10 (https://packages.ubuntu.com/search?suite=jammy&keywords=python3) where the support is also stated earliest for 3.3.8 (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.…) Am I right with my findings? I planned to upgrade the server until end of this year, because there is less traffic in the last days of a year. But I think unless 3.3.8 is not released, I cannot update the server. Kind regards Torge

4 5

MM2 -> MM3 Migration
by Odhiambo Washington Dec. 31, 2022

Dec. 31, 2022

I looked at my list archives and saw that the latest post was on Dec 8, 2022. Then, because I wanted to import any posts that happened from 8th to now(), I looked at two posts: 1. https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This talks about 'hyperkitty_import *--since=01.01.2022* -l mylist@mydomain my-mbox-file' 2. https://mail.python.org/pipermail/mailman-users/2018-July/083607.html Which talks about 'hyperkitty_import *--since='1990-01-01'* -l mylist@mydomain my-mbox-file' I am concerned about the implication of the date format here, especially because our species from America write their dates differently than the British, even though the British colonized us all :P Well, I haven't looked at the manpage (--help) before posting this, and I know I should, but even without that, does Mailman speak American or British English when it comes to the date format? :-) In my case, I have done this: ' hyperkitty_import --since='2022-12-08' -l mylist@mydomain my-mbox-file' After that I ran: /opt/mailman/mm/bin/django-admin update_index_one_listmylist@mydomain And I am hoping that I will have the posts since Dec 8 to Dec 29 showing up in my archives. However, I am not sure. Hope someone can explain to the audience. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 5

Twitter OAuth2
by Odhiambo Washington Dec. 31, 2022

Dec. 31, 2022

I'd like to integrate Twitter OAuth as part of the Social Accounts in my setup. I have gone through https://django-allauth.readthedocs.io/en/latest/providers.html#twitter, but cannot find the config options to add to my settings. Does someone have a config block setting for "SOCIALACCOUNT_PROVIDERS =" ? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 15

combine postorius and hyperkitty into one Apache vhost
by Wolfgang Rosenauer Dec. 29, 2022

Dec. 29, 2022

Hi, I'm in the process to set up a new mailman3 site. (Migrating from mailman2) There are RPMs for my distribution which integrate postorius and hyperkitty with uwsgi. The provided samples assume that both are running in different vhosts what I would like to avoid. Since I couldn't find any uwsgi examples for that I'm experimenting heavily but still having issues. I might just miss a simple thing (hopefully). My current apache config: Alias "/mailman/static" "/srv/www/webapps/mailman/postorius/static" ProxyPassMatch ^/mailman/static ! ProxyPass /mailman unix:/run/uwsgi/uwsgi-postorius.sock|uwsgi://localhost-postorius/ Alias "/archives/static" "/srv/www/webapps/mailman/hyperkitty/static" ProxyPassMatch ^/archives/static ! ProxyPass /archives unix:/run/uwsgi/uwsgi-hyperkitty.sock|uwsgi://localhost-hyperkitty/ This currently assumes that postorius just gets a mailman/ prefix and hyperkitty archives/ This setup immediately fails because of the urlpatterns filter in these components. For testing purposes I changed the patterns in urls.py slightly and I could make it work for me. BUT: This cannot be the solution, can it? Isn't there an easier way to allow these components to run under a different document root? Something slightly unrelated but causing issues in some edge cases also is that Django? does not detect the request url properly. For some functionality e.g. when I want to login to Django admin under /archives/admin (even after modifying urls.py) I get a redirect after the form which shows that my initial path was not recognized as /archives/admin but /archive//admin instead. So the last character is replaced with a / Any hints for me? Thanks, Wolfgang

3 3

hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header
by Odhiambo Washington Dec. 29, 2022

Dec. 29, 2022

I worke up to 959 such entries in my mailmanweb.log: ERROR 2022-12-27 22:49:57,732 82073 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-12-27 22:49:57,784 82073 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-12-27 22:50:05,746 82073 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-12-27 22:50:06,022 82073 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-12-27 22:50:06,183 82073 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-12-27 22:50:06,273 82073 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-12-27 22:50:06,353 82073 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-12-27 22:50:06,435 82073 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. What might have been the cause of this? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 4

Internal Server Error: /mailman3/accounts/fedora/login/
by Mohsen Masoudfar Dec. 29, 2022

Dec. 29, 2022

Hi, I am getting the following errors starting some days ago. It is unclear to me what is causing this. I searched internet, there are some similar reports that mention bugs causing this. I am running mailman3 as Ubuntu 18 package and they do not provide any update for this. Internal Server Error: /mailman3/accounts/fedora/login/ ProgrammingError at /accounts/fedora/login/ relation "socialaccount_openidstore" does not exist LINE 1: SELECT COUNT(*) AS "__count" FROM "socialaccount_openidstore... ^ Request Method: GET Request URL: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flistserv2… Django Version: 1.11.11 Python Executable: /usr/bin/uwsgi-core Python Version: 2.7.17 Python Path: ['.', '', '/usr/lib/python2.7', '/usr/lib/python2.7/plat-x86_64-linux-gnu', '/usr/lib/python2.7/lib-tk', '/usr/lib/python2.7/lib-old', '/usr/lib/python2.7/lib-dynload', '/usr/local/lib/python2.7/dist-packages', '/usr/lib/python2.7/dist-packages'] Server time: Tue, 27 Dec 2022 11:01:12 -0500 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', 'paintstore', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora') Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.auth.middleware.SessionAuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Traceback: File "/usr/lib/python2.7/dist-packages/django/core/handlers/exception.py" in inner 41. response = get_response(request) File "/usr/lib/python2.7/dist-packages/django/core/handlers/base.py" in _legacy_get_response 249. response = self._get_response(request) File "/usr/lib/python2.7/dist-packages/django/core/handlers/base.py" in _get_response 187. response = self.process_exception_by_middleware(e, request) File "/usr/lib/python2.7/dist-packages/django/core/handlers/base.py" in _get_response 185. response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python2.7/dist-packages/django/views/generic/base.py" in view 68. return self.dispatch(request, *args, **kwargs) File "/usr/lib/python2.7/dist-packages/django/views/generic/base.py" in dispatch 88. return handler(request, *args, **kwargs) File "/usr/lib/python2.7/dist-packages/django_mailman3/lib/auth/fedora/views.py" in get 59. return self.post(request, *args, **kwargs) File "/usr/lib/python2.7/dist-packages/django_mailman3/lib/auth/fedora/views.py" in post 72. auth_request = client.begin(form.cleaned_data['openid']) File "/usr/lib/python2.7/dist-packages/openid/consumer/consumer.py" in begin 353. return self.beginWithoutDiscovery(service, anonymous) File "/usr/lib/python2.7/dist-packages/openid/consumer/consumer.py" in beginWithoutDiscovery 376. auth_req = self.consumer.begin(service) File "/usr/lib/python2.7/dist-packages/openid/consumer/consumer.py" in begin 598. assoc = self._getAssociation(service_endpoint) File "/usr/lib/python2.7/dist-packages/openid/consumer/consumer.py" in _getAssociation 1158. assoc = self.store.getAssociation(endpoint.server_url) File "/usr/lib/python2.7/dist-packages/allauth/socialaccount/providers/openid/utils.py" in getAssociation 96. if stored_assocs.count() == 0: File "/usr/lib/python2.7/dist-packages/django/db/models/query.py" in count 364. return self.query.get_count(using=self.db) File "/usr/lib/python2.7/dist-packages/django/db/models/sql/query.py" in get_count 504. number = obj.get_aggregation(using, ['__count'])['__count'] File "/usr/lib/python2.7/dist-packages/django/db/models/sql/query.py" in get_aggregation 485. result = compiler.execute_sql(SINGLE) File "/usr/lib/python2.7/dist-packages/django/db/models/sql/compiler.py" in execute_sql 899. raise original_exception Exception Type: ProgrammingError at /accounts/fedora/login/ Exception Value: relation "socialaccount_openidstore" does not exist LINE 1: SELECT COUNT(*) AS "__count" FROM "socialaccount_openidstore... ^ Request information: USER: AnonymousUser GET: process = u'login' next = u'/mailman3/hyperkitty/list/sec_g_zoom(a)listserv2.aaas.org/message/new' POST: No POST data FILES: No FILES data COOKIES: No cookie data META: CONTEXT_DOCUMENT_ROOT = '/var/www/html' CONTEXT_PREFIX = '' DOCUMENT_ROOT = '/var/www/html' GATEWAY_INTERFACE = 'CGI/1.1' HTTPS = 'on' HTTP_ACCEPT = '*/*' HTTP_ACCEPT_ENCODING = 'gzip, deflate, br' HTTP_CONNECTION = 'keep-alive' HTTP_FROM = 'googlebot(at)googlebot.com' HTTP_HOST = 'listserv2.aaas.org' HTTP_USER_AGENT = 'Googlebot/2.1 (+https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.google.com%2Fbot.html&data=05%7C01%7Cmmasoudf%40aaas.org%7Cc767333920c94048355708dae823947a%7C2eebd8ff9ed140f0a15638e5dfb3bc56%7C0%7C0%7C638077536774767693%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=8%2F5tgjkoHnu%2BWaHwrNVRzcJUh%2BcQ9%2BFUkmB3psMzKMU%3D&reserved=0)' PATH = '/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin' PATH_INFO = u'/accounts/fedora/login/' QUERY_STRING = 'process=login&next=%2Fmailman3%2Fhyperkitty%2Flist%2Fsec_g_zoom%40listserv2.aaas.org%2Fmessage%2Fnew' REMOTE_ADDR = '66.249.66.53' REMOTE_PORT = '37189' REQUEST_METHOD = 'GET' REQUEST_SCHEME = 'https' REQUEST_URI = '/mailman3/accounts/fedora/login/?process=login&next=%2Fmailman3%2Fhyperkitty%2Flist%2Fsec_g_zoom%40listserv2.aaas.org%2Fmessage%2Fnew' SCRIPT_FILENAME = 'proxy:uwsgi://localhost//accounts/fedora/login/' SCRIPT_NAME = u'/mailman3' SERVER_ADDR = '172.24.9.130' SERVER_ADMIN = 'mmasoudf(a)aaas.org' SERVER_NAME = 'listserv2.aaas.org' SERVER_PORT = '443' SERVER_PROTOCOL = 'HTTP/1.1' SERVER_SIGNATURE = '<address>Apache/2.4.29 (Ubuntu) Server at listserv2.aaas.org Port 443</address>\n' SERVER_SOFTWARE = 'Apache/2.4.29 (Ubuntu)' SSL_TLS_SNI = 'listserv2.aaas.org' uwsgi.core = 0 uwsgi.node = 'listserv2' uwsgi.version = '2.0.15-debian' wsgi.errors = <open file 'wsgi_errors', mode 'w' at 0x7fdfa1c748a0> wsgi.file_wrapper = '' wsgi.input = <uwsgi._Input object at 0x7fdfa1ccc710> wsgi.multiprocess = False wsgi.multithread = True wsgi.run_once = False wsgi.url_scheme = 'https' wsgi.version = u'(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 = u"(('Mailman Suite Admin', 'mmasoudf(a)aaas.org'),)" ALLOWED_HOSTS = ['*'] APPEND_SLASH = True AUTHENTICATION_BACKENDS = u"('django.contrib.auth.backends.ModelBackend', 'allauth.account.auth_backends.AuthenticationBackend')" AUTH_PASSWORD_VALIDATORS = u'********************' AUTH_USER_MODEL = u'auth.User' BASE_DIR = '/usr/share/mailman3-web' CACHES = {u'default': {u'BACKEND': u'django.core.cache.backends.locmem.LocMemCache'}} CACHE_MIDDLEWARE_ALIAS = u'default' CACHE_MIDDLEWARE_KEY_PREFIX = u'********************' CACHE_MIDDLEWARE_SECONDS = 600 COMPRESS_CACHEABLE_PRECOMPILERS = u'()' COMPRESS_CACHE_BACKEND = u'default' COMPRESS_CACHE_KEY_FUNCTION = u'********************' COMPRESS_CLEAN_CSS_ARGUMENTS = u'' COMPRESS_CLEAN_CSS_BINARY = u'cleancss' COMPRESS_CLOSURE_COMPILER_ARGUMENTS = u'' COMPRESS_CLOSURE_COMPILER_BINARY = u'java -jar compiler.jar' COMPRESS_CSS_COMPRESSOR = u'compressor.css.CssCompressor' COMPRESS_CSS_FILTERS = [u'compressor.filters.css_default.CssAbsoluteFilter'] COMPRESS_CSS_HASHING_METHOD = u'mtime' COMPRESS_DATA_URI_MAX_SIZE = 1024 COMPRESS_DEBUG_TOGGLE = None COMPRESS_ENABLED = True COMPRESS_JINJA2_GET_ENVIRONMENT = <function JINJA2_GET_ENVIRONMENT at 0x7fdfa1de2f50> COMPRESS_JS_COMPRESSOR = u'compressor.js.JsCompressor' COMPRESS_JS_FILTERS = [u'compressor.filters.jsmin.JSMinFilter'] COMPRESS_MINT_DELAY = 30 COMPRESS_MTIME_DELAY = 10 COMPRESS_OFFLINE = False COMPRESS_OFFLINE_CONTEXT = {u'STATIC_URL': '/mailman3/static/'} COMPRESS_OFFLINE_MANIFEST = u'manifest.json' COMPRESS_OFFLINE_TIMEOUT = 31536000 COMPRESS_OUTPUT_DIR = u'CACHE' COMPRESS_PARSER = u'compressor.parser.AutoSelectParser' COMPRESS_PRECOMPILERS = u"(('text/less', 'lessc {infile} {outfile}'), ('text/x-scss', 'sass -t compressed {infile} {outfile}'), ('text/x-sass', 'sass -t compressed {infile} {outfile}'))" COMPRESS_REBUILD_TIMEOUT = 2592000 COMPRESS_ROOT = '/var/lib/mailman3/web/static' COMPRESS_STORAGE = u'compressor.storage.CompressorFileStorage' COMPRESS_TEMPLATE_FILTER_CONTEXT = {u'STATIC_URL': '/mailman3/static/'} COMPRESS_URL = '/mailman3/static/' COMPRESS_URL_PLACEHOLDER = u'/__compressor_url_placeholder__/' COMPRESS_VERBOSE = False COMPRESS_YUGLIFY_BINARY = u'yuglify' COMPRESS_YUGLIFY_CSS_ARGUMENTS = u'--terminal' COMPRESS_YUGLIFY_JS_ARGUMENTS = u'--terminal' COMPRESS_YUI_BINARY = u'java -jar yuicompressor.jar' COMPRESS_YUI_CSS_ARGUMENTS = u'' COMPRESS_YUI_JS_ARGUMENTS = u'' CSRF_COOKIE_AGE = 31449600 CSRF_COOKIE_DOMAIN = None CSRF_COOKIE_HTTPONLY = False CSRF_COOKIE_NAME = u'csrftoken' CSRF_COOKIE_PATH = u'/' CSRF_COOKIE_SECURE = False CSRF_FAILURE_VIEW = u'django.views.csrf.csrf_failure' CSRF_HEADER_NAME = u'HTTP_X_CSRFTOKEN' CSRF_TRUSTED_ORIGINS = [] CSRF_USE_SESSIONS = False DATABASES = {'default': {'ENGINE': 'django.db.backends.postgresql_psycopg2', 'AUTOCOMMIT': True, 'ATOMIC_REQUESTS': False, 'NAME': 'mailman3web', 'CONN_MAX_AGE': 0, 'TIME_ZONE': None, 'PORT': '', 'HOST': 'localhost', 'USER': 'mailman3web', 'TEST': {'COLLATION': None, 'CHARSET': None, 'NAME': None, 'MIRROR': None}, 'PASSWORD': u'********************', 'OPTIONS': {}}} DATABASE_ROUTERS = [] DATA_UPLOAD_MAX_MEMORY_SIZE = 2621440 DATA_UPLOAD_MAX_NUMBER_FIELDS = 1000 DATETIME_FORMAT = u'N j, Y, P' DATETIME_INPUT_FORMATS = [u'%Y-%m-%d %H:%M:%S', u'%Y-%m-%d %H:%M:%S.%f', u'%Y-%m-%d %H:%M', u'%Y-%m-%d', u'%m/%d/%Y %H:%M:%S', u'%m/%d/%Y %H:%M:%S.%f', u'%m/%d/%Y %H:%M', u'%m/%d/%Y', u'%m/%d/%y %H:%M:%S', u'%m/%d/%y %H:%M:%S.%f', u'%m/%d/%y %H:%M', u'%m/%d/%y'] DATE_FORMAT = u'N j, Y' DATE_INPUT_FORMATS = [u'%Y-%m-%d', u'%m/%d/%Y', u'%m/%d/%y', u'%b %d %Y', u'%b %d, %Y', u'%d %b %Y', u'%d %b, %Y', u'%B %d %Y', u'%B %d, %Y', u'%d %B %Y', u'%d %B, %Y'] DEBUG = False DEBUG_PROPAGATE_EXCEPTIONS = False DECIMAL_SEPARATOR = u'.' DEFAULT_CHARSET = u'utf-8' DEFAULT_CONTENT_TYPE = u'text/html' DEFAULT_EXCEPTION_REPORTER_FILTER = u'django.views.debug.SafeExceptionReporterFilter' DEFAULT_FILE_STORAGE = u'django.core.files.storage.FileSystemStorage' DEFAULT_FROM_EMAIL = 'postorius(a)listserv2.aaas.org' DEFAULT_INDEX_TABLESPACE = u'' DEFAULT_TABLESPACE = u'' DISALLOWED_USER_AGENTS = [] EMAILNAME = 'listserv2.aaas.org' EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = u'localhost' EMAIL_HOST_PASSWORD = u'********************' EMAIL_HOST_USER = u'' EMAIL_PORT = 25 EMAIL_SSL_CERTFILE = None EMAIL_SSL_KEYFILE = u'********************' EMAIL_SUBJECT_PREFIX = u'[Django] ' EMAIL_TIMEOUT = None EMAIL_USE_LOCALTIME = False EMAIL_USE_SSL = False EMAIL_USE_TLS = False FILE_CHARSET = u'utf-8' FILE_UPLOAD_DIRECTORY_PERMISSIONS = None FILE_UPLOAD_HANDLERS = [u'django.core.files.uploadhandler.MemoryFileUploadHandler', u'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 = u'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 = u"('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', 'paintstore', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora')" INTERNAL_IPS = [] LANGUAGES = [(u'af', u'Afrikaans'), (u'ar', u'Arabic'), (u'ast', u'Asturian'), (u'az', u'Azerbaijani'), (u'bg', u'Bulgarian'), (u'be', u'Belarusian'), (u'bn', u'Bengali'), (u'br', u'Breton'), (u'bs', u'Bosnian'), (u'ca', u'Catalan'), (u'cs', u'Czech'), (u'cy', u'Welsh'), (u'da', u'Danish'), (u'de', u'German'), (u'dsb', u'Lower Sorbian'), (u'el', u'Greek'), (u'en', u'English'), (u'en-au', u'Australian English'), (u'en-gb', u'British English'), (u'eo', u'Esperanto'), (u'es', u'Spanish'), (u'es-ar', u'Argentinian Spanish'), (u'es-co', u'Colombian Spanish'), (u'es-mx', u'Mexican Spanish'), (u'es-ni', u'Nicaraguan Spanish'), (u'es-ve', u'Venezuelan Spanish'), (u'et', u'Estonian'), (u'eu', u'Basque'), (u'fa', u'Persian'), (u'fi', u'Finnish'), (u'fr', u'French'), (u'fy', u'Frisian'), (u'ga', u'Irish'), (u'gd', u'Scottish Gaelic'), (u'gl', u'Galician'), (u'he', u'Hebrew'), (u'hi', u'Hindi'), (u'hr', u'Croatian'), (u'hsb', u'Upper Sorbian'), (u'hu', u'Hungarian'), (u'ia', u'Interlingua'), (u'id', u'Indonesian'), (u'io', u'Ido'), (u'is', u'Icelandic'), (u'it', u'Italian'), (u'ja', u'Japanese'), (u'ka', u'Georgian'), (u'kk', u'Kazakh'), (u'km', u'Khmer'), (u'kn', u'Kannada'), (u'ko', u'Korean'), (u'lb', u'Luxembourgish'), (u'lt', u'Lithuanian'), (u'lv', u'Latvian'), (u'mk', u'Macedonian'), (u'ml', u'Malayalam'), (u'mn', u'Mongolian'), (u'mr', u'Marathi'), (u'my', u'Burmese'), (u'nb', u'Norwegian Bokm\xe5l'), (u'ne', u'Nepali'), (u'nl', u'Dutch'), (u'nn', u'Norwegian Nynorsk'), (u'os', u'Ossetic'), (u'pa', u'Punjabi'), (u'pl', u'Polish'), (u'pt', u'Portuguese'), (u'pt-br', u'Brazilian Portuguese'), (u'ro', u'Romanian'), (u'ru', u'Russian'), (u'sk', u'Slovak'), (u'sl', u'Slovenian'), (u'sq', u'Albanian'), (u'sr', u'Serbian'), (u'sr-latn', u'Serbian Latin'), (u'sv', u'Swedish'), (u'sw', u'Swahili'), (u'ta', u'Tamil'), (u'te', u'Telugu'), (u'th', u'Thai'), (u'tr', u'Turkish'), (u'tt', u'Tatar'), (u'udm', u'Udmurt'), (u'uk', u'Ukrainian'), (u'ur', u'Urdu'), (u'vi', u'Vietnamese'), (u'zh-hans', u'Simplified Chinese'), (u'zh-hant', u'Traditional Chinese')] LANGUAGES_BIDI = [u'he', u'ar', u'fa', u'ur'] LANGUAGE_CODE = 'en-us' LANGUAGE_COOKIE_AGE = None LANGUAGE_COOKIE_DOMAIN = None LANGUAGE_COOKIE_NAME = u'django_language' LANGUAGE_COOKIE_PATH = u'/' LOCALE_PATHS = [] LOGGING = {'loggers': {'django': {'handlers': ['file'], 'propagate': True, 'level': 'INFO'}, 'hyperkitty': {'handlers': ['file'], 'propagate': True, 'level': 'INFO'}, 'django.request': {'handlers': ['mail_admins', 'file'], 'propagate': True, 'level': 'INFO'}, 'postorius': {'handlers': ['file'], 'propagate': True, 'level': 'INFO'}}, 'disable_existing_loggers': False, 'handlers': {'console': {'formatter': 'simple', 'class': 'logging.StreamHandler'}, 'file': {'level': 'INFO', 'formatter': 'verbose', 'class': 'logging.handlers.RotatingFileHandler', 'filename': '/var/log/mailman3/web/mailman-web.log'}, 'mail_admins': {'class': 'django.utils.log.AdminEmailHandler', 'filters': ['require_debug_false'], 'level': 'ERROR'}}, 'formatters': {'simple': {'format': '%(levelname)s %(message)s'}, 'verbose': {'format': '%(levelname)s %(asctime)s %(process)d %(name)s %(message)s'}}, 'version': 1, 'filters': {'require_debug_false': {'()': 'django.utils.log.RequireDebugFalse'}}} LOGGING_CONFIG = u'logging.config.dictConfig' LOGIN_REDIRECT_URL = 'list_index' LOGIN_URL = 'account_login' LOGOUT_REDIRECT_URL = None LOGOUT_URL = 'account_logout' MAILMAN_ARCHIVER_FROM = u"('127.0.0.1', '::1')" MAILMAN_ARCHIVER_KEY = u'********************' MAILMAN_REST_API_PASS = u'********************' MAILMAN_REST_API_URL = u'********************' MAILMAN_REST_API_USER = u'********************' MANAGERS = [] MEDIA_ROOT = u'' MEDIA_URL = u'' MESSAGE_STORAGE = u'django.contrib.messages.storage.fallback.FallbackStorage' MESSAGE_TAGS = {40: 'danger'} MIDDLEWARE = None MIDDLEWARE_CLASSES = u"('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.auth.middleware.SessionAuthenticationMiddleware', '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 = u'F j' NUMBER_GROUPING = 0 PASSWORD_HASHERS = u'********************' PASSWORD_RESET_TIMEOUT_DAYS = u'********************' PREPEND_WWW = False Q_CLUSTER = {'orm': 'default', 'save_limit': 100, 'timeout': 300} ROOT_URLCONF = 'urls' SECRET_KEY = u'********************' SECURE_BROWSER_XSS_FILTER = False SECURE_CONTENT_TYPE_NOSNIFF = False SECURE_HSTS_INCLUDE_SUBDOMAINS = False SECURE_HSTS_PRELOAD = False SECURE_HSTS_SECONDS = 0 SECURE_PROXY_SSL_HEADER = None SECURE_REDIRECT_EXEMPT = [] SECURE_SSL_HOST = None SECURE_SSL_REDIRECT = False SERVER_EMAIL = 'root(a)listserv2.aaas.org' SESSION_CACHE_ALIAS = u'default' SESSION_COOKIE_AGE = 1209600 SESSION_COOKIE_DOMAIN = None SESSION_COOKIE_HTTPONLY = True SESSION_COOKIE_NAME = u'sessionid' SESSION_COOKIE_PATH = u'/' SESSION_COOKIE_SECURE = False SESSION_ENGINE = u'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 = u'm/d/Y P' SHORT_DATE_FORMAT = u'm/d/Y' SIGNING_BACKEND = u'django.core.signing.TimestampSigner' SILENCED_SYSTEM_CHECKS = [] SITE_ID = 1 SOCIALACCOUNT_PROVIDERS = {} STATICFILES_DIRS = u'()' STATICFILES_FINDERS = u"('django.contrib.staticfiles.finders.FileSystemFinder', 'django.contrib.staticfiles.finders.AppDirectoriesFinder', 'compressor.finders.CompressorFinder')" STATICFILES_STORAGE = u'django.contrib.staticfiles.storage.StaticFilesStorage' STATIC_ROOT = '/var/lib/mailman3/web/static' STATIC_URL = '/mailman3/static/' TEMPLATES = [{'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']}, 'BACKEND': 'django.template.backends.django.DjangoTemplates'}] TEST_NON_SERIALIZED_APPS = [] TEST_RUNNER = u'django.test.runner.DiscoverRunner' THOUSAND_SEPARATOR = u',' TIME_FORMAT = u'P' TIME_INPUT_FORMATS = [u'%H:%M:%S', u'%H:%M:%S.%f', u'%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 = u'SAMEORIGIN' YEAR_MONTH_FORMAT = u'F Y' Best regards Mohsen Masoudfar

4 5

Approve an email
by Lars Bjørndal Dec. 28, 2022

Dec. 28, 2022

Hi, list! I'm on Fedora 36 with the packages mailman3-3.3.4-6.fc36.noarch and postorius-1.3.6-2.fc36.noarch installed. with the command sudo -u mailman mailman3 create <listname> I was able to create a list. I'm not able to find out how to setup and configure the postorius package. There's no mailman-web command. Hyperkitty will not installed du to a dependency conflict, but I dont need archiving for the list. Here comes my quesitons: - What's the easiest way to approve an email sent to the list? - How can I configure the list to accept messages also from non members? - How can I setup postorius to work on Fedora? I have django-admin, but I'm not sure where to go. Thanks in advance, Lars

3 4

Apache+mod_wsgi issue
by Odhiambo Washington Dec. 27, 2022

Dec. 27, 2022

Still on my MM3 learning path. I mostly have everything running without errors - even uwsgi is starting without errors after I followed the fix from the discussion at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… I have standardized all the files in /opt/mailman/mm/ because this is FreeBSD and our configs for user-installed apps are usually supposed to go to /usr/local/etc/. My VHOST configuration is the exact replica of https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… with the only change being the Python version from 3.6 to 3.9. My challenge now is to get Apache+mod_uwsgi to serve my pages, but I am hitting the error below which has gotten me stuck. Thanking you in advance for your advice on how to overcome this. [Thu Dec 22 14:21:22.758277 2022] [wsgi:info] [pid 4288] [remote 197.232.81.246:15107] mod_wsgi (pid=4288, process='mailman-web', application='mm3-lists.kictanet.or.ke|/mailman3'): Loading Python script file '/opt/mailman/mm/wsgi.py'. [Thu Dec 22 14:21:23.039999 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] mod_wsgi (pid=4288): Failed to exec Python script file '/opt/mailman/mm/wsgi.py'. [Thu Dec 22 14:21:23.040054 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] mod_wsgi (pid=4288): Exception occurred processing WSGI script '/opt/mailman/mm/wsgi.py'. [Thu Dec 22 14:21:23.040841 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] Traceback (most recent call last): [Thu Dec 22 14:21:23.040914 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] File "/opt/mailman/mm/wsgi.py", line 38, in <module> [Thu Dec 22 14:21:23.040921 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] application = get_wsgi_application() [Thu Dec 22 14:21:23.040929 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/wsgi.py", line 12, in get_wsgi_application [Thu Dec 22 14:21:23.040934 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] django.setup(set_prefix=False) [Thu Dec 22 14:21:23.040941 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/__init__.py", line 19, in setup [Thu Dec 22 14:21:23.040945 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] configure_logging(settings.LOGGING_CONFIG, settings.LOGGING) [Thu Dec 22 14:21:23.040952 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/conf/__init__.py", line 92, in __getattr__ [Thu Dec 22 14:21:23.040957 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] self._setup(name) [Thu Dec 22 14:21:23.040964 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/conf/__init__.py", line 79, in _setup [Thu Dec 22 14:21:23.040968 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] self._wrapped = Settings(settings_module) [Thu Dec 22 14:21:23.040975 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/conf/__init__.py", line 190, in __init__ [Thu Dec 22 14:21:23.040979 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] mod = importlib.import_module(self.SETTINGS_MODULE) [Thu Dec 22 14:21:23.040986 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] File "/usr/local/lib/python3.9/importlib/__init__.py", line 127, in import_module [Thu Dec 22 14:21:23.040990 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] return _bootstrap._gcd_import(name[level:], package, level) [Thu Dec 22 14:21:23.040997 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] File "<frozen importlib._bootstrap>", line 1030, in _gcd_import [Thu Dec 22 14:21:23.041004 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] File "<frozen importlib._bootstrap>", line 1007, in _find_and_load [Thu Dec 22 14:21:23.041012 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] File "<frozen importlib._bootstrap>", line 984, in _find_and_load_unlocked [Thu Dec 22 14:21:23.041064 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] ModuleNotFoundError: No module named 'settings' -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

5 41

Errors while importing mm2 list archives
by Odhiambo Washington Dec. 23, 2022

Dec. 23, 2022

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 Dec. 22, 2022

Dec. 22, 2022

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 Dec. 21, 2022

Dec. 21, 2022

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 Dec. 21, 2022

Dec. 21, 2022

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 Dec. 21, 2022

Dec. 21, 2022

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 Dec. 21, 2022

Dec. 21, 2022

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 Dec. 20, 2022

Dec. 20, 2022

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 Dec. 20, 2022

Dec. 20, 2022

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 Dec. 17, 2022

Dec. 17, 2022

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 Dec. 17, 2022

Dec. 17, 2022

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. Dec. 15, 2022

Dec. 15, 2022

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 Dec. 13, 2022

Dec. 13, 2022

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 Dec. 9, 2022

Dec. 9, 2022

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 Dec. 9, 2022

Dec. 9, 2022

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 朱超 Dec. 8, 2022

Dec. 8, 2022

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) Dec. 7, 2022

Dec. 7, 2022

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 Dec. 6, 2022

Dec. 6, 2022

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 Dec. 5, 2022

Dec. 5, 2022

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 Dec. 5, 2022

Dec. 5, 2022

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 Dec. 4, 2022

Dec. 4, 2022

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 Dec. 3, 2022

Dec. 3, 2022

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 Dec. 1, 2022

Dec. 1, 2022

Hi, when trying to reattach a message thread in the Hyperkitty web interface, the following error occurs: > Internal Server Error: /archives/list/testlist@lists.eden.one/thread/T6MCILAVQYV5QIOGHJB3JNJ26Z7E2Z35/reattach-suggest > > PermissionError at /archives/list/testlist@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@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 Nov. 28, 2022

Nov. 28, 2022

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 Nov. 27, 2022

Nov. 27, 2022

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 Nov. 27, 2022

Nov. 27, 2022

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 Nov. 25, 2022

Nov. 25, 2022

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 Nov. 23, 2022

Nov. 23, 2022

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 Nov. 21, 2022

Nov. 21, 2022

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 Nov. 16, 2022

Nov. 16, 2022

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 Nov. 15, 2022

Nov. 15, 2022

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 Nov. 11, 2022

Nov. 11, 2022

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 Nov. 8, 2022

Nov. 8, 2022

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 Nov. 8, 2022

Nov. 8, 2022

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 Nov. 4, 2022

Nov. 4, 2022

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é Nov. 4, 2022

Nov. 4, 2022

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 Nov. 3, 2022

Nov. 3, 2022

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 Nov. 3, 2022

Nov. 3, 2022

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 Nov. 3, 2022

Nov. 3, 2022

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 Nov. 3, 2022

Nov. 3, 2022

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 Nov. 1, 2022

Nov. 1, 2022

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é Nov. 1, 2022

Nov. 1, 2022

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) Oct. 31, 2022

Oct. 31, 2022

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

Re: Problems after Upgrade
by Mark Sapiro Oct. 31, 2022

Oct. 31, 2022

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 Oct. 31, 2022

Oct. 31, 2022

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 Oct. 30, 2022

Oct. 30, 2022

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 Oct. 30, 2022

Oct. 30, 2022

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 Oct. 27, 2022

Oct. 27, 2022

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 Oct. 27, 2022

Oct. 27, 2022

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 Oct. 27, 2022

Oct. 27, 2022

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

Internal Server Error: Reattach this thread
by hasimoto＠designet.co.jp Oct. 27, 2022

Oct. 27, 2022

Hi, In the archive, clicking "Reconnect this thread" causes an internal server error. I received the following email, but I don't know how to solve it, please help me. -- -- -- -- Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/list/testml@list1.example.com/thread/LQ6F7D7EVVUSIJJ7B5S675ZVSU5ZZCBU/reattach-suggest -- -- -- -- Internal Server Error: /archives/list/testml@list1.example.com/thread/LQ6F7D7EVVUSIJJ7B5S675ZVSU5ZZCBU/reattach-suggest AttributeError at /archives/list/testml@list1.example.com/thread/LQ6F7D7EVVUSIJJ7B5S675ZVSU5ZZCBU/reattach-suggest 'function' object has no attribute 'lower' Request Method: GET Request URL: http://mailman.example.com/archives/list/testml@list1.example.com/thread/LQ… Django Version: 3.0.14 Python Executable: /opt/mailman/venv/bin/uwsgi Python Version: 3.10.6 Python Path: ['.', '', '/etc/mailman3', '/usr/lib/python310.zip', '/usr/lib/python3.10', '/usr/lib/python3.10/lib-dynload', '/opt/mailman/venv/lib/python3.10/site-packages'] Server time: 水, 19 10月 2022 01:07:28 +0000 Installed Applications: ['hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount'] Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/opt/mailman/venv/lib/python3.10/site-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/opt/mailman/venv/lib/python3.10/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/lib/view_helpers.py", line 134, in inner return func(request, *args, **kwargs) File "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/views/thread.py", line 413, in reattach_suggest default_search_query = stripped_subject( File "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/lib/utils.py", line 155, in stripped_subject if subject.lower().startswith(mlist.subject_prefix.lower()): Exception Type: AttributeError at /archives/list/testml@list1.example.com/thread/LQ6F7D7EVVUSIJJ7B5S675ZVSU5ZZCBU/reattach-suggest Exception Value: 'function' object has no attribute 'lower' Request information: USER: admin GET: q = '' POST: No POST data FILES: No FILES data COOKIES: csrftoken = 'cBq9h8x7bG6BMboc89DB8ucQiToTRTpwijt0uJbVXq47ucV2cAGYh05TsaVARobK' sessionid = 'upuj3rv0wkxafklk633lx2jppwgrco1t' META: CSRF_COOKIE = 'cBq9h8x7bG6BMboc89DB8ucQiToTRTpwijt0uJbVXq47ucV2cAGYh05TsaVARobK' HTTP_ACCEPT = '*/*' HTTP_ACCEPT_ENCODING = 'gzip, deflate' HTTP_ACCEPT_LANGUAGE = 'ja,en-US;q=0.7,en;q=0.3' HTTP_CONNECTION = 'close' HTTP_COOKIE = 'csrftoken=cBq9h8x7bG6BMboc89DB8ucQiToTRTpwijt0uJbVXq47ucV2cAGYh05TsaVARobK; sessionid=upuj3rv0wkxafklk633lx2jppwgrco1t' HTTP_HOST = 'mailman.example.com' HTTP_REFERER = 'http://mailman.example.com/archives/list/testml@list1.example.com/thread/LQ…' HTTP_USER_AGENT = 'Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:105.0) Gecko/20100101 Firefox/105.0' HTTP_X_FORWARDED_FOR = '192.168.30.94' HTTP_X_REQUESTED_WITH = 'XMLHttpRequest' PATH_INFO = '/archives/list/testml@list1.example.com/thread/LQ6F7D7EVVUSIJJ7B5S675ZVSU5ZZCBU/reattach-suggest' QUERY_STRING = 'q=' REMOTE_ADDR = '127.0.0.1' REQUEST_METHOD = 'GET' REQUEST_URI = '/archives/list/testml@list1.example.com/thread/LQ6F7D7EVVUSIJJ7B5S675ZVSU5ZZCBU/reattach-suggest?q=' SCRIPT_NAME = '' SERVER_NAME = 'ubuntu22' SERVER_PORT = '8000' SERVER_PROTOCOL = 'HTTP/1.0' uwsgi.core = 0 uwsgi.node = b'ubuntu22' 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 0x7f4ac0d23570> 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 = 'http' ACCOUNT_EMAIL_REQUIRED = True ACCOUNT_EMAIL_VERIFICATION = 'mandatory' ACCOUNT_UNIQUE_EMAIL = True ADMINS = "(('Mailman Suite Admin', 'admin1(a)example.org'),)" ALLOWED_HOSTS = ['127.0.0.1', 'mailman.example.com'] 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 0x7f4ac443e050> 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 = 'admin1(a)example.org' DEFAULT_INDEX_TABLESPACE = '' DEFAULT_TABLESPACE = '' DISALLOWED_USER_AGENTS = [] EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_HOST_PASSWORD = '********************' EMAIL_HOST_USER = '' 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://mailman.example.com/mailman3/' 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 = 'admin1(a)example.org' 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' -- -- -- -- Thank you.

5 11

"Unsubscribe all" button
by Philippe B Oct. 21, 2022

Oct. 21, 2022

Would it be possible to add a confirmation screen after you click on it? Like: WARNING! Clicking "Confirm" will empty the list of all its existing members, regardless of what was entered on the previous screen. That operation cannot be reversed. Are you absolutely sure that you want no one to be on your list anymore? The reason is that we've had a lot of list owners who populate the "Emails to Unsubscribe" box on the "Mass Removal" page with a subset of the list's subscribers and proceed to click "Unsubscribe all" with the expectation that "all" means all the users explicitly listed in the box. Which means that the site admins have to restore the entire list of subscribers every time... If adding a confirmation screen isn't straightforward, maybe the wording on the buttons could be modified: * Unsubscribe users -> Unsubscribe users listed above * Unsubscribe all -> Empty list of all its existing members (irreversible)!!! In the meantime, this was problematic enough for us that my colleague Dan had to resort to hiding the "Unsubscribe all" button from the web page(s), which isn't ideal.

3 3

HyperKitty failure: {"error": "'Thread' instance needs to have a primary key value before this relationship can be used."} (400)
by Armin Schöffmann Oct. 21, 2022

Oct. 21, 2022

Hello list, using mailman3 as of current gitlab master with db-backend postgresql 14.5, I get the following error whenever a message is handed over to hyperkitty for archiving: Oct 19 11:43:00 2022 (2164807) HyperKitty failure on https://listserv.foo.bar/archives/api/mailman/archive: {"error": "'Thread' instance needs to have a primary key value before this relationship can be used."} (400) Oct 19 11:43:00 2022 (2164807) Could not archive the message with id <kcEE.5Fsdt1DFSK2fk5foEoTfkw.gCYcK5/j2AE@root> Oct 19 11:43:00 2022 (2164807) archiving failed, re-queuing (mailing-list test-list.foo.bar, message <kcEE.5Fsdt1DFSK2fk5foEoTfkw.gCYcK5/j2AE@root>) Oct 19 11:43:00 2022 (2164807) Exception in the HyperKitty archiver: {"error": "'Thread' instance needs to have a primary key value before this relationship can be used."} Oct 19 11:43:00 2022 (2164807) Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.9/site-packages/mailman_hyperkitty/__init__.py", line 158, in _archive_message url = self._send_message(mlist, msg) File "/opt/mailman/venv/lib/python3.9/site-packages/mailman_hyperkitty/__init__.py", line 228, in _send_message raise ValueError(result.text) ValueError: {"error": "'Thread' instance needs to have a primary key value before this relationship can be used."} I already re-created the db, but this doesn't solve the issue. Sounds like db-definitions for model "Thread" are incomplete, but I can't identify the underlying db-objects. Thanks for any input, Armin. -- Aegaeon technologies GmbH phone: +49.941.8107344 fax: +49.941.8107356 Legal disclaimer: http://aegaeon.de/disclaimer/email_all_int.txt

4 7

How to enable VERP?
by Andy Smith Oct. 19, 2022

Oct. 19, 2022

Hi, I'm a little confused as to how to enable VERP. mailman3 Debian package, version 3.3.3-1, using Exim 4 MTA. In /etc/mailman3/mailman.cfg I added: [mailman] … verp_delivery_interval: 1 verp_probes: yes and restarted mailman3.service. The list's "Alter Messages / Personalize" setting is "Individual" (but I tried "Full" as well and saw no difference in VERP behaviour). I can see the MTA is doing an individual delivery for each recipient, and the list's custom footer tells the recipient which address they are subscribed under, so I know that part is working. With VERP enabled I was expecting the Return-Path header in the delivered list mail to include a cookie to identify the individual subscriber, but instead it is "listname-bounces(a)example.com" like always. In mailman.cfg my MTA-related settings are: [mta] incoming: mailman.mta.exim4.LMTP outgoing: mailman.mta.deliver.deliver smtp_host: localhost smtp_port: 25 configuration: python:mailman.config.exim4 And the Exim configuration itself has ther macros, router and transport files from the "Exim" section of here: https://docs.mailman3.org/en/latest/config-core.html#configuring-mta edited only for correct paths. That's been working for months for delivering list email in and out, but I'm just now trying to enable VERP and it's not happening. Is there something I'm missing? Thanks, Andy

2 2

cannot bind to lmtp host address through lmtp port(OSError: [Errno 99] error while attempting to bind on address: cannot assign requested address)
by Paul Ssekamatte Oct. 19, 2022

Oct. 19, 2022

i have successfully set up mailman3 instance by following the guide at https://gitlab.com/mailman/mailman-suite-doc/blob/master/source/install/vir… and from this mailing list. my setup uses an alias domain i.e the mail server is different from the lists server. I have successfully created an alias domain and mailing list through Postorius but I keep getting this error in syslog. OSError: [Errno 99] error while attempting to bind on address ('xxx.xx.xx.xx', 8024): cannot assign requested address. Even when I change the port number, I still get the same error Kindly assist. here is my mailman.cfg config [paths.here] var_dir: /opt/mailman/mm/var [mailman] layout: here site_owner: postmaster(a)mail.example.com [database] class: mailman.database.postgresql.PostgreSQLDatabase url: postgres://mailman:#passwd@localhost/mailman [archiver.prototype] enable: yes # For the HyperKitty archiver. [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /opt/mailman/mm/mailman-hyperkitty.cfg [shell] history_file: $var_dir/history.py [mta] verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1 incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: mail.example.com lmtp_port: 8024 smtp_host: mail.example.com smtp_port: 25 configuration: python:mailman.config.postfix recipient_delimiter = + unknown_local_recipient_reject_code = 550 owner_request_special = no POSTFIX_STYLE_VIRTUAL_DOMAINS= ['example.com'] /etc/mailman3/settings.py file is as follows from mailman_web.settings.base import * from mailman_web.settings.mailman import * ADMINS = ( ('Mailman Suite Admin', 'root@localhost'), ) DATABASES = { 'default': { 'ENGINE': 'django.db.backends.postgresql_psycopg2', 'NAME': 'mailmanweb', 'USER': 'mailman', # TODO: Replace this with the password. 'PASSWORD': 'passwd', 'HOST': 'localhost', 'PORT': '5432', } } STATIC_ROOT = '/opt/mailman/web/static' LOGGING['handlers']['file']['filename'] = '/opt/mailman/web/logs/mailmanweb.log' ALLOWED_HOSTS = [ 'localhost', 'lists.example.com', 'mail.example.com', # Archiving API from Mailman, keep it. ] SITE_ID = 1 SECRET_KEY = 'key MAILMAN_ARCHIVER_KEY = 'key DEFAULT_FROM_EMAIL = 'postmaster(a)example.com' SERVER_EMAIL = 'postmaster(a)example.com' HAYSTACK_CONNECTIONS = { 'default': { 'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', 'PATH': os.path.join(BASE_DIR, "fulltext_index"), }, } /etc/postfix/main.cf is as follows smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu) biff = no append_dot_mydomain = no readme_directory = no compatibility_level = 2 smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases mydomain = example.com myhostname = lists.example.com mydestination = $myhostname, localhost.$mydomain, localhost relayhost = mail.example.com myorigin = $mydomain mynetworks = 127.0.0.0/8, 10.0.0.0, 192.0.0.1, [::ffff:127.0.0.0]/104 [::1]/128 mynetworks_style = subnet mailbox_size_limit = 4096000000 #message_size_limit = 2048000000 recipient_delimiter = + inet_interfaces = all #inet_protocols = all inet_protocols = ipv4 unknown_local_recipient_reject_code = 550 owner_request_special = no virtual_mailbox_domains = example.com virtual_mailbox_base = /var/vmail virtual_uid_maps = static:20000 virtual_gid_maps = static:20000 transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/opt/mailman/mm/var/data/postfix_lmtp relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains virtual_alias_maps = hash:/opt/mailman/mm/var/data/postfix_vmap postfix domains as follows: lists.example.com example.com postfix lmtp as follows: testlist(a)lists.example.com lmtp:[mail.example.com]:8024 testlist-bounces(a)lists.example.com lmtp:[mail.example.com]:8024 testlist-confirm(a)lists.example.com lmtp:[mail.example.com]:8024 postfix vmap as follows: testlist(a)example.com nmutest(a)lists.example.com testlist-bounces(a)example.com nmutest-bounces(a)lists.example.com testlist-confirm(a)example.com nmutest-confirm(a)lists.example.com

2 2

Mailman 3 Hyperkitty indexes not being built
by tom＠gather.coop Oct. 19, 2022

Oct. 19, 2022

My config looks like this: HAYSTACK_CONNECTIONS = { 'default': { 'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', 'PATH': os.path.join(BASE_DIR, "fulltext_index"), ... I have whoosh 2.7.4 installed. But my fulltext_index directory contains only one file, _MAIN_0.toc, which hasn't been updated in two years. What could be going on here? Presumably Hyperkitty should be indexing new messages as they are archived. I could run update_index to fix the index now but then it would just go out of date again. Also asked on SO: https://stackoverflow.com/questions/74055901/mailman-3-hyperkitty-indexes-n… Thank you!

2 1

URL-lines in templates get folded
by Frank Steinberg Oct. 18, 2022

Oct. 18, 2022

Hi, I’ve added links to some templates to give owners and moderators shortcuts to the postorius UI for moderation tasks, e.g., I’ve added https://lists.xxx.de/postorius/lists/$list_id/held_messages <https://lists.xxx.de/postorius/lists/$list_id/held_messages> Unfortunately those lines seem to exceed a certain limit and get folded, so that they appear as, e.g. https://lists.xxx.de/postorius/lists/$list_id/held_ <https://lists.xxx.de/postorius/lists/$list_id/held_> messages (or similar) and are not directly useful. Do you have any suggestion for this situation?

2 4

Is there a way to see all the list's held messages
by bob B Oct. 16, 2022

Oct. 16, 2022

I run mailman but do not admin the lists. Is there a way for me to see all the held messages for all the lists?

3 4

Updating installed pkgs in MM3 venv
by Odhiambo Washington Oct. 15, 2022

Oct. 15, 2022

What is the recommended way for updating installed the installed pkgs in MM3 venv - to ensure that nothing breaks? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 1

Upgrading packages
by Eggert Ehmke Oct. 13, 2022

Oct. 13, 2022

Hello Mark & all, I have the venv installation on my Debian 11 system running. I followed your suggestion to upgrade all packages. When upgrading hyperkitty by this command: pip install --upgrade git+https://gitlab.com/mailman/hyperkitty@master I noticed that mistune-2.0.0rc1 was upgraded to mistune-2.0.4. All packages were upgraded fine. I applied the patch to venv/lib/python3.9/site-packages/hyperkitty/lib/renderer.py to change the mistune import line. When I run now mailman-web migrate I get: *CommandError: Conflicting migrations detected; multiple leaf nodes in the migration graph: (0017_auto_20220628_1132, 0018_alter_emailtemplate_language in postorius).* *To fix them run 'python manage.py makemigrations --merge'* However, when I run the suggested command as: $ python ./venv/lib/python3.9/site-packages/mailman_web/manage.py makemigrations -- merge No conflicts detected to merge. Can I just ignore this behavior? At the moment, I don't dare to carry out these steps on my production system. Would be nice to shed some light on this. Eggert

2 5

Debian 11 mailman3 installation question
by William Oliver Oct. 13, 2022

Oct. 13, 2022

I have had an installation of mailman3 running for a year or so with no problems. This was a manual installation. I ended up having to change machines, so I decided to install using the debian 11 package. It seems to have gone well except.... when I restart mailman3 service, I get the following fail and error message: oot@emergenis:/etc/nginx/sites-enabled# systemctl restart mailman3 Job for mailman3.service failed because the control process exited with error code. See "systemctl status mailman3.service" and "journalctl -xe" for details. root@emergenis:/etc/nginx/sites-enabled# systemctl status mailman3 ● mailman3.service - Mailman3 server Loaded: loaded (/lib/systemd/system/mailman3.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2022-10-11 15:09:45 EDT; 8s ago Docs: man:mailman(1) https://mailman.readthedocs.io/ Process: 1056 ExecStart=/usr/bin/mailman -C /etc/mailman3/mailman.cfg start --force (code=exited, status=1/FAILURE) CPU: 9.193s Oct 11 15:09:43 emergenis.com mailman3[1056]: File "/usr/lib/python3/dist-packages/mailman/commands/cli_control.py", line 109, in start Oct 11 15:09:43 emergenis.com mailman3[1056]: call_name(config.mta.incoming).regenerate() Oct 11 15:09:43 emergenis.com mailman3[1056]: File "/usr/lib/python3/dist-packages/mailman/mta/postfix.py", line 133, in regenerate Oct 11 15:09:43 emergenis.com mailman3[1056]: raise RuntimeError(NL.join(errors)) Oct 11 15:09:43 emergenis.com mailman3[1056]: RuntimeError: command failure: /usr/sbin/postmap /var/lib/mailman3/data/postfix_lmtp, 1, Operation not permitted Oct 11 15:09:43 emergenis.com mailman3[1056]: command failure: /usr/sbin/postmap /var/lib/mailman3/data/postfix_domains, 1, Operation not permitted Oct 11 15:09:45 emergenis.com systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE Oct 11 15:09:45 emergenis.com systemd[1]: mailman3.service: Failed with result 'exit-code'. Oct 11 15:09:45 emergenis.com systemd[1]: Failed to start Mailman3 server. Oct 11 15:09:45 emergenis.com systemd[1]: mailman3.service: Consumed 9.193s CPU time. Heres the ls for /var/lib/mailman3/data: root@emergenis:/var/lib/mailman3/data# ls -l total 8 -rw-rw---- 1 list list 315 Oct 11 15:09 postfix_domains -rw-rw---- 1 list list 318 Oct 11 15:09 postfix_lmtp The web interface comes up and seems to "work" but of course complains that mailman3 isn't actually running. I assume there's some posfix config I haven't done right, but I am clueless as to what it is. Thanks in advance for any pointers. billo

2 6

Default setting for Delivery status
by Mark Dale Oct. 12, 2022

Oct. 12, 2022

Hi, Where and how do I set the default setting of "Delivery status" to be "Enabled". I'm not seeing any clues in mailman3-web/settings.py At the moment, a new subscriber is neither "Enabled" or "Disabled". Thanks, Mark

3 3

Performance issues with Mailman 3
by Wong, Wesley Oct. 8, 2022

Oct. 8, 2022

Hi, I am having some performance problems with Mailman 3 (version 3.3.5) when it sends out a lot of messages to people. We recently migrated from our old Mailman 2.1.x system to Mailman 3.x about 3 months ago. We host about 350 lists with membership counts varying between 10 to 1500 members on some of the lists. I noticed that outbound messages from Mailman to our outbound SMTP are getting delayed up to an hour when Mailman is processing a lot of messages going to lists. I was wondering if there are good performance tuning tips to be considered for Mailman 3 (i.e. OS, database and/os Mailman Core). I am running the setup on a VM. Here is my configuration for VM and OS: VM config: ESX 6.7 (CPU: Intel(R) Xeon(R) Gold 6242) 4 CPU 8 GB SLES 15 SP3 Python 3.9.10 MariaDB 10.5.17 Mailman 3.3.5 Thanks. wesley Wesley Wong Senior Systems Engineer Anderson Computing & Information Services | ACIS 310-206-2571 [ucla-logo---new_smaller] ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: image001.png Replaced multipart/alternative part with first alternative.

2 2

Mailman2 CLI commands for Mailman3
by Dave Hall Oct. 5, 2022

Oct. 5, 2022

Hello. Sorry if this is an old topic. I'm in the process of migrating from 2.1 to 3.2. In my use case one of the advantages of Mailman 2.1 vs services like Google Groups has been the ability to manage lists from the command line. Things like using sync_members to update the list for a committee when the membership of the committee is updated one a year, or like using find_members and remove_members to remove a user from all mailing lists when they leave the organization. Even the ability to script mailing list creation. So far I haven't found these commands in Mailman3. I hope there is a plan to add these soon. Thanks. -Dave -- Dave Hall Binghamton University kdhall(a)binghamton.edu

2 2

Django site - how to create programmatically - new install
by daniel.botting＠codethink.co.uk Oct. 3, 2022

Oct. 3, 2022

Hi all, I've mainly setup mailman3 to replace our mailman 2.1 install using Ansible, a point I could do with some assistance on is setting the fqdn used programmatically. I've been doing alot of reading before creating this thread. To create a domain I currently navigate to: https://serverfqdn.com/postorius/domains/ and click 'Add Domain'. I believe this is setting the name of the Django site, please accept my apologies if I'm wrong and the SITE_ID=1 is then used, I am only planning to use one domain only. I'm using Postgres and when I check the contents of the Django_mailman3_maildomain table as below afterwards: mailman3web=# TABLE django_mailman3_maildomain; id | mail_domain | site_id ----+--------------------------------------+--------- 1 | mailman3-test2.guest.codethink.co.uk | 1 Many thanks Daniel

2 2

Upgrade Mailmam Core from
by sascha.rissel＠gmail.com Oct. 3, 2022

Oct. 3, 2022

Hello, I have newly set up Mailman 3 on Ubuntu 20.04. Sending and receiving mails between list members does work, but I am currently experiencing two issues: 1) a lists non-members who send mails to the list don't get notified about the message being held for moderation. Moderation itself doesn't seem to work. The moderation list is always empty. 2) Archiving is activated within list settings, but there isn't any archive created. I found this thread, where the first of these issues is also described: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… Here there is an incompatibility between Mailmain 3 and Python depicted, which also seems to affect me. I am running Mailman 3.2.2 on Python 3 .8.10. So I need to either upgrade Mailman Core or downgrade Python. I already did > apt-get upgrade > apt-get update Unfortunately this didn't upgrade Mailman Core's version. Which steps do I have to undertake to upgrade Mailman Core? Regards, Sascha.

5 13

All addresses in a bounced list posting seem to be considered as bouncing
by Andy Smith Oct. 1, 2022

Oct. 1, 2022

Hi, I noticed this happened (bounce.log): Jul 09 12:46:51 2022 (71506) Member xxxxx(a)xxxxx.force9.co.uk already scored a bounce on list users.mailman.bitfolk.com today. Jul 09 12:46:51 2022 (71506) Bounce message for a non subscriber: Email users-leave(a)mailman.bitfolk.com is not a subcriber of users.mailman.bitfolk.com Jul 09 12:46:51 2022 (71506) Member andy(a)bitfolk.com on list users.mailman.bitfolk.com, bounce score = 1. Jul 09 12:46:51 2022 (71506) Bounce message for a non subscriber: Email users(a)mailman.bitfolk.com is not a subcriber of users.mailman.bitfolk.com What happened here is that a reply to one of my posts was rejected by subscriber xxxxx(a)xxxxx.force9.co.uk at smtp time (Exim mainlog): 2022-07-09 12:46:13 1oA9qc-007qOx-0T ** xxxxx(a)xxxxx.force9.co.uk R=dnslookup T=remote_smtp H=mx.avasin.plus.net [212.159.8.200] X=TLS1.2:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256 CV=yes DN="businessCategory=Private Organization,jurisdictionOfIncorporationCountryName=GB,serialNumber=03279013,C=GB,L=Sheffield,O=Plusnet plc,CN=mx.avasin.plus.net": SMTP error from remote mail server after end of data: 552 Spam Message Rejected The message contained my email address (andy(a)bitfolk.com) in quoted text, since it was a reply to a message of mine, and also contained addresses from the list's footer, which accounts for the log messages about users-leave(a)mailman.bitfolk.com and users(a)mailman.bitfolk.com. I'm concerned that Mailman seems to have scored my address as bouncing even though it isn't, merely because it appears inside a message that was rejected. Is that expected? Is there any way to avoid it? I see that Mailman has a bunch of heuristics to parse bounce messages. In this case though, there shouldn't have been a bounce message received to users-bounces@, as this was an SMTP-time rejection. Mailman seems to have parsed addresses out of the actual mail it was sending, rather than only scoring the subscriber address it was trying to send a list posting to. Cheers, Andy

3 11

Help addressing some issues with mailman 3 docker images
by Clark Boylan Oct. 1, 2022

Oct. 1, 2022

Hello, Some of us at opendev.org are looking to migrate to mailman 3 for our list servers. We've got about 98% of things sorted out using maxking's docker images (thank you for publishing those along with excellent documentation). There are however a small number of things that we've run into that we'd like to address before we take this to production. * Mailman 3 relies on lynx to convert html email to txt email. Lynx isn't currently installed in the docker images, but I've pushed a PR to add it to the images. https://github.com/maxking/docker-mailman/pull/552 * There are some user and group inconsistencies between the images. Not a deal breaker, but would be good to understand if these are intentional or if they can be changed without massively impacting people. https://github.com/maxking/docker-mailman/issues/550 * Issues with ALLOWED_HOSTS settings making assumptions about the environment and its inputs. We've worked around these by bind mounting in our own settings.py with these problems addressed, but it would be good to address them in case anyone else has run into this too. Details in these github issues: https://github.com/maxking/docker-mailman/issues/548 https://github.com/maxking/docker-mailman/issues/549 Ideally we'd avoid forking the images downstream and modifying them ourselves, but it seems the docker image repo is not getting a ton of attention recently. Totally understand that this may not be the biggest priority. We're happy to help address these by writing fixes and sending pull requests, but guidance would be appreciated before we head too far down that road. Once again thank you for the great documentation and images. They have already gotten us most of the way to production and the issues we've found are relatively minor. Clark

2 1

serving /static-content within /mailman3-web-Folder - change in recent mm release
by Stefan Bauer Sept. 30, 2022

Sept. 30, 2022

Hi Folks, during our migration to latest MM we noticed, that nowadays, the static content is not served from within mailmans base directory, but from outside. old MM3: domain.tld/mailman3/static/django-mailman3/js/main.js new MM3: domain.tld/static/django-mailman3/js/main.js Is there a chance to change it to the old behavior? We are running an additional nginx-proxy in front of mailman-server and dont want to forward /static, but only /mailman3. Thank you.

2 2

2 postfix instances and 1 mailman instance possible?
by charlie derr Sept. 29, 2022

Sept. 29, 2022

Greetings, We will be (temporarily) splitting our single postfix instance and running two separate instances on our email server. Can we configure mailman to listen to one of them and send to the other? If so, please do direct us towards how we would go about configuring mailman to do this. versions: mailman: 2.1.15-30.el7_9.2 postfix: 2.10.1-9.el7 (both via rh/centos repo(s)) thanks so very much for any assistance/direction you're able to provide, ~c -- Charlie Derr Director of Instructional Technology Bard College at Simon's Rock https://simons-rock.edu Encryption key: http://hope.simons-rock.edu/~cderr/ 413-528-7344 Pronouns: he/him/his

2 1

Re: Start thread with list-address instead of own
by Stefan Bauer Sept. 29, 2022

Sept. 29, 2022

Sorry found it. I was just too stupid. It is the anonymous list flag. sorry for the noise. Stefan

1 0

Start thread with list-address instead of own
by Stefan Bauer Sept. 29, 2022

Sept. 29, 2022

HI folks, latest mm3, when starting a new thread via mm3-webinterface -> Archives -> select List -> Start a new thread. It creates the thread with _my own_ personal address. How can i set the "sender" address as the list-address? IIRC with an older mm version, it had a different behavior. Any help is greatly appreciated. thank you. Stefan

1 0

what process creates webui tables (mailmanweb db)?
by tflatley＠gmail.com Sept. 27, 2022

Sept. 27, 2022

hello again, running a venv installation i think the tables in 2 databases (mailman/mailmanweb) were initially created by running mailman-web migrate - this wrapper is not available in a package install - so i think i need to run something like this after editing my settings.py file python3 manage.py migrate Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: No migrations to apply. Your models have changes that are not yet reflected in a migration, and so won't be applied. Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them. i do see tables in the mailman db but mailmanweb is empty - is there a different flag i need to run to seed the mailmanweb db? Thanks

2 5

Footer from templates not working - DB issue?
by chris＠mehl.one Sept. 27, 2022

Sept. 27, 2022

Hi, I am running Mailman3 on Debian 11 with Apache and MariaDB. Single installation. When I edit a footer from the WebUI templates, it doesn't show in the messages. Could it be an issue with the related DB? If so - what do I need to change? Many thanks in advance for any leads! Chris

4 5

collectstatic msg
by tflatley＠gmail.com Sept. 27, 2022

Sept. 27, 2022

Hello, in a venv install , after the database migration is complete i run the followign collectstatic compress compilemessages for a package install, i run the following ython3 manage.py collectstatic You have requested to collect static files at the destination location as specified in your settings: /var/lib/mailman3/web/static This will overwrite existing files! Are you sure you want to do this? Type 'yes' to continue, or 'no' to cancel: no CommandError: Collecting static files cancelled. on venv i did not get this msg - venv output 406 static files copied to /opt/mailman/web/static is it safe to overwrite these files? also before i run this do i need the mailman services down? thaniks

2 1

mailman-full question
by flatley Sept. 25, 2022

Sept. 25, 2022

Hello, i have successfully installed mailman3 with postgres using the venv method - testing the install of mailman-full package i have some questions - to configure the db in venv i would use mailman-web migrate - this works fine - but mailman-full install does not seem to include mailman-web or mailman3-web - the mailman info cmd works fine - do i need to also install mailman-web? i had thought the mailman-full included all components thanks

4 5

invalid parameter response of the rest-api
by Jacob Sievert Sept. 22, 2022

Sept. 22, 2022

Hello, Since a few days we get an error response from our automated membership script. We use the following code to control the membership for some lists: ``` def mailinglist_manage(list_address, members): """ make sure all 'members' are present on the list and no remove everyone else list_address : mail address of mailing list to manage addresses : mail address that are supposed to be on the list """ print("[*] update subscriptions for {}".format(list_address)) ml = mmc.get_list(list_address) # make sure we dont spam users ml.settings['send_welcome_message'] = False ml.settings.save() addresses = set(members.keys()) ml_members = ml.members ml_addresses = set((x.address.__str__() for x in ml_members)) for addr in ml_addresses - addresses: print("unsubscribe {} from {}".format(addr, list_address)) ml.unsubscribe(addr) for addr in addresses - ml_addresses: print("subscribe {} to {}".format(addr, list_address)) ml.subscribe(addr, members[addr], pre_verified=True, pre_confirmed=True, pre_approved=True) ``` Since Tuesday without any update performed by us we get the following error from the script when it's running: ``` Traceback (most recent call last): File "./mail_user_control.py", line 423, in <module> mailinglist_manage("XXX(a)EXAMPLE.COM", members) File "./mail_user_control.py", line 412, in mailinglist_manage pre_verified=True, pre_confirmed=True, pre_approved=True) File "/root/.local/lib/python3.6/site-packages/mailmanclient/restobjects/mailinglist.py", line 339, in subscribe response, content = self._connection.call('members', data) File "/root/.local/lib/python3.6/site-packages/mailmanclient/restbase/connection.py", line 112, in call error_msg, response, None) urllib.error.HTTPError: HTTP Error 400: Invalid Parameter "subscriber": . ``` If you have an idea why that code now returns this. I would be thankful. regards Jacob Sievert

4 7

Help understanding why some users don't receive emails
by Stephen Daniel Sept. 22, 2022

Sept. 22, 2022

Mailman3 people --- I'm a novice at running mailman, so any advice would be appreciated. I manage a few small lists using a mailman3 server. A few of my users complain they do not receive emails. Looking at one user in particular, I see in /var/log/syslog that postfix is sending the email. There is nothing in bounce.log. They are the only user who uses that particular email domain (embarqmail.com ). Is there anything I can do to debug why they do not get the emails? Or is this up to them and their email provider? Thanks! -- Steve Daniel

3 2

Hyperkitty displaying example.com
by Mark Dale Sept. 22, 2022

Sept. 22, 2022

Hi On a new installation I'm seeing "example.com" displayed at the top of the HyperKitty pages. I was expecting to see "lists.mydomainname.com", so I think I've missed something somewhere. Also, when a user signs up, the confirmation email reads as: ////////////////////////// SUBJECT: [example.com] Please Confirm Your E-mail Address FROM: postorius(a)lists.mydomainname.com BODY: Hello from example.com! You're receiving this e-mail because user yogibear has given your e- mail address to register an account on example.com. To confirm this is correct, go to https://lists.mydomainname.com/mailman3/accounts/confirm-email/NQ:1obAI3:Yw… Thank you for using example.com! example.com ////////////////////////// Any clues greatly appreciated. Thanks, Mark

2 2

Messages not being archived
by Mark Dale Sept. 20, 2022

Sept. 20, 2022

Hi I've just installed Mailman 3 using the Debian 11 package. Mailman-Version: 3.3.3 HyperKitty version 1.3.4 Postorius Version 1.3.4 The first list that I've added is receiving and sending mail okay, however the messages are not being archived. The logs report a HyperKitty error. I've copy-pasted that in at the end of this email. I've checked the following: ============================== /etc/mailman3/mailman.cfg contains: [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /etc/mailman3/mailman-hyperkitty.cfg ============================= The list has archiving configured on in Postorius. - Archive policy: Private archives - Active archivers: hyperkitty ============================= /etc/mailman3/mailman-hyperkitty.cfg has: [general] base_url: https://lists.mydomain.com/mailman3/archives #base_url: https://lists.mydomain.com/mailman3/hyperkitty/ api_key: aaaaaaaaaaaaaaaaaaaaaa ============================= /usr/share/mailman3-web/settings_local.py contains: ALLOWED_HOSTS = [ "localhost", '*' ] MAILMAN_ARCHIVER_KEY = 'aaaaaaaaaaaaaaaaaaaaaa' ============================= The headers of the emails received from the list show blanks for Archived-At and List-Archive: X-Mailman-Version: 3.3.3 Precedence: list Archived-At: <> List-Archive: <> ============================= /var/log/mailman3/mailman.log The errors in the log contain messages (that I'm clueless about) regarding HyperKitty. Sep 20 01:05:54 2022 (1293) HyperKitty failure on https://lists.mydomain.com/mailman3/archives/api/mailman/archive Sep 20 01:05:54 2022 (1293) Exception in the HyperKitty archiver: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> ... <title>503 Service Unavailable</title> ... Sep 20 01:05:54 2022 (1293) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message raise ValueError(result.text) ... ============================= If anyone can point me in the right direction to get the archive happening, that'd be grand. Cheers, Mark

1 1

How to delete non-users
by Allan Hansen Sept. 17, 2022

Sept. 17, 2022

Hi all, This is a bit of an emergency: I am getting a bunch of complaints from potential list members of my lists that they can't subscribe and they don't get messages. Apparently, the issue is that they are non-members. I have never created any non-members but looking at the docs it seems that if someone sends a message to the list, they automatically become non-members. For individuals I have been able to delete their non-membership and they then could subscribe properly. I have looked at some of my most popular lists and they have hundreds of non-members! It will take me an awful amount of time to remove each one manually, and not doing it - handling each as they complain - is also a lot of waste of time and cause of frustration for all involved. I have tried scripting it with delmember, but it does not take the '-r nonmember' option ('findmember' does!). Can anyone help me find out how to a. delete all non-members of all my lists b. prevent MM3 from creating new non-members in the future (so I don't have to keep removing them) Any help with this is appreciated. Yours, Allan I'm still at Mailman Core Version GNU Mailman 3.3.3 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0] My system used to be kept up to date by EMWD, but since Brian died have not been able to get it updated, and I'm too scared (from my attempts at installing MM3) to attempt it myself. If the above can only be solved via an update, I'd appreciate a referral.

3 10

Held message notifications ending up in junk
by Tibor Molnar Sept. 15, 2022

Sept. 15, 2022

Hi there, I wonder if anyone else if having this trouble that all the held message notifications are landing in junk folder. Regards, Tibor

4 5

Messages not going to held queue
by Mail Person Sept. 14, 2022

Sept. 14, 2022

Hi all, Not sure why, but messages set to be held for moderation are appearing to be discarded. I've tried creating a new test list, adjusting settings at the user and list level, but when a user sends a message that should be held for moderation, nothing happens. smtp.log shows the message is going through but it doesn't get to the moderation queue.

3 8

Message-Footer after migrating to Mailman3
by christopher.claus＠tgcamberg1848.de Sept. 13, 2022

Sept. 13, 2022

Hello together, I migrated a number of lists from mailman2 to mailman3 using the import functionality. Everthing works fine and the new lists are in use. Currently I´m using the maxking-docker-images with postorius: Mailman Core Version GNU Mailman 3.3.3 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.8.5 (default, Feb 19 2021, 09:27:16) [GCC 9.3.0] After this migration I started a refactoring with the list-styles specially with message-footers. Already the old lists in mailman2 were confused in some configuration details an I was clear to import this "misconfiguration" and clean it up afterwards. But this was much more difficult than expected: some lists are using a footer (from the mailman2-config) and there is no record in the template-section visible. Further I found no configuration item which points to this "old" footer. I found the file [code] /usr/lib/python3.8/site-packages/mailman/templates/de/list:member:generic:footer.txt [/code] which includes the old footer: [code] _______________________________________________ $display_name Mailingliste -- $listname Zur Abmeldung von dieser Mailingliste senden Sie eine Nachricht an ${short_listname}-leave@${domain} [/code] but no configuration item to disable this behaviour. I created a new template list:member:regular:footer for the list to override the footer. But the old footer is still used - in detail: the resulting message sent to all subcribers of the list contains only the footer and the content sent to the list is an attachement of that "footer-message". This is the basic reason why I want to change it. In the logfiles I found an error and a warning: [code] ERROR 2021-05-24 16:22:22,895 1648 django.security.DisallowedHost Invalid HTTP_HOST header: 'tgc_mailman_web:8000'. The domain name provided is not valid according to RFC 1034/1035. WARNING 2021-05-24 16:22:22,896 1648 django.request Bad Request: /postorius/api/templates/list/homepage.gruppe.tgcamberg1848.de/list:member:regular:footer [/code] Obviously I have a problem with the hostname. I set [code] POSTORIUS_TEMPLATE_BASE_URL=http://tgc_mailman_web:8000 [/code] where tgc_mailman_web is my container name. This URL ist stored in the DB-table "template" for the name=list:member:regular:footer. A call to my fqdn or to localhost [code] wget http://localhost:8000/postorius/api/templates/list/homepage.gruppe.tgcamber… [/code] will return the footer itself - this works fine. Therefore, should i set POSTORIUS_TEMPLATE_BASE_URL to http://localhost:8000? I think, resolving this issue will use the newly configured footer. But I started with the intention to remove alle footers due to the attachement situation described above. Does anybody have an idea how to change the configuration of my list? Are these problems probably related to the import? Currently we are using more then 25 lists with a lot of users. Manually recreating all lists is not possible an could only be a test for a single list. Best regards, chrclaus

6 18

"The content of this message was lost."
by skenny＠scss.tcd.ie Sept. 12, 2022

Sept. 12, 2022

I see that this issue has been discussed in a few other postings - it seems to be affecting us here at the moment. We're running Mailman 3.3.5 inside maxking's mailman-core/mailman-web Docker containers (version 0.4.3). This morning I composed a mail message and included two of our mailing lists in the To: field. On the first list I'm a member with address of the form my_addr_1(a)this.com. On the second I'm on it with a different address, my_addr_2(a)that.com. In the case of each list, Mailman held the message for moderation. As administrator, I accepted both. I then got the full message in my inbox at my_addr_1(a)this.com, but in my other inbox at my_addr_2(a)that.com, the body of the message was not present. Instead it read The content of this message was lost. It was probably cross-posted to multiple lists and previously handled on another list. I'm wondering what's the best thing to do here. Should I maybe downgrade to an earlier version of Mailman (i.e. an earlier version of maxking's Docker containers), pending resolution of this issue ...? Thanks for any advice. Stephen PS: The Mailman web interface "System Information" link reports: Mailman Core Version GNU Mailman 3.3.5 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.8.10 (default, May 6 2021, 06:30:44) [GCC 9.3.0]

2 2

How to set uWSGI buffer size in mailman3 with Dcoker
by bob B Sept. 8, 2022

Sept. 8, 2022

Running into an issue where users are getting a 502 bade gateway and we traced it down to the headers that are getting sent when they request web pages. This looks like our issue ********************* By default, uWSGI allocates a very small buffer (4096 bytes) for the headers of each request. If you start receiving “invalid request block size” in your logs, it could mean you need a bigger buffer. Increase it (up to 65535) with the buffer-size option. ********* So any idea on how to set this in mailman3 running in the maxking docker environment?

2 2

mailman3 not working for mailman21 lists
by blup＠fortytwo.ch Sept. 6, 2022

Sept. 6, 2022

I installed mailman3 on a server where mailman21 was installed before. Newly created mailinglists work fine. But if I create mailinglists with a name that was previously used on mailman21 nothing works (same behaviour with and without import of old configs and archives; no logs). I purged all old mailman21 config and data and also old postfix aliases (or at least I do think so). If I send a mail to old list list1(a)a.b and new list list2(a)a.b I get the following logs /var/log/mail.log Aug 21 22:17:40 basilisgg postfix/lmtp[1728]: ED2171120BF: to=<list2(a)c.a.b>, orig_to=<list2(a)a.b>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.31, delays=0.17/0.01/0/0.13, dsn=2.0.0, status=sent (250 Ok) Aug 21 22:17:40 basilisgg postfix/lmtp[1728]: ED2171120BF: to=<list1(a)c.a.b>, orig_to=<list1(a)a.b>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.31, delays=0.17/0.01/0/0.13, dsn=2.0.0, status=sent (250 Ok) /var/log/mailman3/smtp.log ug 21 22:17:40 2022 (934) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Aug 21 22:17:40 2022 (934) Peer: ('127.0.0.1', 44746) Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) handling connection Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'LHLO c.a.b' Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'MAIL FROM:<....>' Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) sender: .... Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'RCPT TO:<list2(a)c.a.b>' Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) recip: list2(a)c.a.b Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'RCPT TO:<list1(a)c.a.b>' Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) recip: list1(a)c.a.b Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'DATA' Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'QUIT' Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) connection lost Aug 21 22:17:40 2022 (934) Connection lost during _handle_client() Aug 21 22:17:46 2022 (936) <166111306097.933.1775779871266718007@...> smtp to list2(a)a.b for 1 recips, completed in 3.1437485218048096 seconds How can I get more info on why the mail for list1 isn't processed? Where could old mailman21 or postfix info on list1 be stored that causes mailman3 to not handle the list properly? How can I diff the config between list1 and list2 from the command line? Regards Diana

5 12

FYI: Django security releases issued: 4.0.6 and 3.2.14
by Guillermo Hernandez (Oldno7) Aug. 29, 2022

Aug. 29, 2022

https://www.djangoproject.com/weblog/2022/jul/04/security-releases/ Django security releases issued: 4.0.6 and 3.2.14 Posted by *Mariusz Felisiak* on Julio 4, 2022 In accordance with our security release policy <https://docs.djangoproject.com/en/dev/internals/security/>, the Django team is issuing Django 4.0.6 <https://docs.djangoproject.com/en/dev/releases/4.0.6/> and Django 3.2.14 <https://docs.djangoproject.com/en/dev/releases/3.2.14/>. These release addresses the security issue detailed below. We encourage all users of Django to upgrade as soon as possible. CVE-2022-34265: Potential SQL injection via Trunc(kind) and Extract(lookup_name) arguments Trunc() and Extract() database functions were subject to SQL injection if untrusted data was used as a kind/lookup_name value. Applications that constrain the lookup name and kind choice to a known safe list are unaffected. This security release mitigates the issue, but we have identified improvements to the Database API methods related to date extract and truncate that would be beneficial to add to Django 4.1 before it's final release. This will impact 3rd party database backends using Django 4.1 release candidate 1 or newer, until they are able to update to the API changes. We apologize for the inconvenience. Thanks Takuto Yoshikai (Aeye Security Lab) for the report. This issue has severity "high" according to the Django security policy. -- ___________________________________________ 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.

5 18

Migrated from MM2 to MM3, all is well except *one* list
by Scott Courtney Aug. 28, 2022

Aug. 28, 2022

Hello, all I have migrated a multi-list server from MM2 to MM3, on Debian 11, and migrated about half a dozen lists with fairly large archives. Absolutely everything has been working for a couple of months, but I am still unable to get one specific list to send mail to its subscribers. Of course, the first place I started was the logs, but that's the problem -- even with logging turned up, it appears to be failing silently as it connects to the MTA. Here's a summary of the environment: OS: Debian Linux 11, 64-bit, on a virtual machine MTA: Exim 4.94.2 List server: Mailman 3.3.3 (installed from Debian repo) Database: MariaDB 10.5.15 All daemons are running on the same host, and communication is either UNIX socket or loopback network interface, for security. Web server: Apache 2.4.53, with proxy to WSGI per the MM3 setup guide Symptom: There are six lists on the server. All six can accept inbound traffic and will post the messages to the (always private, in this environment) archives. The web interface is working perfectly. Five of the lists also can send out messages to subscribers, but the sixth list cannot send traffic to the MTA, or is not attempting to do so. Tests run so far (all resulting in successful posting to archives, but no outbound mail): * Originate mail from inbound SMTP to the list address. * Originate mail from the web UI as a member/moderator. * Originate mail from the web UI as the site admin (also the list owner). * Originate mail from both inbound SMTP and web UI by multiple users. Log data for the inbound traffic (typical test message, some data redacted): 2022-08-27 15:11:57 1oS1Dn-003AWH-Hz <= REDACTED H=REDACTED:25 P=esmtps X=TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_128_GCM:128 CV=no K S=2552 DKIM=REDACTED id=REDACTED T="TEST 8.27.001" 2022-08-27 15:11:57 1oS1Dn-003AWH-Hz => MY_LIST(a)lists.MY_DOMAIN R=mailman_main_director T=mailman3_transport H=127.0.0.1 [127.0.0.1] I=[127.0.0.1] C="250 Ok" 2022-08-27 15:11:57 1oS1Dn-003AWH-Hz Completed Log data for MM3 smtp.log (again, partially redacted): Aug 27 15:11:57 2022 (690182) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Aug 27 15:11:57 2022 (690182) Peer: ('127.0.0.1', 48170) Aug 27 15:11:57 2022 (690182) ('127.0.0.1', 48170) handling connection Aug 27 15:11:57 2022 (690182) ('127.0.0.1', 48170) Data: b'LHLO REDACTED' Aug 27 15:11:57 2022 (690182) ('127.0.0.1', 48170) Data: b'MAIL FROM:<REDACTED>' Aug 27 15:11:57 2022 (690182) ('127.0.0.1', 48170) sender: REDACTED Aug 27 15:11:57 2022 (690182) ('127.0.0.1', 48170) Data: b'RCPT TO:<erevnite(a)lists.4th.com>' Aug 27 15:11:57 2022 (690182) ('127.0.0.1', 48170) recip: MY_LIST(a)lists.MY_DOMAIN Aug 27 15:11:57 2022 (690182) ('127.0.0.1', 48170) Data: b'DATA' Aug 27 15:11:57 2022 (690182) ('127.0.0.1', 48170) Data: b'QUIT' Aug 27 15:11:57 2022 (690182) ('127.0.0.1', 48170) connection lost Aug 27 15:11:57 2022 (690182) Connection lost during _handle_client() Originally I thought the "connection lost" indicated a failure, but that is happening for all the lists, and also on successful traffic. Since it occurs after the QUIT command in the SMTP session, and based on some online searching, my current understanding is that this is harmless and simply indicates the MTA closed the socket after the QUIT. (Please correct me if that is wrong.) Log data for mailman.log, with partial redaction: Aug 27 15:11:57 2022 (690181) ACCEPT: <REDACTED> Aug 27 15:11:59 2022 (690178) HyperKitty archived message <REDACTED> to https://lists.MY_DOMAIN/hyperkitty/list/MY_LIST@lists.MY_DOMAIN/message/G3D… 19:11:59 [Q] INFO Enqueued 518 19:11:59 [Q] INFO Enqueued 519 19:11:59 [Q] INFO Enqueued 520 19:11:59 [Q] INFO Enqueued 521 19:11:59 [Q] INFO Enqueued 522 19:11:59 [Q] INFO Enqueued 523 19:11:59 [Q] INFO Enqueued 524 INFO 2022-08-27 19:11:59,648 690164 hyperkitty.views.mailman Archived message <REDACTED> to https://lists.MY_DOMAIN/hyperkitty/list/MY_LIST@lists.MY_DOMAIN/message/G3D… [pid: 690164|app: 0|req: 4688541/4688541] 2600:3c04::f03c:91ff:fe02:9cc1 () {64 vars in 1255 bytes} [Sat Aug 27 19:11:59 2022] POST /hyperkitty/api/mailman/archive?key=xombsjgLDqe6d1oxvBaQWH4ZT81uCEjH => generated 113 bytes in 110 msecs (HTTP/1.1 200) 5 headers in 160 bytes (1 switches on core 0) 19:12:00 [Q] INFO Process-1:4 processing [update_from_mailman] 19:12:00 [Q] INFO Process-1:3 processing [sender_mailman_id] 19:12:00 [Q] INFO Process-1:2 processing [rebuild_thread_cache_new_email] 19:12:00 [Q] INFO Process-1:1 processing [compute_thread_positions] 19:12:00 [Q] INFO Processed [rebuild_thread_cache_new_email] 19:12:00 [Q] INFO Process-1:2 processing [rebuild_mailinglist_cache_recent] 19:12:00 [Q] INFO Processed [sender_mailman_id] 19:12:00 [Q] INFO Process-1:3 processing [rebuild_mailinglist_cache_for_month] 19:12:00 [Q] INFO Process-1:1 processing [check_orphans] 19:12:00 [Q] INFO Processed [compute_thread_positions] 19:12:00 [Q] INFO Processed [rebuild_mailinglist_cache_for_month] 19:12:00 [Q] INFO Processed [check_orphans] 19:12:00 [Q] INFO Processed [rebuild_mailinglist_cache_recent] 19:12:00 [Q] INFO Processed [update_from_mailman] [pid: 690164|app: 0|req: 4693691/4693691] 184.94.240.88 () {60 vars in 929 bytes} [Sat Aug 27 19:21:50 2022] HEAD / => generated 0 bytes in 2 msecs (HTTP/1.1 301) 6 headers in 204 bytes (1 switches on core 0) [pid: 690164|app: 0|req: 4693694/4693694] 184.94.240.88 () {60 vars in 1009 bytes} [Sat Aug 27 19:21:50 2022] HEAD /postorius/lists/ => generated 7136 bytes in 142 msecs (HTTP/1.1 200) 5 headers in 163 bytes (1 switches on core 1) There is nothing at all in the Exim log indicating an outbound transaction was attempted by Mailman. I know Exim and Mailman are communicating because all the lists use the same SMTP configuration for Exim and Mailman (i.e., the non-working list is not in any way exceptional). I've done a lot of searching online to find a solution, and I did see that a couple of others had asked about this type of problem, but the only one I found that got a response had an issue that didn't apply in my small environment. Absent any other ideas, I'm going to try inserting some trace logging into the Python code, but I can't figure out what's wrong here. I've even gone to the point of looking at the SQL rows to verify this list is exactly parallel to another working list, except its name and integer ID numbers for various unique auto-increment keys. Any suggestions are appreciated. Thanks!

2 2

Using REST with CLI using curl .... help needed
by Krešimir Mihalj Aug. 27, 2022

Aug. 27, 2022

Hi ! I need simple add/delete member to list using rest ..... but all documentation is for python and not helpfull for me, .... and I need these in CLI using curl command .... To add member using CLI i tried this command: curl -d "{'list_id' : 'list.domain.com', 'subscriber' : 'user(a)email.com'}" -H 'Content-Type: application/json' --user restadmin:restpass http://localhost:8001/3.0/members and I got this response: Missing parameters: list_id, subscriber What is wrong in above command here ? ..... I need to add user: user(a)email.com to list: list(a)domain.com Also, if someone is willing to give example: delete user: user(a)email.com from list: list(a)domain.com I actually create PHP application .... but CLI example is easy to reproduce in PHP function AddUserToList($user,$lista) { $url = 'http://llocalhost:8001/3.0'; $request_url = $url . '/members'; $data = array("list_id" => $lista,"subscriber" => $user ); $postdata = json_encode($data); $ch = curl_init($request_url); curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); curl_setopt($ch, CURLOPT_USERPWD, "restadmin:restpass"); curl_setopt($ch, CURLOPT_POST, 1); curl_setopt($ch, CURLOPT_POSTFIELDS, $postdata); curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1); curl_setopt($ch, CURLOPT_FOLLOWLOCATION, 1); curl_setopt($ch, CURLOPT_HTTPHEADER, array('Content-Type: application/json')); $result = curl_exec($ch); curl_close($ch); print_r ($result); } AddUserToList('user(a)email.com','list.domain.com');

6 8

DKIM header not added to subscribe/unsubscribe notification email
by Philip Colmer Aug. 24, 2022

Aug. 24, 2022

I have a Mailman 3 server set up with OpenDKIM and Postfix. Each of the lists has been configured so that the DMARC mitigation is "Replace From: with list address" and DMARC Mitigate unconditionally is selected. Everything seems to be working fine *except* when the system sends a notification email to the list owners of someone subscribing or unsubscribing. *Those* emails do not have the DKIM header added and are getting trapped by anti-spam systems as a result. Any suggestions as to why this might be, please? I cannot see anything in the configuration for OpenDKIM or Postfix that might allow just those messages to go out unsigned. In case it is relevant/important, this system is running: mailman 3.3.5 mailman-hyperkitty 1.2.0 mailman-web 0.0.5 mailmanclient 3.3.3 Thank you. Regards Philip

2 2

MM3 not starting
by max.diener＠hpi.de Aug. 22, 2022

Aug. 22, 2022

Hi, i am trying to install MM3 and had a few issues with it. First i was trying the Mailman3-full package for Debian which didnt work good for me. There was missing paths and files, after some research i found out it may not be well maintained right now. I was working to fix the issue i come up with but had no luck with it. After that i was trying this Howto: https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 the Installation worked in some aspect. i had a running mailman3 service but the webinterfaces was not working. After some searching i found a issue that was stating that the current release had a bug in it wich made it not working. For instance was the config file different for "systemctl start mailman3" then when i was checking it "mailman info" and some paths was not like in the instructions again, this time i added the folders and put the files needed for it in to it but could not make it work. i kept digging and find out for prod it is best practice to install in a virtual environment so i waited for the bug to fix and took this Installation Instructions: https://docs.list.org/en/latest/install/virtualenv.html#virtualenv-install i was a little bit confused that there seems to be two spots from the official site where you can find Installation Instructions: https://wiki.list.org/DOC/ and https://docs.list.org/ since the last one made it seem like it was newer i choose the venv installation instructions. From the install instructions at https://docs.list.org/en/latest/install/virtualenv.html#virtualenv-install i was seeing that there is also some folders not showing up like mentioned in the howto: /op/mailman/mm was not there. In the part where you configure mailman core it says you need to add the /etc/mailman/mailman.cfg file it shows that the path is used for the hyperkitty config as well as it is the path vor the "var_dir: /opt/mailman/mm/var". i added the paths and at the point in the install instructions here https://docs.list.org/en/latest/install/virtualenv.html#starting-mailman-au… i checked if i can start mailman3 now but still fail to do so. when i check "journalctl -xe" i find the following information but cant get more information on how to fix it in the net with it: Aug 22 09:54:05 mailman3test mailman[55134]: Starting Mailman's master runner Aug 22 09:54:05 mailman3test mailman[55134]: Generating MTA alias maps Aug 22 09:54:05 mailman3test systemd[1]: mailman3.service: Can't open PID file /opt/mailman/mm/var/master.pid (yet?) after start: Operation not permitted Aug 22 09:54:12 mailman3test mailman[55146]: Traceback (most recent call last): Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/bin/runner", line 8, in <module> Aug 22 09:54:12 mailman3test mailman[55146]: sys.exit(main()) Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/click/core.py", line 1130, in __call__ Aug 22 09:54:12 mailman3test mailman[55146]: return self.main(*args, **kwargs) Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/click/core.py", line 1055, in main Aug 22 09:54:12 mailman3test mailman[55146]: rv = self.invoke(ctx) Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/click/core.py", line 1404, in invoke Aug 22 09:54:12 mailman3test mailman[55146]: return ctx.invoke(self.callback, **ctx.params) Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/click/core.py", line 760, in invoke Aug 22 09:54:12 mailman3test mailman[55146]: return __callback(*args, **kwargs) Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/click/decorators.py", line 26, in new_func Aug 22 09:54:12 mailman3test mailman[55146]: return f(get_current_context(), *args, **kwargs) Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/mailman/bin/runner.py", line 188, in main Aug 22 09:54:12 mailman3test mailman[55146]: runner.run() Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/mailman/runners/lmtp.py", line 255, in run Aug 22 09:54:12 mailman3test mailman[55146]: self.lmtp.start() Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/aiosmtpd/controller.py", line 210, in start Aug 22 09:54:12 mailman3test mailman[55146]: raise self._thread_exception Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/aiosmtpd/controller.py", line 176, in _run Aug 22 09:54:12 mailman3test mailman[55146]: srv: AsyncServer = self.loop.run_until_complete(self.server_coro) Aug 22 09:54:12 mailman3test mailman[55146]: File "/usr/lib/python3.9/asyncio/base_events.py", line 642, in run_until_complete Aug 22 09:54:12 mailman3test mailman[55146]: return future.result() Aug 22 09:54:12 mailman3test mailman[55146]: File "/usr/lib/python3.9/asyncio/base_events.py", line 1460, in create_server Aug 22 09:54:12 mailman3test mailman[55146]: infos = await tasks.gather(*fs, loop=self) Aug 22 09:54:12 mailman3test mailman[55146]: File "/usr/lib/python3.9/asyncio/base_events.py", line 1400, in _create_server_getaddrinfo Aug 22 09:54:12 mailman3test mailman[55146]: infos = await self._ensure_resolved((host, port), family=family, Aug 22 09:54:12 mailman3test mailman[55146]: File "/usr/lib/python3.9/asyncio/base_events.py", line 1396, in _ensure_resolved Aug 22 09:54:12 mailman3test mailman[55146]: return await loop.getaddrinfo(host, port, family=family, type=type, Aug 22 09:54:12 mailman3test mailman[55146]: File "/usr/lib/python3.9/asyncio/base_events.py", line 856, in getaddrinfo Aug 22 09:54:12 mailman3test mailman[55146]: return await self.run_in_executor( Aug 22 09:54:12 mailman3test mailman[55146]: File "/usr/lib/python3.9/concurrent/futures/thread.py", line 52, in run Aug 22 09:54:12 mailman3test mailman[55146]: result = self.fn(*self.args, **self.kwargs) Aug 22 09:54:12 mailman3test mailman[55146]: File "/usr/lib/python3.9/socket.py", line 953, in getaddrinfo Aug 22 09:54:12 mailman3test mailman[55146]: for res in _socket.getaddrinfo(host, port, family, type, proto, flags): Aug 22 09:54:12 mailman3test mailman[55146]: socket.gaierror: [Errno -2] Name or service not known Aug 22 09:55:01 mailman3test CRON[55176]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Aug 22 09:55:01 mailman3test CRON[55177]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Aug 22 09:55:01 mailman3test CRON[55176]: pam_unix(cron:session): session closed for user root Aug 22 09:55:34 mailman3test systemd[1]: mailman3.service: start operation timed out. Terminating. Aug 22 09:55:35 mailman3test systemd[1]: mailman3.service: Failed with result 'timeout'. Anybody knows whats going on and what i am doing wrong?

2 1

MM21 -> MM3 Migration: Importing archives hitting a snag
by Odhiambo Washington Aug. 17, 2022

Aug. 17, 2022

With mailman installed using virtualenv /opt/mailman/mm/venv: I am trying to import list archives after importing the configs. python manage.py hyperkitty_import -l listname(a)site.name /var/list/archives/private/listname.mbox/listname.mbox python: can't open file '/opt/mailman/manage.py': [Errno 2] No such file or directory Where is manage.py PATH? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

1 1

List Migration from MM2.1 -> MM3
by Odhiambo Washington Aug. 15, 2022

Aug. 15, 2022

So I thought I have everything running. Fresh install of MM3 on Ubuntu-22.04. I have created a list in postorius - it has the same name as my old list in MM2. [image: MM3.png] Now, following - https://docs.mailman3.org/en/latest/migration.html - I change user to mailman so as to run the migration. mailman@lists:~$ pwd /opt/mailman mailman@lists:~$ id uid=1003(mailman) gid=1002(mailman) groups=1002(mailman),4(adm),38(list) mailman@lists:~$ */opt/mailman/mm/venv/bin/mailman import21 skunkworks(a)lists.my.co.ke <skunkworks(a)lists.my.co.ke> /var/list/lists/skunkworks/config.pck *# running without specifying the absolute path is not working! Usage: mailman import21 [OPTIONS] LISTSPEC PICKLE_FILE Try 'mailman import21 -h' for help. Error: No such list: skunkworks(a)lists.my.co.ke mailman@lists:~$ ls -al /var/list/lists/skunkworks/config.pck -rw-rw---- 1 root list 63765 Aug 14 11:10 /var/list/lists/skunkworks/config.pck mailman@lists:~$ exim -bt skunkworks(a)lists.my.co.ke skunkworks(a)lists.my.co.ke router = mailman3_router, transport = mailman3_transport mailman@lists:~$ What am I missing? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: MM3.png Replaced multipart/alternative part with first alternative.

2 8

Gunicorn problem?
by Odhiambo Washington Aug. 14, 2022

Aug. 14, 2022

Ubuntu 22.04, Mailman3. I am having two problems with the installation of MM3. This has been installed today by referring to https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 1. The following error while trying to access https://my.site.address/mailman3 root@lists:/opt/mailman/mm/var/logs# less error.log Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 47, in inner File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/utils/deprecation.py", line 117, in __call__ File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 49, in inner response = get_exception_response(request, get_resolver(get_urlconf()), 403, exc) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 114, in response_for_exception File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 153, in handle_uncaught_exception File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/utils/decorators.py", line 130, in _wrapped_view response = view_func(request, *args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/views/defaults.py", line 97, in server_error return HttpResponseServerError(template.render()) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/template/backends/django.py", line 61, in render return self.template.render(context) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/template/base.py", line 170, in render context.template_name = self.name File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/template/base.py", line 162, in _render def _render(self, context): File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/template/base.py", line 938, in render bit = node File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/template/base.py", line 905, in render_annotated if context.template.engine.debug and not hasattr(e, 'template_debug'): File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/templatetags/static.py", line 106, in render url = self.url(context) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/templatetags/static.py", line 103, in url return self.handle_simple(path) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/templatetags/static.py", line 117, in handle_simple from django.contrib.staticfiles.storage import staticfiles_storage File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/contrib/staticfiles/storage.py", line 17, in <module> from django.utils.deprecation import RemovedInDjango31Warning ImportError: cannot import name 'RemovedInDjango31Warning' from 'django.utils.deprecation' (/opt/mailman/mm/venv/lib/python3.10/site-packages/django/utils/deprecation.py) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.10/site-packages/gunicorn/workers/sync.py", line 136, in handle self.handle_request(listener, req, client, addr) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/gunicorn/workers/sync.py", line 179, in handle_request respiter = self.wsgi(environ, resp.start_response) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/core/handlers/wsgi.py", line 133, in __call__ response = self.get_response(request) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/core/handlers/base.py", line 130, in get_response # response middleware and then render the response File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 49, in inner response = get_exception_response(request, get_resolver(get_urlconf()), 403, exc) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 114, in response_for_exception File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 153, in handle_uncaught_exception File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/utils/decorators.py", line 130, in _wrapped_view response = view_func(request, *args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/views/defaults.py", line 97, in server_error return HttpResponseServerError(template.render()) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/template/backends/django.py", line 61, in render return self.template.render(context) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/template/base.py", line 170, in render context.template_name = self.name File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/template/base.py", line 162, in _render def _render(self, context): File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/template/base.py", line 938, in render bit = node File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/template/base.py", line 905, in render_annotated if context.template.engine.debug and not hasattr(e, 'template_debug'): File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/templatetags/static.py", line 106, in render url = self.url(context) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/templatetags/static.py", line 103, in url return self.handle_simple(path) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/templatetags/static.py", line 117, in handle_simple from django.contrib.staticfiles.storage import staticfiles_storage File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/contrib/staticfiles/storage.py", line 17, in <module> from django.utils.deprecation import RemovedInDjango31Warning ImportError: cannot import name 'RemovedInDjango31Warning' from 'django.utils.deprecation' (/opt/mailman/mm/venv/lib/python3.10/site-packages/django/utils/deprecation.py) 2. I am a little lost on how one installation instance can be used to handle TWO different domains - domain1 and domain2, both using SSL. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 2

Cannot connect to SMTP server
by mkummini＠cmi.ac.in Aug. 14, 2022

Aug. 14, 2022

Hello. I am setting up a new mailman3 server (debian 11). `mailman3-full` is installed on the same server as postfix (our MTA). There is just one test mailing list now. When I send a message to it (I am a subscriber), mailman3 accepts the message through LMTP. Both the postfix log and mailman.log confirm this. Postfix log: Aug 14 03:21:25 mail postfix/lmtp[4097036]: 44E49272437D: to=<testlist(a)cmi.ac.in>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.15, delays=0.02/0.03/0.01/0.09, dsn=2.0.0, status=sent (250 Ok) mailman.log: Aug 14 03:21:26 2022 (4096856) ACCEPT: <Yvgc3WsoFlpZbypw(a)cmi.ac.in> (The digest.mmdf file shows the test message I sent. Hence mailman3 has received the message from postfix.) However, after this, the postfix log does not show any attempt by mailman3 to send the message to the list members. The following runners have started (after the most recent mailman3 restart) Aug 14 03:19:53 2022 (4096853) archive runner started. Aug 14 03:19:53 2022 (4096863) retry runner started. Aug 14 03:19:53 2022 (4096862) rest runner started. Aug 14 03:19:54 2022 (4096855) command runner started. Aug 14 03:19:54 2022 (4096854) bounces runner started. Aug 14 03:19:55 2022 (4096860) pipeline runner started. Aug 14 03:19:55 2022 (4096866) digest runner started. Aug 14 03:19:55 2022 (4096858) nntp runner started. Aug 14 03:19:55 2022 (4096857) lmtp runner started. Aug 14 03:19:55 2022 (4096865) virgin runner started. Aug 14 03:19:56 2022 (4096856) in runner started. Aug 14 03:19:57 2022 (4096859) out runner started. However, I get the following line each time I do a restart Aug 14 03:19:57 2022 (4096859) Cannot connect to SMTP server localhost on port 587 I tried to specify the name of the postfix server, though it runs on the same machine as mailman3, and the different ports : 25, 465 and 587; they all raise the same error. Following <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/runners/do…>, I tried to create an outgoing test runner, but that resulted in the following errors. >>> from mailman.runners.outgoing import OutgoingRunner >>> from mailman.testing.helpers import make_testable_runner >>> outgoing = make_testable_runner(OutgoingRunner, 'out') Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/python3/dist-packages/mailman/testing/helpers.py", line 92, in make_testable_runner return EmptyingRunner(name) File "/usr/lib/python3/dist-packages/mailman/testing/helpers.py", line 79, in __init__ super().__init__(*args, **kws) File "/usr/lib/python3/dist-packages/mailman/runners/outgoing.py", line 53, in __init__ super().__init__(slice, numslices) File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 63, in __init__ section = getattr(config, 'runner.' + name) File "/usr/lib/python3/dist-packages/mailman/config/config.py", line 123, in __getattr__ return getattr(self._config, name) AttributeError: 'NoneType' object has no attribute 'runner.out' Here are the lines in mailman.cfg referring to smtp smtp_secure_mode : starttls smtp_host: localhost smtp_port: 587 If you could suggest how I could fix this issue, it would be great. Thank you. Manoj.

2 3

RE in Ban List
by Peter Chubb Aug. 12, 2022

Aug. 12, 2022

Hi I tried to add the regular expression sales@.* to the ban list for one of my lists and got: An error occurred: Invalid Parameter "email": Expected a valid email address or regular expression, got sales@.*. Now, 'sales@.*' _is_ a valid regular expression --- so why did it fail? (I wanted to ban that set of addresses, because we get an awful lot of chinese spam from sales@some-company-name where the company name is variable) Peter C

2 1

MM3 not processing some mails from specific user
by Stefan Bauer Aug. 12, 2022

Aug. 12, 2022

Hi, we are running MM3¹ and from time to time, a mail to a mailing list is not processed by MM. MM sees the mail but still does nothing with it. If another user is sending _same_ mail, it is processed. Any idea what that could be? Here are some logs: Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) handling connection Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) Data: b'LHLO mal01.mydomain.tld' Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) Data: b'MAIL FROM:<john.doe(a)mydomain.tld>' Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) sender: john.doe(a)mydomain.tld Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) Data: b'RCPT TO:<ssa(a)mydomain.tld>' Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) recip: ssa(a)mydomain.tld Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) Data: b'DATA' Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) Data: b'QUIT' Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) connection lost Here is a snipped from same user, but different mail that is also not processed by MM: Subject: =?iso-8859-1?Q?Kleine_=C4nderung?= From: john.doe(a)mydomain.tld To: =?us-ascii?Q?ssa=40mydomain=2Etld?= <ssa(a)mydomain.tld> Date: Wed, 10 Aug 2022 12:33:36 +0000 Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=_m+9Z-w1zPVUy50id4xiOsxEs50Bl3xTDSq7AWqqonRf21H5c" Thread-Index: AdistWce8WLKbSqIReeBnR+y5yR5Mw== Message-Id: <kcEE.3C4Toxi/SomLpNH7qUNdhg.gBB2y7Ws2AE(a)mx1.mydomain.tld> This is a multi-part message in MIME format. Your mail reader does not understand MIME message format. --=_m+9Z-w1zPVUy50id4xiOsxEs50Bl3xTDSq7AWqqonRf21H5c Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Das ist ein Test --=_m+9Z-w1zPVUy50id4xiOsxEs50Bl3xTDSq7AWqqonRf21H5c-- Any help is greatly appreciated. Thank you. ¹ 3.1.1-9 (update is scheduled)

3 5

Getting information to connect mailman to new web host
by tg337＠drexel.edu Aug. 11, 2022

Aug. 11, 2022

We moved over to a new platform and now our lists.(domain).org address is not working. I'm trying to find the records I would need to update on the new site to connect them, and not sure how.

2 1

Mailman recovery test did not go as planned
by bob B Aug. 9, 2022

Aug. 9, 2022

I have a test Mailman 3 environment. We are using docker, and we are running the database outside of docker in mysql. I need to perform a DR recovery test. I shut down Mailman in docker (mailman-core & mailman-web, the only docker images I have running for Mailman). While Mailman was stopped, I had our database team take a backup dump of the database. I then restarted Mailman in docker. I threw some more messages at a test list. I validated that the new messages were delivered, and showed up in the archive. I shut down Mailman again. I had the database team restore the Mailman database from the backup. I started Mailman I logged into Mailman I was expecting to see the messages in the archive prior to the backup and all the messages after the backup would be gone. When went into the list archive, I get a spinning icon and no messages showed up. I quit, restarted my browser, and logged in again, and the same thing. I then sent a test message to the list and the message was delivered to the list. Then when I went to check the archive, the spinning icon was gone and that test message was there along with all the messages before the backup was taken. Is this normal? After a restore did the new message cause a refresh of archived messages etc? Is there a way to do this without sending a message to a list after a restoration of the database? Are there better steps I should take when restoring the database? Thanks

3 6

Detectors and Bounces
by summersan＠nclack.k12.or.us Aug. 5, 2022

Aug. 5, 2022

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

2 9

Rpsamd greylist configuration for Mailman3
by Prasanth Nair Aug. 3, 2022

Aug. 3, 2022

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

2 2

Mailman 3 questions (purge archives, list metrics, and auto discard held messages)
by bob B Aug. 2, 2022

Aug. 2, 2022

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

3 4

Mailman 3 Consultant needed
by Mark Taylor Aug. 1, 2022

Aug. 1, 2022

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

1 0

Programmatic Creation of Users
by jciesla＠techsupportme.com July 30, 2022

July 30, 2022

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

2 1

User display name entry field input ignored
by Christian July 27, 2022

July 27, 2022

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

2 3

Shorted Subjects in Mailman
by Stephan Krinetzki July 27, 2022

July 27, 2022

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

4 13

Problem replying via Hyperkitty
by Jeff July 27, 2022

July 27, 2022

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

2 3

Apache Configuration for Subdomain
by Mail Person July 26, 2022

July 26, 2022

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

3 9

Apache Conf
by Guiseppin Thomas July 26, 2022

July 26, 2022

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

5 10

Error while running mailman-web compilemessages
by Prasanth Nair July 26, 2022

July 26, 2022

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

4 7

List and Domain listing slow
by Patrik Peng July 25, 2022

July 25, 2022

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

1 0

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

July 22, 2022

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

3 6

Messages Showing Up as "Forwarded"
by Mail Person July 22, 2022

July 22, 2022

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

2 1

Can't Start Mailman3 Core on Fresh Install
by Mail Person July 21, 2022

July 21, 2022

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

4 7

check/update delivery status via python script
by Eggert Ehmke July 19, 2022

July 19, 2022

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

2 2

Hacking attempts?
by Lists July 17, 2022

July 17, 2022

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

7 19

Messages attached to probe messages
by Bjoern Franke July 15, 2022

July 15, 2022

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

3 6

Adding user - Error 409 Subscription request already pending
by kevin＠coastalaska.org July 14, 2022

July 14, 2022

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

5 17

message size
by ronald.clarke＠sydney.edu.au July 12, 2022

July 12, 2022

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

3 2

message size
by Ronald Clarke July 12, 2022

July 12, 2022

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

1 0

mailman 3.x upgrade and downgrade
by skooperit＠gmail.com July 12, 2022

July 12, 2022

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

3 4

Mailman 3 stops delivering to a domain after too many bounces
by Julian Kippels July 12, 2022

July 12, 2022

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

4 7

Notes about successfuly upgrade from python 3.7 to 3.9
by Guillermo Hernandez (Oldno7) July 12, 2022

July 12, 2022

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

2 2

Walk-thru for Ubuntu Bionic Mailman 3 Full setup
by kelly.close＠lrewater.com July 9, 2022

July 9, 2022

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

6 21

Sorry to repeat a question, but how do I permanently delete messages, again?
by William Oliver July 8, 2022

July 8, 2022

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

2 2

Problem migrating from Ubuntu packaged Mailman to Virtualenv, including Hyperkitty
by tim＠thecutts.org July 7, 2022

July 7, 2022

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

3 2

Problem with database change sqlite -> mysql
by moritz both July 7, 2022

July 7, 2022

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

3 5

Django errors after deleting a thread
by peter＠chubb.wattle.id.au July 6, 2022

July 6, 2022

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

3 4

mailman3 suddenly stopped working after routine package upgrade with "apt update" and "apt upgrade".
by gordon＠dickens.com July 5, 2022

July 5, 2022

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

2 2

Monthly mailman-web job using a lot of memory
by Andy Smith July 4, 2022

July 4, 2022

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

3 7

mailman3 + postfix + dovecot + postfixadmin
by Geoff Nordli July 3, 2022

July 3, 2022

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

2 2

Emails about moderation are sent to list owners, want them sent to moderators instead
by Elias Rudberg July 2, 2022

July 2, 2022

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

2 1

uwsgi memory usage
by peter＠chubb.wattle.id.au June 29, 2022

June 29, 2022

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

4 4

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

June 29, 2022

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

1 1

Run 'manage.py makemigrations' to make new migrations
by christopher.claus＠tgcamberg1848.de June 29, 2022

June 29, 2022

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

3 3

docker setup
by epi＠epinux.com June 28, 2022

June 28, 2022

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

3 5

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

June 27, 2022

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

5 13

Excluding archives from a mailman3web database backup
by Andy Smith June 24, 2022

June 24, 2022

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

2 2

How can I clear "Subscription request already pending" status ?
by Axel Rau June 24, 2022

June 24, 2022

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

3 2

Docker images with Hyper kitty 1.1.0
by bob B June 23, 2022

June 23, 2022

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

3 3

I'm new to mailman
by LIULIANG June 23, 2022

June 23, 2022

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

1 0

Mails sent by mailman-web runjobs hourly
by Eggert Ehmke June 17, 2022

June 17, 2022

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

4 3

Removing the option to delete a list on the Postorious interface
by Wong, Wesley June 14, 2022

June 14, 2022

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

2 1

How to configure mailman3-web
by robert.winkler＠bioprocess.org June 14, 2022

June 14, 2022

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

2 1

Mailman3 Setup
by George R. Kasica June 11, 2022

June 11, 2022

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

4 6

Turned on archiving and it is not working
by bob B June 9, 2022

June 9, 2022

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

2 4

Validity of membership opt-in
by Julian Kippels June 8, 2022

June 8, 2022

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

2 1

Include receipant address as a variable
by chucka＠blackforest-co.com June 7, 2022

June 7, 2022

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

2 7

Remove old bounces in bouncedir
by Stephan Krinetzki June 7, 2022

June 7, 2022

Hello all, our Mailman3 has over 7GB of bounces in its bouncedir. I noticed that some messages there are already over 3 years old. Now my question: Is there a way to remove the old bounces?

2 6

WebFrontend language not working
by c.buhtz＠posteo.jp June 6, 2022

June 6, 2022

Hello, I am using mailman3 as list owner on python.org. The web-frontend shows me everything in "German" which is my native language (in OS, Browser, GeoIP). But I want it in English. in my "Global Mailman-Settings" the "Preferred Language ( "Bevorzugte Sprache" ) is set to "English (USA)". But it seems to me that this doesn't affect the WebFront end. How can set the WebFront end to English? Kind Christian

3 5

Migrating from mailman-suite to mailman-web
by Andrew Hodgson June 4, 2022

June 4, 2022

Hi. Any pointers in migrating from Mailman-suite to Mailman-web? I'm interested specifically in configuration changes required to Gunicorn in order to bring up the Django project using Mailman-web. Thanks. Andrew.

2 1

Lost in default style creation
by kenneth.karlsson＠eco.cept.org June 2, 2022

June 2, 2022

Hi all I have installed a brandnew server - ubuntu 21.10, mailman3 version 3.3.3 (Tom Sawyer) I want to set some default settings to all new lists, as we are creating them through API from another system, i do this (snipped straight from the shell) : >>> from mailman.interfaces.styles import IStyleManager >>> manager = getUtility(IStyleManager) >>> from zope.interface import implementer >>> from mailman.interfaces.styles import IStyle >>> @implementer(IStyle) ... class EcoStyle: ... name = 'ECOstyle' ... description = 'ECO mailing list style.' ... def apply(self, ml): ... ml.dmarc_mitigate_action = 'munge_from' ... ml.dmarc_mitigate_unconditionally = 'True' ... ml.send_welcome_message = 'True' ... ml.subject_prefix = '' ... ml.subscription_policy = 'moderate' ... ml.max_message_size = '0' ... >>> manager.register(EcoStyle()) >>> commit() No error all seem good, i then do this to confirm the style is there: >>> from zope.component import getUtility >>> from mailman.interfaces.styles import IStyleManager >>> manager = getUtility(IStyleManager) >>> >>> for style in manager.styles: ... print(style.name) ... ECOstyle legacy-announce legacy-default private-default It shows me its there, then i proceed to quit() and go back in to the shell, and do this: >>> quit() ecoadmin@list01:/etc/mailman3$ sudo mailman shell Welcome to the GNU Mailman shell >>> from zope.component import getUtility >>> from mailman.interfaces.styles import IStyleManager >>> manager = getUtility(IStyleManager) >>> >>> for style in manager.styles: ... print(style.name) ... legacy-announce legacy-default private-default >>> and now my newly created style is gone again ? What am i missing here ? Kind regards Kenneth Karlsson

2 2

Re: use_https not being honored?
by Kiernan, Sean P. (MSFC-IS90)[EAST2] June 1, 2022

June 1, 2022

Thanks for the quick reply Steve, much appreciated. I'll take a look on the gunicorn side.

1 0

use_https not being honored?
by sean.p.kiernan＠nasa.gov June 1, 2022

June 1, 2022

Using Mailman core 3.3.5, and Mailman API 3.1, I have use_https: yes set in my mailman.cfg so that I can use https for calls to the API, however even in mailman.log, it still says it is using http: [2022-06-01 09:35:54 -0500] [959009] [INFO] Starting gunicorn 20.1.0 [2022-06-01 09:35:54 -0500] [959009] [INFO] Listening at: http://hostname:8001 (959009) GET and POST requests work fine if I use http, but fail when trying to use https. I have a certificate being used by our Mailman installation, so is there some additional config not mentioned in the docs to enable use of the API over https? I've only recently started using Mailman so if there are additional logs or system information I need to help with this?

2 1

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

June 1, 2022

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

2 3

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

May 26, 2022

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

2 1

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

May 25, 2022

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

2 1

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

May 25, 2022

Hello, My setup: - Debian 11 - Mailman3-full v 3.3.3-1 My Question: How to configure the visibility of a list of subscribers to a list? I created a list and set "subscriber visibility" to subscribers only. When I log in as such and try to view the list information, I can't see anywhere how to display that list. It's the same regardless of the setting used for this "subscriber visibility" field (only moderators, only subscribers or anyone). Is this normal? Is there something I misunderstood? Thank you in advance for your lights -- Pierre Malard Responsable architectures système CDS DINAMIS/THEIA Montpellier IRD - UMR Espace-Dev - UAR CPST - IR Data-Terra Maison de la Télédétection 500 rue Jean-François Breton 34093 Montpellier Cx 5 France « Il faut créer en même temps les élites et les débouchés, le syndica- lisme et les usines. Faire l'un sans l'autre, c'est travailler pour le malheur du peuple. » Romain Gary - "Les racines du ciel" |\ _,,,---,,_ /,`.-'`' -. ;-;;,_ |,4- ) )-,_. ,\ ( `'-' '---''(_/--' `-'\_) πr perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-. ;-;;,_: |,A- ) )-,_. ,\ ( `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"' `-'"'"'\_): 24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print' - --> Ce message n’engage que son auteur <-- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

2 1

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

May 22, 2022

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

3 2