Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: Installing mailman 3

by Rafael Mora

It's ok now, but still I can't make it send the confirmation email This is from mailman.log: [mailman@localhost logs]$ tail -f mailman.log Aug 01 15:59:18 2017 (2327) lmtp runner started. Aug 01 15:59:18 2017 (2333) virgin runner started. Aug 01 15:59:18 2017 (2332) retry runner started. Aug 01 15:59:18 2017 (2330) pipeline runner started. Aug 01 15:59:18 2017 (2325) command runner started. Aug 01 15:59:19 2017 (2328) nntp runner started. Aug 01 15:59:19 2017 (2326) in runner started. Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET /3.0/lists?count=0&page=1&advertised=true HTTP/1.1" 200 90 Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET /3.0/lists?count=10&page=1&advertised=true HTTP/1.1" 200 90 Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET /3.0/domains HTTP/1.1" 200 90 What should I do? El mar., 1 ago. 2017 a las 15:36, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 8/1/17 1:14 PM, Rafael Mora wrote: > > > > Why does it say Address already in use? > > > Because you are starting lm tp runner and it's already running. > > Do 'mailman stop'. Then ensure no Mailman processes are running. kill > any if necessary. Then do 'mailman start'. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 1 month

[MM3-users] Re: Mailman 3 installation, no mails in hyperkitty, unable to add footer.

by Ugnius

Mark, Thank You for your guidance. Yes, seems my installed mailman3 package is not full. I have tried to install it on my Debian 9, but I got package broken error and all possible proposals how to fix it did not help. But it is normal - official OS version 9 has no this package included. Then I have decided to play on another machine where is installed Debian 10. I have successfully installed mailman3-full. It already came pre-configured with keys included. Mailman3-web packige was something new for me. I understand it replaces mailman- suite, but like I did not find where to read about it, I did not find how to open the administration or postorius site. Kind regards Ugnius > On 23 Aug 2019, at 23:18, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 8/23/19 12:17 PM, Ugnius S wrote: >> >> It would be good to read about working example how to setup, and which >> moments are important. > > > See <https://wiki.list.org/DOC/Mailman%203%20installation%20experience>. > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

6 years

[MM3-users] Re: Error when sending customized welcome message template

by Markus Grandpré

Dear Mr. Sapiro, Thank you once again for your help. The templates are now being sent without any errors. However, while using the many variables that can be sent with a template, I noticed that the resolution of the variable $hyperkitty_url is not working, even though i am using a private archive in this list and a URL to this archive exists. Best regards, Markus Grandpré Am 13.03.25 um 14:12 schrieb Mark Sapiro: > On 3/13/25 2:54 PM, Markus Grandpré wrote: >> Dear List, >> >> As soon as a template "[list:user:notice:welcome]" exists, and at >> least one email address is provided during mass subscribe, while >> sending an invitation is disabled and sending a welcome message is >> enabled, the following error occurs: >> >> HTTP Error 400: ('Connection aborted.', ConnectionResetError(104, >> 'Connection reset by peer')) > > Was this template set in Postorius? If so, there is an issue with your > setting for POSTORIUS_TEMPLATE_BASE_URL. The default is > ``` > POSTORIUS_TEMPLATE_BASE_URL = http://localhost:8000/ > ``` > which should work if your wsgi server is listening on the local host, > port 8000, but setting it to the base scheme and host you use to access > Postorius is generally good. > -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: +49 7531 88 4342

5 months, 3 weeks

[MM3-users] Re: templates

by Odhiambo Washington

Isn't that the same thing as not having them in the FS? I read (and asked questions about) templates almost 10x before I got to understand the locations and how MM uses them. It's not easy to understand the ones in the FS while the ones in the DB are easy. Then again, one needs to know that Postorius only writes to the DB. On Thu, May 4, 2023, 22:59 Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/4/23 12:44, Odhiambo Washington wrote: > > If you don't have any templates in the file system and none in the DB > > table, then you must go to Jerusalem and pray, because you don't have any > > and nothing will work the way you want. > > It's either or! > > > He didn't say he didn't have templates in the file system. He said he > didn't have any custom templates in Mailman's var/templates/lists/ > directory. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to odhiambo(a)gmail.com >

2 years, 4 months

[MM3-users] Re: Change language to welcome message in mailman3

by Mark Sapiro

On 7/29/20 4:15 PM, Massimo Zappalà wrote: > Hi Mark, > > /usr/lib/python3/dist-packages/mailman/templates/it$ ls -la > > -rw-r--r-- 1 root root 484 Jul 25 17:21 domain:admin:notice:new-list.txt > -rw-r--r-- 1 root root 825 Jul 25 17:06 help.txt > -rw-r--r-- 1 root root 0 Jan 4 2019 __init__.py > -rw-r--r-- 1 root root 701 Jul 25 17:19 invite.txt > -rw-r--r-- 1 root root 337 Jul 26 16:36 list:admin:action:post.txt > -rw-r--r-- 1 root root 145 Jul 26 16:36 list:admin:action:subscribe.txt > -rw-r--r-- 1 root root 157 Jul 26 16:36 list:admin:action:unsubscribe.txt > -rw-r--r-- 1 root root 56 Jul 26 16:23 list:admin:notice:subscribe.txt > -rw-r--r-- 1 root root 334 Jul 26 16:49 list:admin:notice:unrecognized.txt > -rw-r--r-- 1 root root 43 Jul 26 16:49 list:admin:notice:unsubscribe.txt > -rw-r--r-- 1 root root 0 Jan 4 2019 list:member:digest:header.txt > -rw-r--r-- 1 root root 423 Jul 26 17:07 list:member:digest:masthead.txt > -rw-r--r-- 1 root root 160 Jul 26 17:08 list:member:generic:footer.txt > -rw-r--r-- 1 root root 0 Jan 4 2019 list:member:regular:header.txt > -rw-r--r-- 1 root root 658 Jul 26 17:18 list:user:action:subscribe.txt > -rw-r--r-- 1 root root 675 Jul 26 17:18 list:user:action:unsubscribe.txt > -rw-r--r-- 1 root root 0 Jan 4 2019 list:user:notice:goodbye.txt > -rw-r--r-- 1 root root 328 Jul 26 17:23 list:user:notice:hold.txt > -rw-r--r-- 1 root root 464 Jul 26 17:31 list:user:notice:no-more-today.txt > -rw-r--r-- 1 root root 108 Jul 26 17:32 list:user:notice:post.txt > -rw-r--r-- 1 root root 634 Jul 26 17:38 list:user:notice:probe.txt > -rw-r--r-- 1 root root 318 Jul 26 17:40 list:user:notice:refuse.txt > -rw-r--r-- 1 root root 155 Jul 26 17:42 list:user:notice:rejected.txt > -rw-r--r-- 1 root root 554 Jul 26 17:47 list:user:notice:welcome.txt > drwxr-xr-x 2 root root 4096 Jul 29 22:14 __pycache__ What is the ownership of the other directories in /usr/lib/python3/dist-packages/mailman/? They are probably also owned by root and that should be OK as long as they are world readable. >> I may need more information about messages that are and aren't >> delivered. I.e. what's different between them and the way they are >> submitted, or is this one message only delivered to some users? > > After copying the template files in the path indicated by you, the translated emails arrive only to the administrator user while the members of the list arrive in English. Please tell me what messages. Do you mean if I subscribe to the list, I get a welcome message in English, but the list owner gets the notification of a new member in Italian? I think you need to set the system default_language. In mailman.cfg, set [mailman] default_language: it -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: DKIM signatures with message footers or subject prefixes

by Stanisław Findeisen

Thank you for your clarification. I am now wildcard (*) DKIM-signing the (arbitrary) From: address domain with the host domain key. However my mailing list is a virtual host (actually there are several of them), which is different than the host domain. Do you know if such a setup is harmful? Or if there is a way to select the VHOST key? This is Postfix + OpenDKIM. With DMARC mitigation action = Replace From: and DMARC Mitigate unconditionally = Yes the VHOST key gets selected, which also results in (existing and) valid DMARC. Perhaps this setup makes it easier to pass through the spam filters?... But the cost is the abused From:. Thank you Stanisław On Sat, Mar 12, 2022 at 12:49:38PM -0800, Mark Sapiro wrote: > On 3/12/22 12:20, Stanisław Findeisen via Mailman-users wrote: > > On Fri, Mar 11, 2022 at 10:41:00AM -0800, Mark Sapiro wrote: > > > Also, your outgoing MTA should DKIM sign the mail on the way out. With that and the above setting, the outgoing message will have only your > > > valid DKIM signature and no prior Authentication-Results:. > > > > Ok, you mean after replacing the From address with the list address, right? > > I can see no way (or sense) to DKIM sign arbitrary From: addresses. > > > Your DKIM signature only says you sent the mail and if the signature validates, the mail hasn't been modified since you signed it. I.e. > validation of the signature is a statement to the recipient that the mail received is what you sent. That's all. > > If the domain of the From: address doesn't align with your domain, the signature won't help with DMARC, but that's a separate issue and why we > have DMARC mitigations suck as replacing the From: with the list address. > > > > This actually works quite good: the recipient just gets 2 DKIM signatures. The original one is broken, the MTA-generated one (after writing my list address into From) is OK. This is good enough even for ProtonMail (no red warning). > > > And your rewriting the From: is only necessary for DMARC. If the ProtonMail red flag is only because there was no valid DKIM signature, you > shouldn't need to rewrite From:. If it is because of DMARC, you do. > > > > What about this list (mailman-users). It looks this one also has From address replacement + conditional DMARC mitigation. And remove_dkim_headers: no. Correct? > > > This list has DMARC mitigation action = Replace From: and DMARC Mitigate unconditionally = No and remove_dkim_headers: no. > > We DKIM sign all outgoing mail from lists.mailman3.org. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

3 years, 5 months

[MM3-users] Re: Blocked by Hotmail

by Mark Sapiro

On 1/22/21 4:11 PM, Tom @ Gather wrote: > I am getting rejections from Hotmail > > Jan 18 14:42:22 mail postfix/smtp[6571]: 046713F914: to=< > helen_maryd(a)hotmail.com>, > relay=hotmail-com.olc.protection.outlook.com[104.47.58.161]:25, > delay=0.14, delays=0.06/0.03/0.04/0.01, dsn=5.7.1, status=bounced (host > hotmail-com.olc.protection.outlook.com[104.47.58.161] said: 550 5.7.1 > Unfortunately, messages from [167.99.151.239] weren't sent. Please contact > your Internet service provider since part of their network is on our block > list (S3140). You can also refer your provider to > http://mail.live.com/mail/troubleshooting.aspx#errors. [ > BN8NAM11FT014.eop-nam11.prod.protection.outlook.com] (in reply to MAIL FROM > command)) > > I have submitted a ticket to > https://support.microsoft.com/en-us/supportrequestform/8ad563e3-288e-2a61-8… > > Not sure why they are blocking me. Not on any other blacklists per > mxtoolbox... > > Anyone else experienced this? How to resolve? Yes, I've had this block at times. All the affected servers subscribe to SNDS and JMRP and never receive any bad reports. The process is to submit the form as you have done. This may result in mitigation without further action on your part, but if they reply to the ticket with Not qualified for mitigation (IP address) Our investigation has determined that the above IP(s) do not qualify for mitigation. The next step is to reply to that with an explanation of what you do. Here's a copy of such a reply: ------------------------------------------------------------ Beginning around 14:43 -0500 on Dec 31, mail from mail.python.org (IP 188.166.95.178) to various hotmail.com, outlook.com. live.com, etc. addresses is being blocked. A typical response to such mail is Jan 4 19:11:49 mail postfix/smtp[14283]: 4D8tGD3YZSzpFbf: to=<marksapiro(a)hotmail.com>, relay=hotmail-com.olc.protection.outlook.com[104.47.17.161]:25, delay=0.69, delays=0.55/0.01/0.11/0.03, dsn=5.7.1, status=bounced (host hotmail-com.olc.protection.outlook.com[104.47.17.161] said: 550 5.7.1 Unfortunately, messages from [188.166.95.178] weren't sent. Please contact your Internet service provider since part of their network is on our block list (S3140). You can also refer your provider to http://mail.live.com/mail/troubleshooting.aspx#errors. [VI1EUR05FT004.eop-eur05.prod.protection.outlook.com] (in reply to MAIL FROM command)) This mail is virtually all messages to confirmed opt-in subscribers of various python.org email lists. We do not send spam and we have various filters in place to block spam from reaching these lists. We publish SPF and DMARC records for our domain and DKIM sign our outgoing mail. We subscribe to your Junk Email Reporting Program (JMRP) and Smart Network Data Services (SNDS) and see no reports or unusual complaint rates. Our IP 188.166.95.178 is not found on any blacklists checked at <https://mxtoolbox.com/SuperTool.aspx?action=blacklist%3a188.166.95.178&run=…> Please stop blocking our mail. ------------------------------------------------------------ This usually works. If not, you just have to persist. > My mail server is on Digital Ocean if that makes any difference. It may. All of my recent blocks have been DigitalOcean servers including mail.python.org, but I think I've had this in the past from non- DigitalOcean servers. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: Lessons learned and a couple little gotcha for newbies

by Mark Sapiro

On 12/28/21 11:56 AM, William Oliver wrote: > > 1) I got the error > > django.template.library.InvalidTemplateLibrary: Invalid template > library specified. ImportError raised when trying to load > 'hyperkitty.templatetags.decorate': cannot import name 'escape_html' > from 'mistune.scanner' (/opt/mailman/venv/lib/python3.9/site- > packages/mistune/scanner.py) > > when I ran 'mailman-web migrate' > > The fix was trivial: I just added the lines: > > from mistune.util import escape_html > from mistune.util import escape_url > to > /opt/mailman/venv/lib/python3.9/site-packages/mistune/scanner.py This is fixed at https://gitlab.com/mailman/hyperkitty/-/merge_requests/379. Unfortunately, that fix is not in the latest release version. We will need to address that as mistune 2.0.0 moved those functions from their prior location in mistune 2.0.0rc1 > 2) Similarly, migrate (using postgres) also gave the error: > > File "/opt/mailman/venv/lib/python3.9/site- > packages/django/db/backends/postgresql/utils.py", line 6, in > utc_tzinfo_factory > raise AssertionError("database connection isn't set to UTC") > > I was able to find a discusson of this one at > > https://stackoverflow.com/questions/68024060/assertionerror-database-connec… > > which had me downgrade to an older version of psycopg2-binary: > > pip install psycopg2-binary==2.8.6 > > There might be a different fix, but this worked. This should be fixed in psycopg2-binary, but it isn't. The work around is what you did and I'll update the doc. > 3) When I ran the test "uwsgi --ini /etc/mailman3/uwsgi.ini" I got the > error: > > ModuleNotFoundError: No module named 'settings' > > This was also trivially fixed by adding the path: > > export PYTHONPATH=$PYTHONPATH:/etc/mailman3 > > in /opt/mailman/.bashrc The recommended uwsgi.ini includes pythonpath = /etc/mailman3/ according to https://uwsgi-docs.readthedocs.io/en/latest/Options.html?highlight=pythonpa… this should work. Did you have that? If you did and it doesn't work, perhaps adding env = PYTHONPATH=/etc/mailman3 would work. > 4) Sometimes when I rebooted the machine, when I ran 'systemctl start > mailman3' I'd get the error that mailman wouldn't start because the > lock was stll there. I never could figure out where the lock was, so I > worked around it by replacing > > > ExecStart=/opt/mailman/venv/bin/mailman start > > with > ExecStart=/opt/mailman/venv/bin/mailman start --force > > in /etc/systemd/system/mailman3.service > > I'm sure there's something bad about doing that, but it works for me, > so far. The lock is /opt/mailman/mm/var/locks/master.lck* The problem with using --force unconditionally is you can start a second instance when mailman core is already running and that causes other issues. > 5) I had a problem with mail to outside people not being delivered > while mail to the local host was delivered. It turned out that this was > because in my mailman.cfg I had "smtp_host:my.listserver.tld when it > should have been localhost. The error was "relay access denied." To > fix this, I had to add my.listserver.tld to "mynetworks" in > /etc/postfix/main.cf, ie change: > > mynetworks = 127.0.0.0/8 10.0.0.0/24 > > to > > mynetworks = 127.0.0.0/8 10.0.0.0/24 111.222.333.444 <--- my ip address > > However, Mark Sapiro (a God) told me this was because I had changed a > line in the [mta] section of mailman.cfg. I had changed > > smtp_host: localhost > > to > > smtp_host: mydomain.tld > > Here's the thing. The reason I did this was because the instructions at > https://docs.mailman3.org/en/latest/config-core.html > > give this as their model: > > > [mta] > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > lmtp_host: mail.example.com > lmtp_port: 8024 > smtp_host: mail.example.com <---- not localhost > smtp_port: 25 I'll add some clarification to the doc. > The instructions are good, but there are a few places where one size > does not fit all, I guess. > > 6) A second error in delivery to outside addresses resulted in an > "Access denied" error. A search on the internet revealed that this had > to do with (for me) smtpd_recipient_restrictions in postfix. See, for > instance: > https://know.mailsbestfriend.com/postfix_error_relay_access_denied_noqueue_… > > Changing this fixed things. > > I'm not sure, but I think this shows up mostly with installations that > include dovecot. This is a Postfix configuration issue. <big snip> Thanks for your feedback. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: How to hide sender completely

by Mark Sapiro

On 5/9/23 14:22, Roland Miyamoto via Mailman-users wrote: > • Anonymous list= Yes ... > As you can see, the header contains the sender's address > > sender(a)otherdomain.tld > > twice. ... > From - Fri Apr 21 23:18:21 2023 > X-Mozilla-Status: 0001 > X-Mozilla-Status2: 00000000 > X-Mozilla-Keys: > Return-Path: <ourlist-bounces(a)list.timebrain.org> > Received: from mail.timebrain.org > by mail.timebrain.org with LMTP > id Ph5sJ0XzQmSxBQAAMe3UBQ > (envelope-from <ourlist-bounces(a)list.timebrain.org>); Fri, 21 Apr > 2023 22:34:13 +0200 > Received: from timebrain.org (localhost [IPv6:::1]) > by mail.timebrain.org (Postfix) with ESMTP id 9110FC0082; > Fri, 21 Apr 2023 22:34:13 +0200 (CEST) > DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=list.timebrain.org; > s=202205; t=1682109253; > bh=KEcouWpeNLb32k6bFssIJDhe16IGlOZEsBeJOIigkLs=; > h=Date:To:In-Reply-To:References:From:Reply-To:Subject:List-Id: > List-Help:List-Post:List-Subscribe:List-Unsubscribe:From; > b=MmI/E0AHnIway3V//e0KNbYj06VBWcDKGMlK4yA+tPGmgCAnje4NwZM9YXbZk/hc7 > FKM8O1RRkfUhC6iCUHMQa28XK4Nr9+45G/Yxl7Tgr8h6qt1B/1myOCLS8Mb+4XSwpm > CuShRI812x7GkCWVqpLoRBKwq4CP8j8BdDgN4rmrUF18Mdh0J/kkccV13dJvG9xapB > XzUkpqcJICWNyQ/1+GY59VEISP3EBQxUzg6Qkd6a4BXkPKNPCRzVUVM0irvQ0nLi8Z > nAKnV7iutn5nKMXOkEfX5K+8HuFm2Ixd1cWnSIfPY7gd0WK0DyjLVgsZIINA6Hnwt5 > 9fABm1Dsr6YeQ== > Received: from mail.timebrain.org (localhost [127.0.0.1]) > by mail.timebrain.org (Postfix) with ESMTP id C912FC0082 > for <ourlist(a)list.timebrain.org>; Fri, 21 Apr 2023 22:34:11 +0200 > (CEST) > DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=demonetize.it; > s=201907; t=1682109251; > bh=799sMT9Q1QA5X8QRdz/ErDUnITC5MNct/qLMzA5zPSA=; > h=Date:From:To:Subject:In-Reply-To:References:From; > b=KKp8OdYRcEStg4A3qhDgKm4fJQg8U6xPL9w1jbcNJ3BozX8QKqg3NqVC6cbcptHtr > 9tUzsc1WBCYy1UHH7UOCFXowfNtRu+KlvT8YpBNeGgsa12nZ4Ljhw7IRuENcp1sqyj > tnZWWRW8T+wcsJlftOhcCudT59gq1LilZIEPpDNGJ63jgJIX5838IBaz2cXZyHQAWd > XMF6uTz/xc5sRutPHWOUtRETHySK0PEI59cpkRz1UvHwDu1opliv4ILZmR4BW32T6a > OeK06uv6uhRfH8Gc420zhkp+tYSgUc28Z4G93uDC12MypmKshnsZiR52MUFZp1JM8X > eJGEpnGP7xHew== > Received: from [IPv6:::1] ([2a02:560:4ca5:ea00:5c9f:6282:e0ec:582]) > by mail.timebrain.org with ESMTPSA > id zuaKLUPzQmSnBQAAMe3UBQ > (envelope-from <sender(a)otherdomain.tld>) > for <ourlist(a)list.timebrain.org>; Fri, 21 Apr 2023 22:34:11 +0200 Both this and all other incoming Received: headers are removed from posts to anonymous lists beginning with Mailman 3.3.4. > Date: Fri, 21 Apr 2023 22:31:08 +0200 > To: Ourlist Ourtown <ourlist(a)list.timebrain.org> > User-Agent: K-9 Mail for Android > In-Reply-To: <a8c92d51-66c2-2588-f00c-31146bee2f54(a)timebrain.org> > References: <3e35f420-a766-095e-b79a-afb8e795f011(a)timebrain.org> > <a8c92d51-66c2-2588-f00c-31146bee2f54(a)timebrain.org> > Message-ID: <7AB6FFA2-BDA7-4484-BF14-4CF512A4B8E8(a)demonetize.it> > MIME-Version: 1.0 > Message-ID-Hash: 7IYNX33ESBTJZ3M4FGHGGVDBTZ3HGL2B > X-Message-ID-Hash: 7IYNX33ESBTJZ3M4FGHGGVDBTZ3HGL2B > X-MailFrom: sender(a)otherdomain.tld X-MailFrom: headers are also removed as of Mailman 3.3.4. > X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; > emergency; loop; banned-address; member-moderation; > nonmember-moderation; administrivia; implicit-dest; max-recipients; > max-size; news-moderation; no-subject; suspicious-header > From: Our List <ourlist(a)list.timebrain.org> > X-Mailman-Version: 3.2.1 > Precedence: list > Reply-To: Ourlist Ourtown <ourlist(a)list.timebrain.org> > Subject: [Ourlist] Re: whatever was the topic > List-Id: Our List <ourlist.list.timebrain.org> > List-Help: <mailto:ourlist-request@list.timebrain.org?subject=help> > List-Post: NO > List-Subscribe: <mailto:ourlist-join@list.timebrain.org> > List-Unsubscribe: <mailto:ourlist-leave@list.timebrain.org> > Content-Type: multipart/mixed; > boundary="===============6841522137146215921==" > > --===============6841522137146215921== > Content-Type: multipart/alternative; > boundary=----F0JANJPGLDOAM8SUMOY3TD9QT0ZRGF > Content-Transfer-Encoding: 7bit > > ------F0JANJPGLDOAM8SUMOY3TD9QT0ZRGF > Content-Type: text/plain; > charset=utf-8 > Content-Transfer-Encoding: quoted-printable -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Mailman 3 Web Application Startup Time or Availability - 502 Bad Gateway and Postorius

by Mark Sapiro

On 5/3/21 1:45 PM, summersan(a)nclack.k12.or.us wrote: > Hello, > > I've been setting up a new Mailman 3 installation earlier this year, and I think things have been going okay so far. > > I've noticed, however, that after a long amount of time passes (for example, a weekend), when I try to visit the local Mailman 3 web application (e.g., example.mailman.site/mailman3/lists/, where it says "Postorius" at the top left corner of the page and shows a list of mailing lists in the body of the page), I sometimes get a 502 Bad Gateway type of error (referenced from my notes). As far as I can tell, this looks like a normal web server (nginx?) error. If I try visiting the Mailman 3 server location again in a web browser shortly thereafter, I still might get a 502 Bad Gateway error. If I wait a while longer (maybe a minute or more?), the Mailman 3 web application appears to load as expected. What is your configuration for accessing Mailman. I gather you are proxying from nginx to something. Is that something gunicorn or uwsgi? You mention gunicorn but this can be confusing as mailman core's REST API uses gunicorn, but that is separate from the web server's wsgi interface to Django. In any case, this issue is probably with whatever nginx is proxying to (gunicorn or uwsgi) and not with Django or Mailman core. > I've tried looking at the gunicorn documentation (https://docs.gunicorn.org/en/stable/index.html) and searching online (including in this Mailman3 mailing list) to see if there's something that can be done to fix this issue. The closest thing I can find for now is advice for something that, while possibly being technologically unrelated, includes the idea of "warmup requests", which makes me think of simply setting up some sort of script to periodically load a page on the Mailman 3 web application in order to keep it more available for visitors (https://stackoverflow.com/a/57056170) That's certainly a possibility and may be a solution. It would be simple enough to set up an hourly cron to do a curl or wget to retrieve example.mailman.site/mailman3/lists/ and see if that helps. > Is there a setting or something in any of the Mailman 3 related programs that could help with keeping the Mailman 3 web application up and running more often without having to resort to making an ongoing, automated request to the Mailman 3 web application? Nothing that I'm aware of, but if so, it would most likely be a gunicorn or uwsgi setting rather than something in Mailman or Django, although it could be that gunicorn or uwsgi is timing out in trying to connect to Django in which case it could be a Django issue, but not one I've heard of. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

Search results for query "sapiro"