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

[MM3-users] Re: nginx configuration on a multitasking server

by David Newman

On 12/10/21 4:48 PM, Mark Sapiro wrote: > On 12/10/21 3:22 PM, David Newman wrote: >> On 12/10/21 12:57 PM, Mark Sapiro wrote: >>> >>> Are you using uwsgi or some other wsgi server. >> >> uwsgi, per the venv and PDF docs. Thanks for the fix. >> >> Regarding the uwsgi_pass docs, would 'uwsgi_pass_header' directives >> replace the 'proxy_set_header' ones in the venv doc? >> >> Looking at the uwsgi doc, it seems they might do different things. > > > If you are using uwsgi and proxy_pass http://127.0.0.1:8000 is working > for you, then I'm satisfied that the docs are OK now and we don't need > to say anything about uwsgi_pass. > > > >> It's not the situation I have to deal with, though. Short of changing >> a long-standing URL, what I'm looking to do is have "/" continue to >> default to roundcubemail, and have users type in longer URLs for MM3 >> and other services. > > > I think you can set the document root to the roundcubemail root and then > set locations for the Mailman destinations as, e.g. > > location /mailman3/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > location /archives/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > location /accounts/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > location /admin/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > location /user-profile/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > > I haven't tried anything like this, so I'm not sure it will work, but I > think so. Update: The above worked fine until MM3 informed a list owner of pending subscription requests, with a URL like this: https://lists.example.com/mailman/admindb/listname and that URL returned a 404 error. Adding a stanza for 'location /mailman/' to the nginx config above clears the 404 error, but Postorius returns "Page not found" with no entry in the web or MM3 logs, and a 200 OK in the Nginx logs. I think the URL is supposed to go to the list page in Postorius. How to configure this so that list owners and moderators get a valid URL for list management? Thanks! dn

3 years, 10 months

[MM3-users] Re: Pck files stuck in out queue

by Lieuallen, Thomas Otis

Mark, There were no apparent permissions problems on templates. I was getting the ‘Cannot connect to SMTP server’ message in mailman.log. I did end up applying the patch to decorate.py and messages went through. I’ve since removed the patch, as I’m still looking for an answer and might as well let it queue up again. The only thing that is making me ponder at the moment is that the list owners setup a template for list:member:regular:footer in postorius. It appears that each list has a copy of that file. The modifications I see in postorius are not in their …/templates/list/<listname>/en/list:member:regular:footer.txt file. Are their modifications stored somewhere else and causing the problem? Thx Tom Lieuallen From: Mark Sapiro <mark(a)msapiro.net> Date: Thursday, February 6, 2025 at 2:22 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Pck files stuck in out queue [This email originated from outside of OSU. Use caution with links and attachments.] On 2/6/25 12:42, Lieuallen, Thomas Otis via Mailman-users wrote: > Running Mailman 3.3.10 > > I have 11x pck files stuck in my out queue. There tends to always be a .bak file as well. If I run ‘ls -l’, the files are continually updated and rotated through, just as fast as I can look. Are old ones being delivered and new ones added or the same ones just being renamed? I suspect the latter and I suspect the issue in that case is probably due to the OUT runner trying to access a template file like list:member:{regular|generic}:{header|footer}.txt and not having permission. See the last two posts in the thread at https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> > I believe they’re all for one list. When I use ‘strings’ on one to get a hint of what’s inside, I see the list members at the bottom (recipients). One of them consistently has ‘!’ before their email address. Not sure if that’s a clue. Just no other reason to suspect that, though. The files are python pickles and `strings` shows lots of stuff. The ! may be something in the pickle that's not part of the email address. The way to examine these files is with the `mailman qfile` command. -- 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://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to lieualth(a)oregonstate.edu

8 months, 3 weeks

[MM3-users] Re: {Spam?} Server name in new account confirmation email

by Meehan, John

Thanks for your replies. From Mark's reply, and looking at django_allauth, the Subject of the confirmation email uses the site name from the django_site db table in brackets, but the URL in the message body comes from the HTTP header. Adding proxy_set_header Host $http_host before the proxy_pass line on the SSL proxy server solved the problem. ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, December 3, 2020 10:25 AM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: {Spam?} Server name in new account confirmation email On 12/3/20 9:26 AM, Meehan, John wrote: > Hi, when someone creates a new account (Sign Up), an email is sent to them to confirm their email address. It has the form below. Does anyone know how I can Caution (External, mark(a)msapiro.net<mailto:mark@msapiro.net>) Sensitive Content, First-Time Sender Details<https://shared.outlook.inky.com/details?id=Y29tbXNjb3BlL2pvaG4ubWVlaGFuQGNv…> Report This Email<https://shared.outlook.inky.com/report?id=Y29tbXNjb3BlL2pvaG4ubWVlaGFuQGNvb…> FAQ<https://www.inky.com/banner-faq/> Protection by INKY<https://www.inky.com> On 12/3/20 9:26 AM, Meehan, John wrote: > Hi, when someone creates a new account (Sign Up), an email is sent to them to confirm their email address. It has the form below. Does anyone know how I can change the server name in the URL (From server.example.com to something else)? I have an SSL proxy server that I want to direct users through. Thanks. - John This message comes from django_allauth. The domains come from the django_site database table. If you have Postorius >= 1.3.3 The Domains view will show you the SITE_ID for the domain and has an `Edit` link the the Django admin UI entry for that site. Otherwise, you can go to the Django admin `Sites` view and see the DOMAIN NAME and DISPLAY NAME for each defined site, and you can edit the domain name. You may also need to adjust the SITE_ID setting in your Django settings to match the site you want. The trick here is the SITE_IDs aren't displayed in the Django admin UI or in Postorius < 1.3.3, and they may not be sequential or start at 1. If you query the database with `SELECT * FROM django_site;` you'll see entries with columns id, domain and name which will tell you the SITE_ID. -- 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://secure-web.cisco.com/1FBkrl8Fna83jeBpMzhcS-TGdx6ALOyBwi0uCPsqGDtm9J…

4 years, 10 months

[MM3-users] Re: content filtering in version 3.1

by Simon Handfield

Thanks for your quick reply, Mark. I see, I've retried without the -l switch and the shell returns without error. The --help switch returns: # mailman shell --help usage: mailman shell [-h] [-i] [-r RUN] [--details] [LISTNAME] positional arguments: LISTNAME The 'fully qualified list name', i.e. the posting address of the mailing list to inject the message into. This can be a Python regular expression, in which case all mailing lists whose posting address matches will be processed. To use a regular expression, LISTNAME must start with a ^ (and the matching is done with re.match(). LISTNAME cannot be a regular expression unless --run is given. Thanks once again, Simon. ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, 12 May 2021 14:22 To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: content filtering in version 3.1 On 5/11/21 8:45 PM, Simon Handfield via Mailman-users wrote: > Hi everyone, > > I'm sorry to resurrect this thread from so long ago but it appeared to provide exactly the answer I was looking for, trying to manage pass_types in 3.1.1 on Ubuntu 18.04. > > GNU Mailman 3.1.1 (Between The Wheels) > > Unfortunately when I run: > > ./bin/mailman shell -l [list address] > > I receive: > > usage: mailman [-h] [-v] [-C CONFIG] > {help,aliases,conf,create,digests,import21,info,inject,lists,members,qfile,remove,reopen,restart,shell,start,status,stop,unshunt,version,withlist} > ... > mailman: error: unrecognized arguments: -l > > Can anyone advise how I can use the -l switch to manage this setting for a list? Older versions of Mailman core did not support the -l/--listspec option for mailman shell. They expected the listname as an argument as in ``` mailman shell list(a)example.com ``` What does ``` mailman shell --help ``` show in your case? -- 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://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… _ [State Library of NSW]<https://www.sl.nsw.gov.au/> Simon Handfield Desktop and Infrastructure Leader simon.handfield(a)sl.nsw.gov.au<mailto:simon.handfield@sl.nsw.gov.au> +61 2 9273 1535 Macquarie Street, Sydney NSW 2000, Australia www.sl.nsw.gov.au<https://www.sl.nsw.gov.au/> This message is intended for the addressee named and may contain confidential information. If you are not the intended recipient, please delete it and notify the sender. Views expressed in this message are those of the individual sender, and are not necessarily the views of their organisation.

4 years, 5 months

[MM3-users] Re: Main daemon process sticks around after forking

by Jérôme Charaoui

Mark Sapiro wrote: > On 8/6/25 18:17, Mark Sapiro wrote: > > On 8/6/25 09:03, Jérôme Charaoui wrote: > > I'm running a (rather large) mailman3 instance on Debian 13 (trixie) > > using the distribution packages. > > To manage the mailman3 daemon, the package installs this systemd > > service unit: > > https://sources.debian.org/src/mailman3/3.3.10-2/debian/mailman3.service/ > > It has been working fine until recently: after a reboot, we noticed > > the mailman3 unit consistently failing to start due to a timeout error. > > I figured out that the timeout was related to the service unit type > > (Type=forking) and the fact that the main/parent process was forking > > subprocesses (and running normally), writing a PID file, but it wasn't > > exiting, so systemd identifies this as an error and aborts the service. > > The master is not supposed to exit. It continues to run and monitor the > > child runner processes and will under some circumstances restart a > > runner that dies. > > Further, our recommended systemd configuration is at > https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-mailman... > and includes Type=forking and this is the first I've heard of an issue > with that. I ended up figuring out the problem by myself: I needed to create a list, and via the web interface it would return a 502 error after a small delay. On the command-line, the "create" operation was hanging forever, never completing. I used strace to check out what the process was doing and saw it was in a loop attempting to get a lock on "/var/lib/mailman3/locks/mta". There were a number of files in that locks directory that also seemed stale, so I stopped the mailman3 daemons, removed all the lock files manually, and started them again. That fixed both creating a new list and the fact that the startup process was not exiting as systemd was expecting. [0] It seems to me like this all might be caused by some code path that will retry forever to get a lock without ever timing out or logging some error. Furthermore, I suspect the stale lock file themselves could have been a side-effect of the extremely frequent OOMs we were suffering from before disabling HYPERKITTY_MBOX_EXPORT, due to scrapers continuously hitting /export/ endpoints. [1] [2] [0] https://gitlab.torproject.org/tpo/tpa/team/-/issues/42255 [1] https://gitlab.torproject.org/tpo/tpa/team/-/issues/41957 [2] https://gitlab.com/mailman/hyperkitty/-/issues/385

2 months, 3 weeks

[MM3-users] Re: Multi-domain oddities in Hyperkitty and Postorius

by Mark Sapiro

On 2/15/23 07:52, Jeremy Stanley wrote: > > Thanks, I'm still doing my best to wrap my brain around how Django > uses database migrations to create sites (seems like a very strange > use of a migration, I'm only accustomed to seeing them applied for > database schema updates). I don't think it does. There are a couple of migrations at django/contrib/sites/migrations, but these are only the initial creation of the model and an update to make the domain field unique. Why do you think it creates sites in this way. > Once I work out how to script site > creation, I'm still not completely finding the explanations I need > for how to map them to domains in Mailman though. > > The Mailman documentation about domains says "Domains are how > Mailman interacts with email host names and web host names" but > doesn't actually go on to say (that I can find anywhere) how it > actually associates them. Mailman core doesn't associate domains with Django sites. Mailman core knows nothing about a web UI. The association between Mailman core domains and Django sites is via Postorius. It doesn't exist in Mailman core. When Postorius sees a new domain from core, it assigns it a web_host based on the current web host accessing Postorius. > I can see in the API docs that a POST to > the domains endpoint will create a new domain with a specific > mail_host FQDN, but there's some association somewhere of that to a > web host (Django site), right? No. The only association is if Postorius is creating the domain in core, vs something else creating it via the REST API, Postorius will assign it a web_host in it's own Domain model, and that web host must be an existing Django site, which is only created via Django. > How is that set or manipulated > through the API? Or is that something which has to be set directly > in Django's data structures instead? Yes, A new site has to be created in Django. Even Postorius doesn't do that. > To recap, on creation of a mailing list server I want to populate it > automatically with multiple lists on different domains and have > dynamic SITE_ID=0 domain guessing performed so that the correct site > name and list filtering is performed depending on which domain name > is used in a URL the client requests. I believe I need to have the > automation perform the following steps: > > 1. Instantiate the Mailman installation and run initial migrations > with SITE_ID=1 in order to avoid the problem mentioned in the docs > about not using SITE_ID=0 until the tables have been populated, then > switch the settings.py to use SITE_ID=0 once done. > > 2. Create the individual sites I need in Django (Mailman web hosts) > by creating and applying database migrations. No. You create the sites via Django, but not by creating and applying database migrations. > 3. Create the individual domains I need in Mailman (Mailman mail > hosts) through its REST API. > > 4. "Somehow" tell Mailman (or Django?) which mail hosts correspond > to what web hosts. Neither Mailman nor Django. It's Postorius which maintains the relationship between Django sites which it calls web_hosts and domains. > As I said, I'm still trying to understand how to make step 2 happen > (Django has a steep learning curve for me), but beyond that I'm > unsure how to do step 4 at all. I can do all of this through the > WebUI of course, and have confirmed that it works as expected when I > do, I'm just trying to work out the automation so that our other > sysadmins don't have to perform these steps by hand the next time we > need to rebuild the server. Step 2. $ django_admin shell ``` >>> from django.contrib.sites.models import Site >>> new_site = Site(id=5, domain='5.example.com', name='display_name') >>> new_site.save() ``` Of course the values are up to you and you can omit the id= to have Django assign the first available.. Once you've done step 2, you need to create a domain in Postorius. Look at the code behind Postorius add new domain. Or you can create the domain in core via REST, but you then have to modify it in Postorius to associate the correct site. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Re: Bulk delivery status change?

by Stephen Daniel

If I run >>> for mlist in getUtility(IListManager): ... print(mlist) ... <mailing list "testlist1(a)chapelwoodhoadev.org" at 0x7f83f593fba8> I get only one list. Permissions? Where are the other lists? On Sun, Nov 10, 2024 at 11:52 AM Stephen Daniel <swd(a)pobox.com> wrote: > OK. Ran the script. No errors while running it, but when I look at the > users through Postorius GUI, they still show as 'Disabled by Bounces' > > ?? > > On Sun, Nov 10, 2024 at 11:42 AM Stephen Daniel <swd(a)pobox.com> wrote: > >> Thanks all! I will use these pronto. >> >> On Sun, Nov 10, 2024 at 11:42 AM Mark Sapiro <mark(a)msapiro.net> wrote: >> >>> On 11/10/24 08:34, Odhiambo Washington via Mailman-users wrote: >>> > On Sun, Nov 10, 2024 at 7:16 PM Stephen Daniel <swd(a)pobox.com> wrote: >>> > >>> >> Mistakes were made, and for while every single outbound email bounced. >>> >> I've fixed the mistakes, but now in my largest and most active email >>> list, >>> >> every single user's delivery status is "Disabled by Bounces". >>> >> >>> >> Is there a way to bulk fix this? Or do I have to go into each user, >>> one at >>> >> a time, and fix them? >>> > >>> > Please see this thread: >>> > >>> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >>> >>> The script in that post does all lists. For a single list see >>> >>> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >>> but note that the command line >>> ``` >>> $ shell -l list(a)example.com >>> ``` >>> should be >>> ``` >>> $ mailman shell -l list(a)example.com >>> ``` >>> >>> -- >>> 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 swd(a)pobox.com >>> >>

11 months, 2 weeks

[MM3-users] Re: Running mailman3 on AWS and dealing with SES email verification

by Mohsen Masoudfar

Thank you Mark, this is really very helpful. I am going to work on the details. It would be breat, if there were a way to set some of this options as default, like DMARC mitigation is default to no, I changed it to unconditionally and replace From to with list address and got good results, but the default is no. How may I changed the default, do that the list owner/creator does not need to update these fields. Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, April 30, 2020 1:15 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Running mailman3 on AWS and dealing with SES email verification [EXTERNAL EMAIL] On 4/30/20 9:25 AM, Mohsen Masoudfar wrote: > Hi, > > This seems to be a very basic question and/or issue, but I could not find a reliable for it: > > Assume a list member with the email address like (just as an example) > joe.student(a)university.edu sends an email to a list, Mailman gets the > email, processes it and would try to send that email to all members > with a sender field as: 'joe.student(a)university.edu'. plus > listname(a)listserver.TLD Are you referring to the envelope sender or to the From: header? The envelope sender will be listname-bounces(a)listserver.TLD or if VERP is enabled, listname-bounces+recipient=recipient.domain(a)listserver.TLD. The From: header will be unchanged from the incoming message. If yo want the From: to be the list, you can apply DMARC "Replace From with list address" unconditionally and the From: will look like From: joe.student via listname <listname(a)listserver.TLD> ... > I found some solution: > > > * Asking the members to add their email to the signature > * manipulating the from field and add the name of the sender as a comment, not that easy, needs some Python code > * manipulating the from files and replacing the @ with something else, not that easy, needs some Python code > * . . . The DMARC mitigations will do these thing for you. > More important: None of these would allow a simple click on the reply bottom to send the email to the original sender. And they will add the poster's original From: address to Reply-To: -- 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

5 years, 5 months

[MM3-users] Re: MTA setup

by Arte Chambers

I'm not sure how to check mailmans shunt queue. I'm not seeing any errors in mailman logs There are several .pck files in Mailman's var/archives/hyperkitty/spool/ I can send email from the server using mail utilities as long as the "from email address" contains the server's domain name. I also notice that in this MM3-Users list the "from" email shows senders(a)emailaddress.com VIA mailman3.org. I'm wondering if I've missed something that would allow my server to behave this way. Thank you, Paul 'Arte Chambers' Robey 502-408-6922 On Sun, Nov 17, 2024 at 11:31 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/17/24 19:32, Arte Chambers via Mailman-users wrote: > > > > Mailman is successfully sending invite emails however user messages sent > to > > the list are not being sent to subscribers. Also in Hyperkitty none of my > > test messages to the list are showing up in the archive. > > > Are there messages in Mailman's shunt queue? Check for errors in > mailman.log. Are there messages for hyperkitty queued in Mailman's > var/archives/hyperkitty/spool/ directory? > > > I am using Postfix with an SMTP relay hosted at Brevo.com (formally > > sendinblue). Brevo's logs show the message getting rejected > > > > > > Log from brevo.com (SMPT Relay) > > Sent on 17-11-2024 21:49:16 > >>From listmember(a)gmail.com > > To listmember(a)gmail.com > > Message ID<CAPesOD1y0fEaG=GFodz=Lgs1m_hqRErPnQcpXCNtKsBbJ= > > BJ7Q(a)mail.gmail.com> > > > > 17-11-2024 21:49:16 > > Sending has been rejected because the sender you used > listmember(a)gmail.com > > is not valid. Validate your sender or authenticate your domain > > > This appears to be something you need to do for the MTA at > smtp-relay.sendinblue.com, or possibly something more is needed in > /etc/postfix/sasl_passwd. > > > #SMPT Relay Brevo > > relayhost = [smtp-relay.sendinblue.com]:587 > > smtp_sasl_auth_enable = yes > > smtp_sasl_security_options = noanonymous > > smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd > > > -- > 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 paul.m.robey(a)gmail.com >

10 months, 1 week

[MM3-users] Re: Mailman REST API not available. Please start Mailman core.

by Christian

That worked. Now on https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-mailman -automatically it says "Pay attention to the config file output above and make sure that you see /etc/mailman3/mailman.cfg there. If the config path is different, you should make sure to create a new config file at /etc/mailman3/mailman.cfg and re-run the command." Well...mailman info yields GNU Mailman 3.3.5 (Tom Sawyer) Python 3.7.3 (default, Mar 23 2024, 16:12:05) [GCC 8.3.0] config file: /opt/mailman/mm/mailman.cfg db url: postgres://mailman:5DqTHnv8hUQSdd@localhost/mailman devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass Should I create a new config file at /etc/mailman3/mailman.cfg ? Lastly, when I ran this command it says "loaded failed failed" (venv) mailman@lists:/opt/mailman/mm$ systemctl list-units | grep -i mailman gunicorn.service loaded active running GNU Mailman web interfaces ● mailman.service loaded failed failed GNU Mailing List Manager Please advise. Thank you. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, February 12, 2025 10:33 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Mailman REST API not available. Please start Mailman core. On 2/12/25 09:24, Christian via Mailman-users wrote: > Running Debian 4.19.316-1 > Python 3.7.3 > > I am unable to start mailman core > > > mailman@lists:~$ /opt/mailman/mm/bin/mailman start > Usage: mailman start [OPTIONS] > Try 'mailman start -h' for help. > > Error: A previous run of GNU Mailman did not exit cleanly > (stale_lock). Try using --force mailman@lists:~$ > > > I try using --force and it did not work. So how do I start it? In Mailman's var/locks directory (maybe /opt/mailman/mm/var/locks/) you will see at least two files. The ones of interest are: ``` master.lck master.lck|<host_name>|<pid>|<random_integer> ``` First verify that pid is not running or if it is, that it's not Mailman's `master` process. Then remove all the files from the var/locks/ directory and Mailman should start. > Bottom line: I would like for Mailman core to start when I reboot the > server. How can this be achieved please? See https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-mailman -automatically -- 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/ LV5WTFTNRZ455KPDESRQHFV67SJ5VOFH/ This message sent to csa(a)web-analysts.net

8 months, 2 weeks

Search results for query "sapiro"