- Mailman-users - lists.mailman3.org

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

Jan. 16, 2022

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

3 5

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

Jan. 16, 2022

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

2 23

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

Jan. 14, 2022

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

4 6

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

Jan. 14, 2022

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

3 2

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

Jan. 13, 2022

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

4 8

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

Jan. 13, 2022

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

2 1

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

Jan. 13, 2022

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

5 6

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

Jan. 13, 2022

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

1 0

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

Jan. 12, 2022

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

2 5

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

Jan. 11, 2022

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

3 5

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

Jan. 11, 2022

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

2 2

Newbie hyperkitty question
by Stephen Daniel Jan. 11, 2022

Jan. 11, 2022

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

3 5

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

Jan. 10, 2022

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

2 4

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

Jan. 10, 2022

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

3 4

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

Jan. 10, 2022

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

4 25

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

Jan. 8, 2022

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

2 7

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

Jan. 7, 2022

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

2 3

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

Jan. 7, 2022

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

2 2

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

Jan. 6, 2022

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

2 2

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

Jan. 6, 2022

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

2 2

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

Jan. 6, 2022

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

4 13

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

Jan. 6, 2022

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

2 8

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

Jan. 5, 2022

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

2 3

Healthchecks and Django
by Philip Colmer Jan. 5, 2022

Jan. 5, 2022

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

2 5

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

Jan. 5, 2022

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

2 2

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

Jan. 4, 2022

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

3 4

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

Jan. 4, 2022

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

3 5

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

Jan. 3, 2022

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

2 4

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

Jan. 2, 2022

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

3 8

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

Jan. 1, 2022

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

3 6

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

Dec. 29, 2021

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

3 6

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

Dec. 29, 2021

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

2 2

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

Dec. 29, 2021

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

4 9

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

Dec. 29, 2021

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

2 2

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

Dec. 28, 2021

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

2 2

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

Dec. 28, 2021

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

2 1

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

Dec. 28, 2021

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

2 17

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

Dec. 25, 2021

I have recently installed mailman3 on a Debian system with Posftix and Dovecot. I did it directly and did not use the docker setup. I managed to get it working to the point that I could send mail locally and outside my domain through mailman and log in as administrator. I decided to add a domain, but noticed on the form that the server was called "example.com." Clearly, I thought, I missed a configuration item here. I clicked on that, and it took me to a page where I could add servers. So, I added my real domain (libertyfp.org) It successfully added it, so I decided that I clearly didn't need "example.com" as a server, and deleted it using the same page. Immediately, I got an "internal server error" and have now lost all web interfaces. I tried restarting the daemons and rebooting the box, to no avail. The error message sent to my admin email is shown below. So... I have a couple of questions: 1) How can I set libertyfp.org as my server by use of a config file? 2) Failing that, how do a add "example.com" back, since I no longer have the web interface? I can't believe I did this. It took me a week to get this up and working, and I destroyed it in ten minutes after it was working. Any help would be appreciated. I suppose reinstalling will go much more quickly, since I know the mistakes I made over the past few days, but I really don't want to do that... Here's what it sends me: DoesNotExist at /mailman3/lists/ Site matching query does not exist. Request Method: GET Request URL: https://www.libertyfp.org/mailman3/lists/ Django Version: 3.0.14 Python Executable: /opt/mailman/venv/bin/uwsgi Python Version: 3.9.2 Python Path: ['/etc/mailman3/', '.', '', '/etc/mailman3', '/usr/lib/python39.zip', '/usr/lib/python3.9', '/usr/lib/python3.9/lib- dynload', '/opt/mailman/venv/lib/python3.9/site-packages'] Server time: Sat, 25 Dec 2021 04:14:00 +0000 Installed Applications: ['hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount'] Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.9/site- packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/opt/mailman/venv/lib/python3.9/site- packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/opt/mailman/venv/lib/python3.9/site- packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/venv/lib/python3.9/site- packages/postorius/views/list.py", line 978, in list_index return render(request, template, File "/opt/mailman/venv/lib/python3.9/site- packages/django/shortcuts.py", line 19, in render content = loader.render_to_string(template_name, context, request, using=using) File "/opt/mailman/venv/lib/python3.9/site- packages/django/template/loader.py", line 62, in render_to_string return template.render(context, request) File "/opt/mailman/venv/lib/python3.9/site- packages/django/template/backends/django.py", line 61, in render return self.template.render(context) File "/opt/mailman/venv/lib/python3.9/site- packages/django/template/base.py", line 169, in render with context.bind_template(self): File "/usr/lib/python3.9/contextlib.py", line 117, in __enter__ return next(self.gen) File "/opt/mailman/venv/lib/python3.9/site- packages/django/template/context.py", line 246, in bind_template updates.update(processor(self.request)) File "/opt/mailman/venv/lib/python3.9/site- packages/django_mailman3/context_processors.py", line 32, in common context["site_name"] = get_current_site(request).name File "/opt/mailman/venv/lib/python3.9/site- packages/django/contrib/sites/shortcuts.py", line 13, in get_current_site return Site.objects.get_current(request) File "/opt/mailman/venv/lib/python3.9/site- packages/django/contrib/sites/models.py", line 58, in get_current return self._get_site_by_id(site_id) File "/opt/mailman/venv/lib/python3.9/site- packages/django/contrib/sites/models.py", line 30, in _get_site_by_id site = self.get(pk=site_id) File "/opt/mailman/venv/lib/python3.9/site- packages/django/db/models/manager.py", line 82, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/opt/mailman/venv/lib/python3.9/site- packages/django/db/models/query.py", line 415, in get raise self.model.DoesNotExist( Exception Type: DoesNotExist at /mailman3/lists/ Exception Value: Site matching query does not exist. Request information: USER: AnonymousUser GET: No GET data POST: No POST data FILES: No FILES data COOKIES: csrftoken = 'qklMdfLOyqa1TWm0b8nEHMFVBLaa0CgU2DXhSywjpgZMTnCSTNA4MkD4lGLB6z5N' META: CSRF_COOKIE = 'qklMdfLOyqa1TWm0b8nEHMFVBLaa0CgU2DXhSywjpgZMTnCSTNA4MkD4lGLB6z5N' CSRF_COOKIE_USED = True HTTP_ACCEPT = 'text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image /webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9' HTTP_ACCEPT_ENCODING = 'gzip, deflate, br' HTTP_ACCEPT_LANGUAGE = 'en-US,en;q=0.9' HTTP_CONNECTION = 'close' HTTP_COOKIE = 'csrftoken=qklMdfLOyqa1TWm0b8nEHMFVBLaa0CgU2DXhSywjpgZMTnCSTNA4MkD4lGLB 6z5N' HTTP_DNT = '1' HTTP_HOST = 'www.libertyfp.org' HTTP_SEC_FETCH_DEST = 'document' HTTP_SEC_FETCH_MODE = 'navigate' HTTP_SEC_FETCH_SITE = 'none' HTTP_SEC_FETCH_USER = '?1' HTTP_SEC_GPC = '1' HTTP_UPGRADE_INSECURE_REQUESTS = '1' HTTP_USER_AGENT = 'Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.93 Safari/537.36' HTTP_X_FORWARDED_FOR = '174.212.65.52' HTTP_X_FORWARDED_HOST = 'www.libertyfp.org' HTTP_X_FORWARDED_PROTO = 'https' HTTP_X_FORWARDED_SERVER = 'www.libertyfp.org' PATH_INFO = '/mailman3/lists/' QUERY_STRING = '' REMOTE_ADDR = '127.0.0.1' REQUEST_METHOD = 'GET' REQUEST_URI = '/mailman3/lists/' SCRIPT_NAME = '' SERVER_NAME = 'libertyfp.org' SERVER_PORT = '8000' SERVER_PROTOCOL = 'HTTP/1.0' uwsgi.core = 0 uwsgi.node = b'libertyfp.org' uwsgi.version = b'2.0.20' wsgi.errors = <_io.TextIOWrapper name=2 mode='w' encoding='UTF-8'> wsgi.file_wrapper = '' wsgi.input = <uwsgi._Input object at 0x7f8591167d90> wsgi.multiprocess = True wsgi.multithread = True wsgi.run_once = False wsgi.url_scheme = 'https' wsgi.version = '(1, 0)' Settings: Using settings module settings ABSOLUTE_URL_OVERRIDES = {} ACCOUNT_AUTHENTICATION_METHOD = 'username_email' ACCOUNT_DEFAULT_HTTP_PROTOCOL = 'https' ACCOUNT_EMAIL_REQUIRED = True ACCOUNT_EMAIL_VERIFICATION = 'mandatory' ACCOUNT_UNIQUE_EMAIL = True ADMINS = "(('Mailman Suite Admin', 'fp145(a)libertyfp.org'),)" ALLOWED_HOSTS = ['localhost', 'www.libertyfp.org', 'libertyfp.org', 'mail.libertyfp.org', 'list.libertyfp.org', '127.0.0.1'] APPEND_SLASH = True AUTHENTICATION_BACKENDS = "('django.contrib.auth.backends.ModelBackend', 'allauth.account.auth_backends.AuthenticationBackend')" AUTH_PASSWORD_VALIDATORS = '********************' AUTH_USER_MODEL = 'auth.User' BASE_DIR = PosixPath('/opt/mailman/web') CACHES = {'default': {'BACKEND': 'django.core.cache.backends.locmem.LocMemCache'}} CACHE_MIDDLEWARE_ALIAS = 'default' CACHE_MIDDLEWARE_KEY_PREFIX = '********************' CACHE_MIDDLEWARE_SECONDS = 600 COMPRESSORS = {'css': 'compressor.css.CssCompressor', 'js': 'compressor.js.JsCompressor'} COMPRESS_CACHEABLE_PRECOMPILERS = '()' COMPRESS_CACHE_BACKEND = 'default' COMPRESS_CACHE_KEY_FUNCTION = '********************' COMPRESS_CLEAN_CSS_ARGUMENTS = '' COMPRESS_CLEAN_CSS_BINARY = 'cleancss' COMPRESS_CLOSURE_COMPILER_ARGUMENTS = '' COMPRESS_CLOSURE_COMPILER_BINARY = 'java -jar compiler.jar' COMPRESS_CSS_HASHING_METHOD = 'mtime' COMPRESS_DATA_URI_MAX_SIZE = 1024 COMPRESS_DEBUG_TOGGLE = None COMPRESS_ENABLED = True COMPRESS_FILTERS = {'css': ['compressor.filters.css_default.CssAbsoluteFilter', 'compressor.filters.cssmin.rCSSMinFilter'], 'js': ['compressor.filters.jsmin.rJSMinFilter']} COMPRESS_JINJA2_GET_ENVIRONMENT = <function CompressorConf.JINJA2_GET_ENVIRONMENT at 0x7f859064d670> COMPRESS_MINT_DELAY = 30 COMPRESS_MTIME_DELAY = 10 COMPRESS_OFFLINE = False COMPRESS_OFFLINE_CONTEXT = {'STATIC_URL': '/static/'} COMPRESS_OFFLINE_MANIFEST = 'manifest.json' COMPRESS_OFFLINE_TIMEOUT = 31536000 COMPRESS_OUTPUT_DIR = 'CACHE' COMPRESS_PARSER = 'compressor.parser.AutoSelectParser' COMPRESS_PRECOMPILERS = "(('text/x-scss', 'sassc -t compressed {infile} {outfile}'), ('text/x-sass', 'sassc -t compressed {infile} {outfile}'))" COMPRESS_REBUILD_TIMEOUT = 2592000 COMPRESS_ROOT = '/opt/mailman/web/static' COMPRESS_STORAGE = 'compressor.storage.CompressorFileStorage' COMPRESS_TEMPLATE_FILTER_CONTEXT = {'STATIC_URL': '/static/'} COMPRESS_URL = '/static/' COMPRESS_URL_PLACEHOLDER = '/__compressor_url_placeholder__/' COMPRESS_VERBOSE = False COMPRESS_YUGLIFY_BINARY = 'yuglify' COMPRESS_YUGLIFY_CSS_ARGUMENTS = '--terminal' COMPRESS_YUGLIFY_JS_ARGUMENTS = '--terminal' COMPRESS_YUI_BINARY = 'java -jar yuicompressor.jar' COMPRESS_YUI_CSS_ARGUMENTS = '' COMPRESS_YUI_JS_ARGUMENTS = '' CSRF_COOKIE_AGE = 31449600 CSRF_COOKIE_DOMAIN = None CSRF_COOKIE_HTTPONLY = False CSRF_COOKIE_NAME = 'csrftoken' CSRF_COOKIE_PATH = '/' CSRF_COOKIE_SAMESITE = 'Lax' CSRF_COOKIE_SECURE = False CSRF_FAILURE_VIEW = 'django.views.csrf.csrf_failure' CSRF_HEADER_NAME = 'HTTP_X_CSRFTOKEN' CSRF_TRUSTED_ORIGINS = [] CSRF_USE_SESSIONS = False DATABASES = {'default': {'ENGINE': 'django.db.backends.postgresql_psycopg2', 'NAME': 'mailman', 'USER': 'mailman', 'PASSWORD': '********************', 'HOST': 'localhost', 'PORT': '5432', 'ATOMIC_REQUESTS': False, 'AUTOCOMMIT': True, 'CONN_MAX_AGE': 0, 'OPTIONS': {}, 'TIME_ZONE': None, 'TEST': {'CHARSET': None, 'COLLATION': None, 'NAME': None, 'MIRROR': None}}} DATABASE_ROUTERS = [] DATA_UPLOAD_MAX_MEMORY_SIZE = 2621440 DATA_UPLOAD_MAX_NUMBER_FIELDS = 1000 DATETIME_FORMAT = 'N j, Y, P' DATETIME_INPUT_FORMATS = ['%Y-%m-%d %H:%M:%S', '%Y-%m-%d %H:%M:%S.%f', '%Y-%m-%d %H:%M', '%Y-%m-%d', '%m/%d/%Y %H:%M:%S', '%m/%d/%Y %H:%M:%S.%f', '%m/%d/%Y %H:%M', '%m/%d/%Y', '%m/%d/%y %H:%M:%S', '%m/%d/%y %H:%M:%S.%f', '%m/%d/%y %H:%M', '%m/%d/%y'] DATE_FORMAT = 'N j, Y' DATE_INPUT_FORMATS = ['%Y-%m-%d', '%m/%d/%Y', '%m/%d/%y', '%b %d %Y', '%b %d, %Y', '%d %b %Y', '%d %b, %Y', '%B %d %Y', '%B %d, %Y', '%d %B %Y', '%d %B, %Y'] DEBUG = False DEBUG_PROPAGATE_EXCEPTIONS = False DECIMAL_SEPARATOR = '.' DEFAULT_CHARSET = 'utf-8' DEFAULT_EXCEPTION_REPORTER_FILTER = 'django.views.debug.SafeExceptionReporterFilter' DEFAULT_FILE_STORAGE = 'django.core.files.storage.FileSystemStorage' DEFAULT_FROM_EMAIL = 'mailman(a)libertyfp.org' DEFAULT_INDEX_TABLESPACE = '' DEFAULT_TABLESPACE = '' DISALLOWED_USER_AGENTS = [] EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_HOST_PASSWORD = '********************' EMAIL_HOST_USER = 'mailman(a)libertyfp.org' EMAIL_PORT = 25 EMAIL_SSL_CERTFILE = None EMAIL_SSL_KEYFILE = '********************' EMAIL_SUBJECT_PREFIX = '[Django] ' EMAIL_TIMEOUT = None EMAIL_USE_LOCALTIME = False EMAIL_USE_SSL = False EMAIL_USE_TLS = False FILE_CHARSET = 'utf-8' FILE_UPLOAD_DIRECTORY_PERMISSIONS = None FILE_UPLOAD_HANDLERS = ['django.core.files.uploadhandler.MemoryFileUploadHandler', 'django.core.files.uploadhandler.TemporaryFileUploadHandler'] FILE_UPLOAD_MAX_MEMORY_SIZE = 2621440 FILE_UPLOAD_PERMISSIONS = 420 FILE_UPLOAD_TEMP_DIR = None FILTER_VHOST = False FIRST_DAY_OF_WEEK = 0 FIXTURE_DIRS = [] FORCE_SCRIPT_NAME = None FORMAT_MODULE_PATH = None FORM_RENDERER = 'django.forms.renderers.DjangoTemplates' HAYSTACK_CONNECTIONS = {'default': {'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', 'PATH': '/opt/mailman/web/fulltext_index'}} HYPERKITTY_ENABLE_GRAVATAR = True IGNORABLE_404_URLS = [] INSTALLED_APPS = ['hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount'] INTERNAL_IPS = [] LANGUAGES = [('af', 'Afrikaans'), ('ar', 'Arabic'), ('ast', 'Asturian'), ('az', 'Azerbaijani'), ('bg', 'Bulgarian'), ('be', 'Belarusian'), ('bn', 'Bengali'), ('br', 'Breton'), ('bs', 'Bosnian'), ('ca', 'Catalan'), ('cs', 'Czech'), ('cy', 'Welsh'), ('da', 'Danish'), ('de', 'German'), ('dsb', 'Lower Sorbian'), ('el', 'Greek'), ('en', 'English'), ('en-au', 'Australian English'), ('en-gb', 'British English'), ('eo', 'Esperanto'), ('es', 'Spanish'), ('es-ar', 'Argentinian Spanish'), ('es-co', 'Colombian Spanish'), ('es-mx', 'Mexican Spanish'), ('es-ni', 'Nicaraguan Spanish'), ('es-ve', 'Venezuelan Spanish'), ('et', 'Estonian'), ('eu', 'Basque'), ('fa', 'Persian'), ('fi', 'Finnish'), ('fr', 'French'), ('fy', 'Frisian'), ('ga', 'Irish'), ('gd', 'Scottish Gaelic'), ('gl', 'Galician'), ('he', 'Hebrew'), ('hi', 'Hindi'), ('hr', 'Croatian'), ('hsb', 'Upper Sorbian'), ('hu', 'Hungarian'), ('hy', 'Armenian'), ('ia', 'Interlingua'), ('id', 'Indonesian'), ('io', 'Ido'), ('is', 'Icelandic'), ('it', 'Italian'), ('ja', 'Japanese'), ('ka', 'Georgian'), ('kab', 'Kabyle'), ('kk', 'Kazakh'), ('km', 'Khmer'), ('kn', 'Kannada'), ('ko', 'Korean'), ('lb', 'Luxembourgish'), ('lt', 'Lithuanian'), ('lv', 'Latvian'), ('mk', 'Macedonian'), ('ml', 'Malayalam'), ('mn', 'Mongolian'), ('mr', 'Marathi'), ('my', 'Burmese'), ('nb', 'Norwegian Bokmål'), ('ne', 'Nepali'), ('nl', 'Dutch'), ('nn', 'Norwegian Nynorsk'), ('os', 'Ossetic'), ('pa', 'Punjabi'), ('pl', 'Polish'), ('pt', 'Portuguese'), ('pt-br', 'Brazilian Portuguese'), ('ro', 'Romanian'), ('ru', 'Russian'), ('sk', 'Slovak'), ('sl', 'Slovenian'), ('sq', 'Albanian'), ('sr', 'Serbian'), ('sr-latn', 'Serbian Latin'), ('sv', 'Swedish'), ('sw', 'Swahili'), ('ta', 'Tamil'), ('te', 'Telugu'), ('th', 'Thai'), ('tr', 'Turkish'), ('tt', 'Tatar'), ('udm', 'Udmurt'), ('uk', 'Ukrainian'), ('ur', 'Urdu'), ('uz', 'Uzbek'), ('vi', 'Vietnamese'), ('zh-hans', 'Simplified Chinese'), ('zh-hant', 'Traditional Chinese')] LANGUAGES_BIDI = ['he', 'ar', 'fa', 'ur'] LANGUAGE_CODE = 'en-us' LANGUAGE_COOKIE_AGE = None LANGUAGE_COOKIE_DOMAIN = None LANGUAGE_COOKIE_HTTPONLY = False LANGUAGE_COOKIE_NAME = 'django_language' LANGUAGE_COOKIE_PATH = '/' LANGUAGE_COOKIE_SAMESITE = None LANGUAGE_COOKIE_SECURE = False LOCALE_PATHS = [] LOGGING = {'version': 1, 'disable_existing_loggers': False, 'filters': {'require_debug_false': {'()': 'django.utils.log.RequireDebugFalse'}}, 'handlers': {'mail_admins': {'level': 'ERROR', 'filters': ['require_debug_false'], 'class': 'django.utils.log.AdminEmailHandler'}, 'file': {'level': 'INFO', 'class': 'logging.handlers.WatchedFileHandler', 'filename': '/opt/mailman/web/logs/mailmanweb.log', 'formatter': 'verbose'}, 'console': {'class': 'logging.StreamHandler', 'formatter': 'simple'}}, 'loggers': {'django.request': {'handlers': ['mail_admins', 'file'], 'level': 'ERROR', 'propagate': True}, 'django': {'handlers': ['file'], 'level': 'ERROR', 'propagate': True}, 'hyperkitty': {'handlers': ['file'], 'level': 'DEBUG', 'propagate': True}, 'postorius': {'handlers': ['console', 'file'], 'level': 'INFO'}}, 'formatters': {'verbose': {'format': '%(levelname)s %(asctime)s %(process)d %(name)s %(message)s'}, 'simple': {'format': '%(levelname)s %(message)s'}}} LOGGING_CONFIG = 'logging.config.dictConfig' LOGIN_REDIRECT_URL = 'list_index' LOGIN_URL = 'account_login' LOGOUT_REDIRECT_URL = None LOGOUT_URL = 'account_logout' MAILMAN_ARCHIVER_FROM = "('127.0.0.1', '::1')" MAILMAN_ARCHIVER_KEY = '********************' MAILMAN_REST_API_PASS = '********************' MAILMAN_REST_API_URL = '********************' MAILMAN_REST_API_USER = '********************' MANAGERS = [] MEDIA_ROOT = '' MEDIA_URL = '' MESSAGE_STORAGE = 'django.contrib.messages.storage.fallback.FallbackStorage' MESSAGE_TAGS = {40: 'danger'} MIDDLEWARE = "('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware')" MIGRATION_MODULES = {} MONTH_DAY_FORMAT = 'F j' NUMBER_GROUPING = 0 PASSWORD_HASHERS = '********************' PASSWORD_RESET_TIMEOUT_DAYS = '********************' POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000' PREPEND_WWW = False Q_CLUSTER = {'retry': 360, 'timeout': 300, 'save_limit': 100, 'orm': 'default'} ROOT_URLCONF = 'mailman_web.urls' SECRET_KEY = '********************' SECURE_BROWSER_XSS_FILTER = False SECURE_CONTENT_TYPE_NOSNIFF = True SECURE_HSTS_INCLUDE_SUBDOMAINS = False SECURE_HSTS_PRELOAD = False SECURE_HSTS_SECONDS = 0 SECURE_PROXY_SSL_HEADER = None SECURE_REDIRECT_EXEMPT = [] SECURE_REFERRER_POLICY = None SECURE_SSL_HOST = None SECURE_SSL_REDIRECT = False SERVER_EMAIL = 'root(a)localhost.local' SESSION_CACHE_ALIAS = 'default' SESSION_COOKIE_AGE = 1209600 SESSION_COOKIE_DOMAIN = None SESSION_COOKIE_HTTPONLY = True SESSION_COOKIE_NAME = 'sessionid' SESSION_COOKIE_PATH = '/' SESSION_COOKIE_SAMESITE = 'Lax' SESSION_COOKIE_SECURE = False SESSION_ENGINE = 'django.contrib.sessions.backends.db' SESSION_EXPIRE_AT_BROWSER_CLOSE = False SESSION_FILE_PATH = None SESSION_SAVE_EVERY_REQUEST = False SESSION_SERIALIZER = 'django.contrib.sessions.serializers.PickleSerializer' SETTINGS_MODULE = 'settings' SHORT_DATETIME_FORMAT = 'm/d/Y P' SHORT_DATE_FORMAT = 'm/d/Y' SIGNING_BACKEND = 'django.core.signing.TimestampSigner' SILENCED_SYSTEM_CHECKS = [] SITE_ID = 1 SOCIALACCOUNT_PROVIDERS = {'openid': {'SERVERS': [{'id': 'yahoo', 'name': 'Yahoo', 'openid_url': 'http://me.yahoo.com'}]}, 'google': {'SCOPE': ['profile', 'email'], 'AUTH_PARAMS': {'access_type': 'online'}}, 'facebook': {'METHOD': 'oauth2', 'SCOPE': ['email'], 'FIELDS': ['email', 'name', 'first_name', 'last_name', 'locale', 'timezone'], 'VERSION': 'v2.4'}} STATICFILES_DIRS = '()' STATICFILES_FINDERS = "('django.contrib.staticfiles.finders.FileSystemFinder', 'django.contrib.staticfiles.finders.AppDirectoriesFinder', 'compressor.finders.CompressorFinder')" STATICFILES_STORAGE = 'django.contrib.staticfiles.storage.StaticFilesStorage' STATIC_ROOT = '/opt/mailman/web/static' STATIC_URL = '/static/' TEMPLATES = [{'BACKEND': 'django.template.backends.django.DjangoTemplates', 'DIRS': [], 'APP_DIRS': True, 'OPTIONS': {'context_processors': ['django.template.context_processors.debug', 'django.template.context_processors.i18n', 'django.template.context_processors.media', 'django.template.context_processors.static', 'django.template.context_processors.tz', 'django.template.context_processors.csrf', 'django.template.context_processors.request', 'django.contrib.auth.context_processors.auth', 'django.contrib.messages.context_processors.messages', 'django_mailman3.context_processors.common', 'hyperkitty.context_processors.common', 'postorius.context_processors.postorius']}}] TEST_NON_SERIALIZED_APPS = [] TEST_RUNNER = 'django.test.runner.DiscoverRunner' THOUSAND_SEPARATOR = ',' TIME_FORMAT = 'P' TIME_INPUT_FORMATS = ['%H:%M:%S', '%H:%M:%S.%f', '%H:%M'] TIME_ZONE = 'UTC' USE_I18N = True USE_L10N = True USE_THOUSAND_SEPARATOR = False USE_TZ = True USE_X_FORWARDED_HOST = False USE_X_FORWARDED_PORT = False WSGI_APPLICATION = 'mailman_web.wsgi.application' X_FRAME_OPTIONS = 'DENY' YEAR_MONTH_FORMAT = 'F Y'

2 4

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

Dec. 23, 2021

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

2 1

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

Dec. 23, 2021

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

2 1

Mailing Lists
by John McDonald Dec. 23, 2021

Dec. 23, 2021

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

1 0

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

Dec. 22, 2021

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

4 7

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

Dec. 22, 2021

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

2 1

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

Dec. 20, 2021

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

4 21

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

Dec. 17, 2021

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

3 3

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

Dec. 16, 2021

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

2 1

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

Dec. 12, 2021

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

3 4

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

Dec. 10, 2021

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

1 1

Lookup Table Questions
by Peter Williams Dec. 8, 2021

Dec. 8, 2021

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

2 1

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

Dec. 8, 2021

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

2 3