Search results for "Postorius" - Mailman-users

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, 1 month

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

11 months, 2 weeks

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

4 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.

1 year, 9 months

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, 6 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.

1 year, 11 months

Re: list owner creation

by Mark Sapiro

On 2/21/21 4:15 PM, Brian Carpenter wrote: > On 2/21/21 6:50 PM, Christian Stalberg via Mailman-users wrote: >> If one inadvertently deleted a list owner account, how could one either >> create a new account and make them a list owner -or- make an existing >> account a list owner? Thanks! > > Are you talking about deleting the account via the Django admin > interface or via Postorius? > Yes, the answer depends on what you did and what tools you have available. For example, if you deleted the owner via the Delete button on the page at <https://example.com/mailman3/lists/list.example.com>/members/owner/>, you can add it back on the same page. You need to tell us what you did. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

Question to add "alias" address in list by group

by Stephen J. Turnbull

Pierre Malard via Mailman-users writes: > We must add some (a lot) alias address for members and I don’t find > any indications on doc to do that with « mailman » command. I have no idea what you mean by an "alias address" that can be added for many members simultaneously. There is no concept of "alias" in Mailman, and almost certainly no special command for this. The general way to add a lot of addresses for a single list is the mass add command in Postorius's users tab, or an equivalent script using mailmanclient. If you need to do this at the user level (rather than the subscription level), you will need to write a script for it, and also to update subscriptions if that is what you have in mind. Steve

3 years, 9 months

Rejecting held emails

by Darren Smith

Hello, We recently had a phishing message make it through our spam filters and arrive at a mailing list. The good news is that since it was not from a list member it was in the held message queue. I was able to find the message in the var/messages directory by searching for a keyword in the subject. However, after rejecting the message from Postorius, the message doesn't seem to be removed from the var/messages directory. Is this expected behavior? I know that infosec people won't be too happy about a phishing email sitting around on our disk. (Infosec guys are notoriously paranoid. :) ) Is there some sort of cleanup process that would remove these messages? If not, does this pose an issue where over time disk usage will creep up? This could be a pretty significant problem if that is the case. What do you think, sirs? -Darren

7 years, 9 months

Re: django request error

by eggert＠eehmke.de

I did a fresh installation on another machine, and the problem showed up too. I guess it is a Debian bug. The point is, the last letter of mailman3 in the url gets lost somewhere, so all urls get invalid. I could get this workaround to work: in the apache vhost config: Alias /mailman3/favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico Alias /mailman3/static /var/lib/mailman3/web/static <Directory /var/lib/mailman3/web/static> Require all granted </Directory> <IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! ProxyPass /mailman unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost </IfModule> Note I changed the mailman3 to mailman in the uwsgi line. The static files including the css had to be accessed still under mailman3. Still this is an ugly solution, but my mailing lists work again. If someone finds a clean solution, you are welcome. Will try to create a Debian issue.

4 years, 3 months

Mailman-users search results for query "Postorius"