Search results for "Postorius" - Mailman-users

Re: [GSoC 2026] [Feature Proposal] Per-List Backup and Restore Support

by sonika gutha

Thank you Stephen, this is very helpful. I understand that the implementation discussion is better continued on mailman-developers, and that mailman-users is more appropriate for feedback about user experience and feature demand. Your guidance on scope and architecture is especially useful. My current understanding is: - the backup/restore logic should live in Mailman Core - the initial interface should be exposed through the mailman utility - Postorius, if added, would come later as an additional UI - the backup format should be versioned and include metadata such as timestamp and schema compatibility - archives and site-wide web template customizations are out of scope for the first version - subscription preferences and restore permissions need special care I will refine the proposal in that direction and continue the implementation discussion on mailman-developers. Thank you again.

2 months, 3 weeks

[Django] ERROR (EXTERNAL IP): Internal Server Error: /hyperkitty/list/direttivo@catania.linux.it/top-threads

by blackout69

Hello everybody,I received this error message and from that moment the maiilan3 has stopped working.I restarted the following services mailman3 and mailman3-web and everything started working fine.Can you tell me what is the problem my django server has encountered? Internal Server Error: /hyperkitty/list/direttivo(a)catania.linux.it/top-threads DoesNotExist at /hyperkitty/list/direttivo(a)catania.linux.it/top-threads Thread matching query does not exist. Request Method: GET Request URL: https://lists.catania.linux.it/hyperkitty/list/direttivo@catania.linux.it/t… Django Version: 1.11.29 Python Executable: /usr/bin/uwsgi-core Python Version: 3.7.3 Python Path: ['.', '', '/usr/lib/python37.zip', '/usr/lib/python3.7', '/usr/lib/python3.7/lib-dynload', '/usr/local/lib/python3.7/dist-packages', '/usr/lib/python3/dist-packages'] Server time: Ven, 26 Feb 2021 20:10:53 +0100 Installed Applications: ('hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount') Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Traceback: File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 41. response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 187. response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 185. response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/lib/view_helpers.py" in inner 134. return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/mlist.py" in overview_top_threads 196. 'threads': mlist.top_threads, File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py" in top_threads 157. return self.cached_values["top_threads"]() File "/usr/lib/python3/dist-packages/hyperkitty/models/common.py" in __call__ 59. return self.get_or_set(*args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py" in get_or_set 365. return [Thread.objects.get(pk=pk) for pk in thread_ids] File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py" in <listcomp> 365. return [Thread.objects.get(pk=pk) for pk in thread_ids] File "/usr/lib/python3/dist-packages/django/db/models/manager.py" in manager_method 85. return getattr(self.get_queryset(), name)(*args, **kwargs) File "/usr/lib/python3/dist-packages/django/db/models/query.py" in get 380. self.model._meta.object_name Exception Type: DoesNotExist at /hyperkitty/list/direttivo(a)catania.linux.it/top-threads Exception Value: Thread matching query does not exist. Request information: USER: blackout69 GET: No GET data POST: No POST data FILES: No FILES data COOKIES: csrftoken = 'tqNIiLrMWyYNHYhkmnmQfjRdd0AtCeCAAW46VOL24wk2g7Opl5LSZWB2dZ2p79Sb' sessionid = 'brhb9jd3ko9blnluuc6bz3c1627u6h22' META: CONTENT_LENGTH = '' CONTENT_TYPE = '' CSRF_COOKIE = 'tqNIiLrMWyYNHYhkmnmQfjRdd0AtCeCAAW46VOL24wk2g7Opl5LSZWB2dZ2p79Sb' DOCUMENT_ROOT = '/usr/share/nginx/html' HTTPS = 'on' HTTP_ACCEPT = 'text/html, */*; q=0.01' HTTP_ACCEPT_ENCODING = 'gzip, deflate, br' HTTP_ACCEPT_LANGUAGE = 'it-IT' HTTP_COOKIE = 'csrftoken=tqNIiLrMWyYNHYhkmnmQfjRdd0AtCeCAAW46VOL24wk2g7Opl5LSZWB2dZ2p79Sb; sessionid=brhb9jd3ko9blnluuc6bz3c1627u6h22' HTTP_HOST = 'lists.catania.linux.it' HTTP_REFERER = 'https://lists.catania.linux.it/hyperkitty/list/direttivo@catania.linux.it/' HTTP_TE = 'trailers' HTTP_USER_AGENT = 'Mozilla/5.0 (Android 11; Mobile; rv:86.0) Gecko/86.0 Firefox/86.0' HTTP_X_REQUESTED_WITH = 'XMLHttpRequest' PATH_INFO = '/hyperkitty/list/direttivo(a)catania.linux.it/top-threads' QUERY_STRING = '' REMOTE_ADDR = '2.38.155.170' REMOTE_PORT = '39208' REQUEST_METHOD = 'GET' REQUEST_SCHEME = 'https' REQUEST_URI = '/hyperkitty/list/direttivo(a)catania.linux.it/top-threads' SCRIPT_NAME = '' SERVER_NAME = 'lists.catania.linux.it' SERVER_PORT = '443' SERVER_PROTOCOL = 'HTTP/2.0' uwsgi.core = 1 uwsgi.node = b'glugct.catania.linux.it' uwsgi.version = b'2.0.18-debian' wsgi.errors = <_io.TextIOWrapper name=2 mode='w' encoding='UTF-8'> wsgi.file_wrapper = '' wsgi.input = <uwsgi._Input object at 0x7f0e65582f00> wsgi.multiprocess = False wsgi.multithread = True wsgi.run_once = False wsgi.url_scheme = 'https' wsgi.version = '(1, 0)' Thank you in advance -- blackout69

5 years, 3 months

Re: Re-enable member after bouce processed disable

by Henrik Rasmussen

Henrik Rasmussen wrote: > 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. It seems that I was right, however, I need to re-enable all members on a single list who have been disabled due to bounces. Using the `mailman members` command it is possible to list such members, however how do I enable them using either the `mailman shell` command (available) og the mailmanclient (needs first to be installed in the docker container)? Regards, Henrik Rasmussen

4 years, 5 months

Re: Speed up importing mailman2 lists

by Jeremy Stanley

On 2025-02-20 07:15:57 +0000 (+0000), Stephen J. Turnbull wrote: [...] > I've done two massive migrations in the last year. In the first (~20k > lists), the lists were down for maybe two hours, but it took 22 hours > for HyperKitty to populate, mostly in Xapian indexing we realized in > post-mortem analysis. In the second (~1k lists), no perceptible > downtime because they have their own bespoke archiver that has a > list-manager-agnostic API. Our sites didn't have nearly that many mailing lists, but we were migrating from multiple side-by-side MM2 installs for domains hosted on one server to a multi-domain MM3 deployment on another. In our case we did piecemeal outages one domain at a time rather than having one mass migration for everything all at once, and that kept the impact to each individual domain/site minimal. > The trick to zero delivery downtime is that you can configure your MTA > to route to Mailman 3 if the list exists there, if not route to > Mailman 2 if the list exists there, and if not continue to any lower > priority routes. It worked as designed (mops sweat off brow ;-). We > did take Postorius and the Mailman 2 management CGIs and email command > addresses offline for the duration (3 hours in the first case, 30 > mminutes in the second). This is sraightforward if Mailman 2 and > Mailman 3 are running on the same host. Life is more complex if > you're spinning up Mailman 3 in a separate node but it should be > possible. Yes, our downtime included finalizing a warmed rsync over the Internet and waiting for DNS changes to propagate (we tried to time things so that the import occurred in parallel with DNS settling out, even with lowered TTLs it helped some for larger sites). We didn't have a lot of incentive to avoid downtime entirely in that situation, and instead just warned the various communities in advance when we'd scheduled their particular migration for and what they should expect. We relied primarily on delivery deferrals between taking a domain offline on one server and bringing up the imported copy on the other, and just accepted that the associated Web content would be offline during the maintenance window but that posts anyone sent at that time would still make it to the lists once they were back. > I think if you're migrating to HyperKitty you can speed up the > migration by shutting off indexing, and doing that later at the cost > of confusing people who expect the lists to be indexed. I'm not sure > if it's possible to migrate the archives concurrently with accepting > new posts, or maybe to migrate archives in advance and backfill any > posts that arrive during the list migration. And there's no reason > why you can't leave the legacy Mailman 2 archives up for browsing > as a backup for as long as needed. In our case, "as long as needed" is approximately forever, but we did install some redirects in Apache for things like list info pages and archive roots. We drew the line at trying to develop an automated mapping to redirect individual posts in the archives though, which is the main reason we keep the pre-migration pipermail content around, since we'd rather not break random links elsewhere on the Web, e.g. in news articles that link to list discussions. -- Jeremy Stanley

1 year, 3 months

Mailman3 via Docker and NGINX

by brian＠emwd.com

I have Mailman3 installed on CentOS 7 using maxking's docker image. I believe the installation went fine and running "curl http://172.19.199.3:8000/postorius/lists/" produces the correct output. I also will be using exim and nginx with this installation. It seems I am stuck with the nginx setup. I created a sitename.com.conf file in the /etc/nginx/conf.d folder. I have the following inputted there: server { listen 80; server_name `sitename.com`; location /static/ { alias /opt/mailman/web/static/; } location / { include uwsgi_params; uwsgi_pass 172.19.199.3:8000; uwsgi_read_timeout 300; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } } However when I go to http://sitename.com (obviously using an alias here for privacy reasons) I get the default nginx index page. Do I need to add anything to the main nginx.conf file to be able to see my mailman3 installation? Thank you for any assistance, Brian Carpenter

7 years, 5 months

Re: After server upgrade debian 11→12 and reinstalling everything in (venv), I got this error when accessing → mailman3/lists

by Mark Sapiro

On 9/21/25 14:49, Wikinaut wrote: > Do you have a programmatic way to delete n ( n > 20) such entries in Postorius, e.g. via a python script + REST to loop through all lists and perhaps to exclude a few based on a small condition (like a text found in old template and/or list name)? I don't have anything off hand, and in the time it would take me to create one and for you to customize it for your exceptions, you could probably go through well over 20 lists/templates via the web UI. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 2 weeks

Re: Welcome message template errors

by Mark

> On 2024-04-24 03:58, Mark Sapiro wrote: > >> What do you get if you do >> ``` >> sudo -u mailman curl >> https://lists.mydomain.com/mailman3/api/templates/list/mytestlist.lists.myd… >> ``` >> with the template set in Postorius? > ******************* > The welcome message is returned. > > root@hel:~# sudo -u mailman curl > https://LISTS.MYDOMAIN.COM/mailman3/api/templates/list/MYTESTLIST.LISTS.MYD… > Test Welcome message for new subscribers.root@hel:~# ******************* Making progress... I edited settings file again, replacing the domain name with the IP address () POSTORIUS_TEMPLATE_BASE_URL = 'http://12.34.56.78' (no SSL) The URI in the template table now has this. http://12.34.56.78/mailman3/api/templates/list/MYTESTLIST.MYDOMAIN.COM/list… Now, when Mass subscribing a new member, a Welcome email is sent to the new member with the correct Subject and From, but the message is blank.

2 years, 1 month

Re: Integration with spamassassin?

by Thomas Krichel

Peter Chubb via Mailman-users writes > What I'd like is a way for emails that I click 'discard' on in > Postorius, to be submitted to the spamassassin Bayes classifier to > make it more likely similar ones will be rejected in future at SMTP > conversation time. Well anybody who has saved emails classified as spam by spamassassin will have no shortage of sample spam emails. Saving the emails to a Mailman instance will only bring added value if these emails are different from the general spam. All evidence that I have had with spam suggest that spam is sent indiscriminately, i.e. without considering what type of person (or list) is the recipient. Thus I am not sure this is worth implementing given the other resource constraints that the Mailman developers have. -- Written by Thomas Krichel http://openlib.org/home/krichel on his 22224th day.

1 month, 3 weeks

mm3mod: command line moderation tool

by David Bremner

Because we're not running postorius, and the moderate-by-mail change is not available in the older version of mailman3 we're running, I needed a tool to moderate lists from the command line. I found mailman-tools, but wasn't able to get them working with python3, so I started from scratch. Maybe someone else will find it useful https://git.tethera.net/mm3mod.git/about/ It's a work in progress, but I am running the version from that repo in production. Like any program using the REST interface, in principle this has complete administrator access to your mailman site, so you need to to trust both this code and the users you let run it. I do run it in "kiosk mode" via ssh command="/home/listmod/.local/bin/mm3mod" ssh-rsa blahblah in .ssh/authorized_keys. This is more of a keeping-honest-people-honest kind of thing.

4 years, 9 months

Re: Hiding an ML from a site

by Mark Sapiro

On February 7, 2024 1:34:32 PM PST, Odhiambo Washington <odhiambo(a)gmail.com> wrote: >What should I do then? Edit some file? Apply some patch? >It's pretty easy for me to create a DNS record for the same server (IP) for >use with the web host that I'd like to hide. In the Domains view in postorius, you need separate mail hosts. Then you need to change the domain of one of the lists to the 'new' mail host. This implies changing its address which may not be acceptable. Or, you can just live with it as is. Note, I have been without power at my house for almost 3 days now, so I don't have access to all my usual resources. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

2 years, 3 months

Mailman-users search results for query "Postorius"