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

[MM3-users] Re: HyperKitty/Mailman3 issues

by Florian Schulze

On 22 Nov 2018, at 19:53, Mark Sapiro wrote: > On 11/22/18 2:58 AM, Florian Schulze wrote: >> Hi! >> >> I tried setting up Scheduled Tasks as described in >> <http://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required> >> >> but the "runjobs" command can't be found. I see the hyperkitty and >> mailman commands when using "help". > > > Does "help" show a list under [django_extensions] including runjob and > runjobs? > > Is 'django-extensions' in the list of INSTALLED_APPS in your Django > settings? That was the issue. Thanks! >> The "qcluster" service is working. >> >> Using Django 2.1.1 and HyperKitty 1.2.1. >> >> Maybe related to that, I have two issues with archives. >> >> 1. Changing the archiving setting in the Web-UI to something else >> than >> public seems to have no effect. The already archived messages are >> still >> accessible in public. > > > This is related. It is one of the "daily" jobs that updates this. Note > that changing to "private" will require login after the "daily" jobs > run, but changing to "do not archive" will leave the existing archive > accessible. After manually running the daily job, the archive is now private. >> 2. Related to 1., how can I remove a list archive without affecting >> other lists? > > > There's no easy way. For the "prototype" archiver, the archives for a > list are in var/archives/prototype/listname(a)example.com/ and that > directory can be removed, but that doesn't affect HyperKitty. > HyperKitty's archives are in the Mailman database and multiple tables > are involved. > > One could try just removing the row for the list from the > hyperkitty_mailinglist table. That may render the list's archive > inaccessible via the web UI, but I have no idea what would be broken > by > doing this. I hope this will be added at some point. For now I have the archive set to private. Thanks again for the pointers! Regards, Florian Schulze

7 years, 7 months

[MM3-users] Re: Solved Re: after last upgrade I've got a CSRF failed verification

by Guillermo Hernandez (Oldno7)

El 27/10/22 a las 21:39, Mark Sapiro escribió: >> After that the compress part showed errors... but the postorius web >> maintenance was working well except for the CSRF error verification. >> I will trace the compress errors and will try to find the problem later. > > > Do you have `COMPRESS_ENABLED = True` in your settings? If that's not > the issue, it may be in the settings for COMPRESS_PRECOMPILERS While I'm tracing the problem out, this is the configuration I had working and the error it shows after upgrade: <------- snip of settings.py> # COMPRESS_PRECOMPILERS = ( ('text/less', 'lessc {infile} {outfile}'), ('text/x-scss', 'sassc -t compressed {infile} {outfile}'), ('text/x-sass', 'sassc -t compressed {infile} {outfile}'), ) # On a production setup, setting COMPRESS_OFFLINE to True will bring a # significant performance improvement, as CSS files will not need to be # recompiled on each requests. It means running an additional "compress" # management command after each code upgrade. # http://django-compressor.readthedocs.io/en/latest/usage/#offline-compression #### activo compresion 18/12/20 COMPRESS_OFFLINE = True ###COMPRESS_OFFLINE = False <---------- end snip> And below is the error it shows: /usr/local/mailman3 # su -m mailman3 -c "python3 manage.py compress" Traceback (most recent call last): File "/usr/local/mailman3/manage.py", line 10, in <module> execute_from_command_line(sys.argv) File "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line utility.execute() File "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", line 440, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", line 279, in fetch_command klass = load_command_class(app_name, subcommand) File "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", line 49, in load_command_class return module.Command() File "/usr/local/lib/python3.9/site-packages/django/core/management/base.py", line 274, in __init__ raise TypeError("requires_system_checks must be a list or tuple.") TypeError: requires_system_checks must be a list or tuple. -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

3 years, 8 months

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Eggert Ehmke

I have a file /opt/mailman/.bashrc file with this line: source /opt/mailman/venv/bin/activate works quite well with systemd. My service file looks like this: [Unit] Description=GNU Mailing List Manager After=syslog.target network.target mysqld.service [Service] Type=forking PIDFile=/opt/mailman/mm/var/master.pid Environment="MAILMAN_CONFIG_FILE=/etc/mailman3/mailman.cfg" User=mailman Group=mailman ExecStart=/opt/mailman/venv/bin/mailman start ExecReload=/opt/mailman/venv/bin/mailman restart ExecStop=/opt/mailman/venv/bin/mailman stop [Install] WantedBy=multi-user.target Eggert Am Donnerstag, 20. Oktober 2022, 08:38:05 CEST schrieb Mark Sapiro: > On 10/19/22 21:23, Stephen J. Turnbull wrote: > > Onyeibo Oku writes: > > > Mailman starts well from virtual environment though, ... but systemd > > > doesn't replicate that success. > > > > systemd doesn't know anything about venv. If it's possible to source > > (not call as a command!) the venv bin/activate script via systemd, > > that should fix it. If not, we'll have to figure out what it is that > > the venv provides that the current systemd config does not. I would > > guess that after sourcing the venv's bin/activate > > Our suggested systemd script at > https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-mailman > -automatically has > > ExecStart=/opt/mailman/venv/bin/mailman start > ExecReload=/opt/mailman/venv/bin/mailman restart > ExecStop=/opt/mailman/venv/bin/mailman stop > > /opt/mailman/venv/bin/mailman should work whether or not a venv is active. > > Judging from the traceback, Onyeibo Oku's /opt/mailman/venv/bin/mailman > is quite different from mine which is just > ``` > #!/opt/mailman/venv/bin/python3 > # EASY-INSTALL-ENTRY-SCRIPT: 'mailman==3.3.5','console_scripts','mailman' > __requires__ = 'mailman==3.3.5' > import re > import sys > from pkg_resources import load_entry_point > > if __name__ == '__main__': > sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0]) > sys.exit( > load_entry_point('mailman==3.3.5', 'console_scripts', 'mailman')() > ) > ``` > What is yours? and can you start mailman as the mailman user with > ``` > /opt/mailman/venv/bin/mailman start > ``` > without activating the venv?

3 years, 9 months

[MM3-users] Re: Help with fresh debian install

by Mark Dadgar

Thanks for the al the help - much appreciated! Mailman3 is a HUGE step up from 2.1.x. Running the commands as the correct user solved my issues. Specially, I ran the import21 command as the “list” user (created by the debian/ubuntu package) and the hyperkitty import command as the “www-data” user. I had to add login shells to the passwd entries for those users to make it happen as they get installed with nologin. I imported a 24G archive inbox and something went wrong along the way - the archives for many months consist of just a single identical thread. Re-running the import results in the following in just a few seconds: www-data@mail:/tmp$ python /usr/share/mailman3-web/manage.py hyperkitty_import -l trackjunkies(a)pdc-racing.net /backups/trackjunkies.mbox Importing from mbox file /backups/trackjunkies.mbox to trackjunkies(a)pdc-racing.net Computing thread structure Synchronizing properties with Mailman Warming up cache The full-text search index will be updated every minute. Run the 'manage.py runjob update_index' command to update it now. Any thoughts on how I can re-run the full import to make sure that all the archives are present? Thanks! - Mark ----- mark(a)pdc-racing.net | 408-348-2878 > On Oct 3, 2019, at 9:25 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 10/3/19 5:17 PM, Mark Dadgar wrote: >> >> I brought up a fresh install of Mailman3 via the current Debian package alongside my current 2.1 setup (installed and updated from source since 2002) on Ubuntu 18.04 LTS. >> >> Importing lists from 2.1 has been a real problem. >> >> I am trying to import a list with no archives to keep it simple while I prove out the process. If I run the mailman import21 comment as my user, I get the following errors: >> >> — >> mark@mail:/tmp$ mailman import21 announce(a)pdc-racing.net ./announce-config.pck >> Traceback (most recent call last): >> File "/usr/bin/mailman", line 11, in <module> >> load_entry_point('mailman==3.1.1', 'console_scripts', 'mailman')() >> File "/usr/lib/python3/dist-packages/mailman/bin/mailman.py", line 94, in main >> initialize(config_path) >> File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 189, in initialize >> initialize_2(propagate_logs=propagate_logs) >> File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 152, in initialize_2 >> mailman.core.logging.initialize(propagate_logs) >> File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 157, in initialize >> _init_logger(propagate, sub_name, log, logger_config) >> File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 110, in _init_logger >> handler = ReopenableFileHandler(sub_name, path_abs) >> File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 50, in __init__ >> self._stream = self._open() >> File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 53, in _open >> return codecs.open(self.filename, 'a', 'utf-8') >> File "/usr/lib/python3.6/codecs.py", line 897, in open >> file = builtins.open(filename, mode, buffering) >> PermissionError: [Errno 13] Permission denied: '/var/log/mailman3/mailman.log' > > > This is the issue. I don't know how the Debian packages do this, but I > recommend having a 'mailman' user that owns everything and running > commands as that user. > > >> Error in atexit._run_exitfuncs: >> Traceback (most recent call last): >> File "/usr/lib/python3.6/logging/__init__.py", line 1945, in shutdown >> h.flush() >> File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 56, in flush >> if self._stream: >> AttributeError: 'ReopenableFileHandler' object has no attribute '_stream' > > > This is due to the prior permissions error. > >> If I run it as root, it runs for a long time but spews a HUGE stream of these errors to /var/log/mailman3/mailman.log: > > > If there are a lot of members to add, that can take a long time. The > current version of import21 has a progress thermometer for this. > >> — >> Oct 03 17:08:48 2019 (19118) Skipping and preserving unparseable message: 1570147727.3029191+80f1cc4d18f54868ad6162e8e41e52567185e983 >> Oct 03 17:08:49 2019 (19118) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1570147728.618866+174175d39c301feab4ebb2aac0a51226334fa54c.pck' >> Oct 03 17:08:49 2019 (19118) Traceback (most recent call last): >> File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 156, in _one_iteration >> msg, msgdata = self.switchboard.dequeue(filebase) >> File "/usr/lib/python3/dist-packages/mailman/core/switchboard.py", line 150, in dequeue >> with open(filename, 'rb') as fp: >> PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1570147728.618866+174175d39c301feab4ebb2aac0a51226334fa54c.pck' > > First, I don't know what these messages are. Normally import21 doesn't > send any mail. I'm guessing it's trying to send 'you are subscribed' > notices to the users, but it shouldn't be doing this. > > All these files should wind up in Mailman's var/queue/bad/ directory > with a .psv extension. You should be able to examine them with the > 'mailman qfile' command. > > Whatever they are, the error comes from virgin runner so import21 should > have actually succeeded. Did it import the list? > > >> It also dumps some mail footer templates into the template directory that are owned by root, which seems … incorrect? > > > It makes a weak effort at converting the list's msg_footer and > digest_footer into MM 3 templates in > templates/list/<list-id>/<list-lang>/. These are owned by root in your > case because you ran import21 as root. > > >> Any thoughts on what’s going wrong here? > > > It looks like this may be an issue with the Debian package, at least the > sending of messages part. > > As for the rest, the Debian package should install stuff as a Mailman > user, perhaps 'mailman' or 'list', and you should be running all > commands as that user. > > -- > 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, 9 months

[MM3-users] Re: Auth question

by David Krantz

On Fri, Mar 31, 2017 at 12:01 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > This is <https://gitlab.com/mailman/hyperkitty/issues/106>. > > I'm not sure what you mean by drop and recreate the databases. You > should just drop the `social_auth*` tables, or if there's nothing in the > database you want, just starting with an empty database should work. Very good! Thank you very much, I got a bit further. The database contained a couple of test lists that I can recreate, so nothing of value. The strange thing was that drop database followed by create database did not yield an empty database in Postgres. I probably forgot a commit somewhere. I got a bit further. The problem with not being an expert on Django is that the configuration of all web frameworks is that is a bit involved. I have no experience of Django outside of this and I just want to get it running in this case. Now I get the following errors in the mailman_web-log, somehow complaining on the url mapping. ERROR 2017-03-31 00:51:31,558 exception 2456 140113416898304 Internal Server Error: /mailman3/lists/ Traceback (most recent call last): [...] File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/template/defaulttags.py", line 458, in render url = reverse(view_name, args=args, kwargs=kwargs, current_app=current_app) File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/urls/base.py", line 91, in reverse return force_text(iri_to_uri(resolver._reverse_with_prefix(view, prefix, *args, **kwargs))) File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/urls/resolvers.py", line 497, in _reverse_with_prefix raise NoReverseMatch(msg) NoReverseMatch: Reverse for 'hk_user_login' not found. 'hk_user_login' is not a valid view function or pattern name. The Django 1.18 points to a Django 1.11rc1, should probably be mentioned. My urls.py (a copy from the docs, I think) from django.conf.urls import include, url from django.core.urlresolvers import reverse_lazy from django.views.generic import RedirectView from django.contrib import admin # Comment the next two lines to disable the admin: #admin.autodiscover() urlpatterns = [ url(r'^$', RedirectView.as_view(url=reverse_lazy('hyperkitty.views.index.index'))), url(r'^mailman3/', include('postorius.urls')), url(r'^archives/', include('hyperkitty.urls')), url(r'', include('django_mailman3.urls')), url(r'^accounts/', include('allauth.urls')), # Django admin url(r'^admin/', include(admin.site.urls)), ] cheers // David

9 years, 3 months

[MM3-users] Re: Random characters in "The results of your email commands" e-mail

by Jeffrey D

Mark Sapiro wrote: > To understand what's going on, We would like to see the complete, raw > response message. Also, the headers of the message sent to the -request > address, in particular the Content-Type: header of the first text/plain > part and its charset param. I didn't check the source headers... Mailman isn't the issue, my mail client (Evolution) is the problem. Messages sent to the -request@ with Subject: help and message body with my mail signature are working fine. I received the expected response from Mailman. Messages sent to the -request@ with Subject: help and empty message body, gives the random characters response. Instead of leaving the body empty, Evolution paste "Cgo=" into the message body. Mailman reply with the expected "No such command: cg0k" and Evolution couldn't decode the message. Long story short, don't use Evolution ;-) Thanks for pointing me in the right direction! Mail headers: Sent message -request@ (with empty body) ===================================== Message-ID: <eaa8bc6bec172bf3e19700959d6f86f637a3d59c.camel(a)domain.tld> Subject: help From: Jeffrey <jeffrey(a)domain.tld> To: test-jeffrey-request(a)domain.tld Date: Mon, 17 Feb 2020 10:54:13 +0100 Content-Type: text/plain User-Agent: Evolution 3.34.1-3 MIME-Version: 1.0 Content-Transfer-Encoding: base64 X-Evolution-Identity: 1f54715bb67ff0bd5b87ec47786956d762aec607 X-Evolution-Fcc: folder://f23e08ef4c9736554f0b631ce301539d32916444/Sent X-Evolution-Transport: 6fd443d2352de0b9c1126fe4334605581b1903c2 X-Evolution-Source: Cgo= Response message ===================================== Subject: The results of your email commands From: test-jeffrey-bounces(a)domain.tld To: jeffrey(a)domain.tld Content-Transfer-Encoding: base64 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: <158193325438.30764.17876047045035004661(a)domain.tld> Date: Mon, 17 Feb 2020 10:54:14 +0100 Precedence: bulk X-Mailman-Version: 3.2.1 X-Evolution-Source: f23e08ef4c9736554f0b631ce301539d32916444 The results of your email command are provided below. - Original message details: From: Jeffrey <jeffrey(a)domain.tld> Subject: help Date: Mon, 17 Feb 2020 10:54:13 +0100 Message-ID: <eaa8bc6bec172bf3e19700959d6f86f637a3d59c.camel(a)domain.tld> - Results: confirm - Confirm a subscription request. echo - Echo back your arguments. end - Stop processing commands. help - Get help about available email commands. join - Join this mailing list. leave - Leave this mailing list. stop - An alias for 'end'. subscribe - An alias for 'join'. unsubscribe - An alias for 'leave'. No such command: cg0k - Done.

6 years, 5 months

[MM3-users] Re: add custom styles to postorius list creation menu

by mhazan＠mandint.org

Le 2022-05-02 17:32, Mark Sapiro a écrit : > On 5/2/22 06:39, Michael Hazan wrote: >> Hello, >> >> When creating a list via postorius, i can see 3 style appear >> (announce, discussion, private). Is it possible to either create a new >> style and add it to that list or modify one of those style ? > > > See this thread > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > Thanks i will look into setting up that plugin, hopefully an easier way to do that can make it's way to the default install. >> Also, coming from mailman2, you could directly set the members post >> moderation action when subscribing, now you can only do it via the >> user menu, is there a way to automate this in mm3 ? > > > I don't understand what you mean here. In MM 2.1 a member had only one > setting - moderated yes or no and if moderated there was a list > setting for the moderation action. There was also a list setting for > whether new members were moderated by default. How were you setting > the new member's moderation when subscribing? > > You are correct that when subscribing a new member, the member gets > the default action for members and different action has to be set in a > separate operation. I don't think this is significantly different from > MM 2.1. Also, can you describe what you mean by "automate this". in MM2.1, if you set the list to moderated and default action to hold posting, you can set a some member to be un-moderated (mod bit off) to automatically allow their posting. In the web interface of MM2.1 there is a checkbox with moderated bit on/off on the member list itself, in the postorius interface for MM3 you have to open each members settings page to access that. For automation, as list owner, upon registering a member (via mass subscription) the possibility to change that ? also the me too/dupe setting for example. Thanks

4 years, 2 months

[MM3-users] Re: hyperkitty failed to create a thread

by Abhilash Raj

On Mon, Feb 11, 2019, at 2:08 PM, Marvin Gülker wrote: > Hi, > > Am 11. Februar 2019 um 13:20 Uhr -0800 schrieb Mark Sapiro: > > I downloaded the February mbox from > > <https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/export/wlug@l…> > > and imported it to a test list with 'django-admin hyperkitty_import and > > see the same issue. > > Here's the Hyperkitty Mbox for my affected mailinglist: > <https://lists.secretchronicles.org/hyperkitty/list/tsc-devel@lists.secretch…> > > Maildir from my local machine as received from Mailman via e-mail: > <https://files.guelker.eu/misc/tsc-devel.tar.gz> > > > Examination of the mbox shows for the first message [...] > > Note the folding of the header and the double angle brackets. > > I can confirm that I see this behaviour for my affected mailinglist as > well. The Message-ID header is broken over two lines with double angle > brackets in the Hyperkitty MBox linked above: > > Message-ID: < > <153582973006.27514.7508703206376217479(a)alexandria.secretchronicles.org>> > > However, the original message as it was delivered by Mailman to me does > not have such a weird message-id header: > > Message-ID: > <153582973006.27514.7508703206376217479(a)alexandria.secretchronicles.org> > > In this message, the header is broken exactly as shown above after the > colon of "Message-ID:". Maybe some problem with parsing long Message-ID > headers, or ones folded over multiple lines? > > With regard to bug reporting on gitlab.com: I already have accounts on a > ton of sites, and at some point I'd actually like to stop creating new > ones all the time... I created an issue on Gitlab for this with this thread: https://gitlab.com/mailman/hyperkitty/issues/216 > > Marvin > > -- > Blog: https://mg.guelker.eu > PGP/GPG ID: F1D8799FBCC8BC4F > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking)

7 years, 5 months

[MM3-users] Re: Importing Mailman 2 Lists apart from Django

by Brian Carpenter

On 4/30/20 11:59 AM, Mark Sapiro wrote: > On 4/30/20 7:59 AM, Brian Carpenter wrote: >> Hello Mailman Users, >> >> Are there instructions on importing a Mailman 2 list into a Mailman 3 >> core installation only? Does the import21 script not need >> Django/Postorius/Hyperkitty? > > import21 requires only Mailman core. > > >> It seems Django is required to import archives I guess because of the >> use of Hyperkitty. How about importing archives without having a Django >> installation? Is that what the prototype archiver for? > > The only current archive import we support is `django-admin > hyperkitty_import` which imports archive .mbox files into HyperKitty. > > The prototype archiver is just a maildir format collection of messages. > > Converting an mbox file to a maildir is trivial. > > from mailbox import Maildir, mbox > mb = mbox('/path/to/mbox', create=False) > md = Maildir('/path/to/maildir', create=True) > for msg in mb: > md.add(msg) > > >> We are getting ready to start working on a custom forum application for >> Mailman 3 (called Empathy) and I am would like to import some mailman 2 >> archives into the development server to work with. > > First you have to decide how Empathy will store messages. Look at > <https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/management/c…>. > This is how HyperKitty gets messages from a mbox and adds them to its > database. It's actually fairly simple - a lot of the code is handling > exceptions due to defective messages. > > Presumably Empathy will have a method for adding a message to the > archive, so importing is just getting messages from the mbox and using > Empathy's method to add it. > Thank you Mark. Your response was very helpful. This should help my developer make some decisions. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

6 years, 2 months

[MM3-users] Re: Archive download - unexpected end of file

by Mark

>> On 3/1/25 13:58, Mark wrote: >> >> I have a MM3 list to whose archive I recently added an mbox file of >> older emails. >> >> Viewing/searching the archive (Hyperkitty) is working fine. >> >> Downloading archives "for the month" or "last 30 days" delivers the >> expected ".mbox.gz" file and those are fine. >> >> However, when I download the "Entire archive" and attempt to gunzip >> that ".mbox.gz" file I get the error: " ... unexpected end of file". ?On 2025-03-01 23:04, Mark Sapiro wrote: > > The process creating the zip for download times out. You can increase > the timeout. If your wsgi server is Gunicorn, see > https://docs.gunicorn.org/en/stable/settings.html#timeout - for uwsgi > see > https://uwsgi-docs-additions.readthedocs.io/en/latest/Options.html#harakiri > > However, it's probably easier to get it in pieces. You can prpbably > get chunks bigger than a month. Look at the URL for a month, e.g. for > Jun, 2005 it will be something like > > https://www.example.com/archives/list/<fqdn-listname>/export/<fqdn-listname>-2025-02.mbox.gz?start=2025-01-01&end=2025-02-01 > > The <fqdn-listname>-2025-02.mbox.gz can be any arbitrary file name. > The start and end parameters determine what's included. E.g. for all > of 2024 > > https://www.example.com/archives/list/<fqdn-listname>/export/<fqdn-listname>-2024.mbox.gz?start=2024-01-01&end=2025-01-01 > > Note that the end date is the first date not included, i.e. the day > after the last date included. Thank you very much Mark, for your detailed advice. Increasing the timeout from the default of 30 seconds to 360 now sees the entire archive downloading successfully. # /etc/mailman3/gunicorn.conf # bind = ['127.0.0.1:8000'] proc_name = "mailman-web" chdir = "/opt/mailman/mm" pidfile = "/opt/mailman/mm/var/gunicorn.pid" accesslog = "/opt/mailman/mm/var/logs/access.log" errorlog = "/opt/mailman/mm/var/logs/error.log" #Added 2025-03-02 to resolve timeout on download full archive. timeout = 360 $ systemctl daemon-reload $ systemctl restart mailman3 $ systemctl restart mailmanweb $ pstree ├─gunicorn───gunicorn ├─mailman-web───mailman-web─┬─mailman-web │ └─3*[mailman-web───{mailman-web}]

1 year, 4 months

Search results for query "sapiro"