Search results for "Postorius" - Mailman-users

Re: Unable to update templates

by Mark Sapiro

On 5/27/25 18:54, Mark wrote: > > However when I update the template, the databases are updated correctly > but the Welcome message is still sent with the old template content. > > mailman.templates > mailmanweb.postorius_emailtemplate > > Additionally, if I delete the template and create a new one the old > content still gets sent. > > I cannot find where this content is written or is being cached. The content is stored in the mailmanweb.postorius_emailtemplate table. As far as Mailman core and Postorius are concerned, that's the only place. I'm guessing, but my guess is it's cached in your wsgi server. I.e., upon initial creation an entry is made in the mailman.template table with a uri like https://example.com/mailman3/api/templates/list/list.example.com/list:user:… and when Mailman core wants the template, it gets that uri which I'm guessing is then cached in the wsgi server. Then, if the content is changed, the GET returns the old cached value instead of getting the new value from Postorius. If the template is deleted, the mailman.template table entry is deleted and at that point Mailman core will get the template from the file system following it's normal search rules, but if the template is recreated in Postorius, a new table entry is made with the same uri which may still get a cached template from the wsgi server. If this is correct, restarting mailman-web or whatever controls the wsgi server should fix it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[Django] ERROR (EXTERNAL IP): Service Unavailable

by dancab＠caltech.edu

I've imported a list from Mailman2 and had the owner send a message for testing purposes. His message are moderated per the list configuration. The message is delivered to Mailman3 and shows that it's being held. However if we attempt to view the message in Postorius web UI then an error is thrown. In the web interface the error is simply "Mailman REST API not available. Please start Mailman core." But Mailman Core is running and we can do other functions just fine. Our superuser account receives a much more detailed message with the subject below. [Django] ERROR (EXTERNAL IP): Service Unavailable: /postorius/lists/cpa-announcement.caltech.edu/held_messages Does "Service Unavailable" mean I'm missing something in the configuration? Thanks for your help. ---- Dan Caballero

5 years, 8 months

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

by summersan＠nclack.k12.or.us

Hi Mark, Thank you for your quick response! When setting up Mailman 3, I went through much of this "how to" guide here: https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10. As far as I can tell, my current setup appears to be proxying from Nginx to Gunicorn, according to the related Nginx and mailman3-project-specific Gunicorn config files. Specifically, I checked the local address:port being used in the Nginx file and compared that to the mailman3-project-specific Gunicorn bind address. It looks like I might have "separated out" the REST API to a different server block in the Nginx config file, so I think I'm looking at the correct server block with this conclusion. For what it's worth, I don't recall this type of "slow first visit startup" issue happening in the past when using web applications with uwsgi, and I've had the opportunity to use uwsgi with a variety of programs. I think Gunicorn is fairly new to me. I do, however, remember that something like this might have happened in the past when using Passenger (https://www.phusionpassenger.com/) a long time ago, but that might have been setting related on my part. Okay, thanks for the encouragement about the potential solution to periodically accessing the related "example.mailman.site/mailman3/lists/" type location (from my earlier email). Wanted to check on that and was also hoping that there might be some setting I'm missing in the overall Mailman 3 project setup related to the "slow first visit startup" issue. Thank you!

5 years, 6 months

Re: Turn off social logins?

by Abhilash Raj

On Sun, Feb 10, 2019, at 6:54 PM, Nick Wynja wrote: > On 02/10/19 at 08:57, brian(a)emwd.com <brian(a)emwd.com> wrote: > > > "In your `settings_local.py` copy the whole INSTALLED_APPS section from [default settings](https://github.com/maxking/docker-mailman/blob/master/web/mailman… and add/remove the auth providers you want/don't want. Notice the `allauth.socialaccount.providers.<provider>` in the list below." > > Another option, which seems more future-proof, is to strictly remove > the account providers you don't want from INSTALLED_APPS rather than > defining INSTALLED_APPS locally. > > First, you have to access INSTALLED_APPS by importing settings into > settings_local.py: > > ``` > from settings import * > ``` > > Then, you can set INSTALLED_APPS to everything it already is minus the > social providers: > > ``` > INSTALLED_APPS = [a for a in INSTALLED_APPS if not > a.startswith('allauth.socialaccount.providers') and not > a.startswith('django_mailman3.lib.auth.fedora')] > ``` > > This way if Postorius ever adds any apps you won't need to update your > local settings. Anyone see any downsides to doing it this way? Please don't do that, it will create a circular import since settings_local.py is imported by settings. Postorius (actually, allauth) adding more providers won't affect the INSTALLED_APPS list, which is a static setting defined in the container images. Unless the image changes that list, it won't affect you. Having the list customized is actually good for you, since there is some extra configuration required for adding a new provider, so you don't want something to just show up without you knowing. -- thanks, Abhilash Raj (maxking)

7 years, 9 months

Re: Mailman upgrade results in page not found error

by Abhilash Raj

On 11/3/22 18:30, Andrew Hodgson wrote: > I think this is a problem with the new urls.py I downloaded, what is the best way to restore the old behaviour of having https://lists.hodgsonfamily.org going to the correct place? > urlpatterns = [ > path( > '', > RedirectView.as_view(url=reverse_lazy('list_index'), permanent=True), > ), > path('mailman3/', include('postorius.urls')), You _probably_ had DOMAIN/postorius as your URL? If that's the case, replace the 'mailman3/' above with your old 'posotorius/' in your new urls.py. That should fix the problem you are having with 404 because you browser probably remembers the old URL and tries to auto-redirect root path to /postorius. -- thanks, Abhilash Raj (maxking)

4 years

Post-installation documentation?

by Stephen J. Turnbull

David Newman writes: > I am looking for a high-level "do these steps next to get a list > working" document rather than an API command reference. There's no such documentation. "Get a list working" depends on what you mean by "working". The basic answer is 1. Install Mailman 3 suite. 2. Log in to Postorius as an admin user and create the list. After that, it's case-specific. > - why do the venv docs and admin FAQ give different nginx configs for > the reverse proxy? Because the FAQ is providing a short snippet to solve a specific problem, the venv docs provide what I guess is somebody's full working config. Setting up a Mailman server is complex; usually any example you see in the docs is somebody's "works for me" configuration. > - Does the 'Secret_Hyperkitty_API_Key' need to go anywhere else besides > /opt/mailman/mm/mailman-hyperkitty.cfg? It needs to match MAILMAN_ARCHIVER_KEY in HyperKitty's settings.py. There are a couple of reasonable ways to organize HyperKitty and Postorius configs, I'm not sure where the appropriate settings.py would be on your server. > - For Django (presumably in /etc/mailman3/settings.py, but the docs > don't say), what values to use with Postfix to set up the email back end? The answer is "that depends on your mail environment". As far as I know, normally it just works with the default settings, but if your Postfix requires secure, you need to set that up: https://docs.djangoproject.com/en/3.2/ref/settings/#std:setting-EMAIL_USE_T… and possibly the following 3 or 4 variables if authentication is needed. There was a thread on this a couple of weeks ago.

4 years, 11 months

Re: installing a new instance of mm3

by Mark Sapiro

On 10/22/21 6:37 AM, Christian Stalberg via Mailman-users wrote: > Is this document that Brian Carpenter wrote still valid? > > https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 As Steve said, it should be. > Brian installed my instance. Now its broken. My lists are down. I'm getting > nowhere with diagnostics and troubleshooting (which was easier with mailman > 2). What's broken? Postorius, Hyperkitty, mail delivery, all of them? Do you find any clues in the logs at /opt/mailman/mm/var/logs/? Particularly mailman.log for core and mailmansuite.log for Postorius and Hyperkitty. We will try to help if we have information to help identify the problem. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

Re: hyperkitty won't list more than 5 posts and shows empty grey Activity Summary box

by Barry Warsaw

On Aug 9, 2017, at 16:00, Abhilash Raj <maxking(a)asynchronous.in> wrote: > Can this be done using the REST API? If not, maybe we should do that so that > Postorius can take of the periodic tasks? It certainly could. Right now you can do effectively `mailman digests —send —bump` through the REST API, so if you wanted to leave the periodicity to Postorius, that would work right now. If we added the —periodic option to the CLI, then we should also add it to the REST API. The one thing is that —periodic and —send should be mutually exclusive for both. I’ve updated the issue with those comments. Cheers, -Barry

9 years, 3 months

Re: [Mailman-Developers] Mailman Core 3.3.1rc1 release

by Brian Carpenter

On 4/10/20 3:31 AM, Abhilash Raj wrote: > Hey Everyone, > > I have just released Mailman Core 3.3.1rc1. The final release is scheduled for next week, 17th April. > > This release includes support for bounce processing, which had been lacking in Mailman 3 until now. So, after upgrading to this release, you will notice bounce related notifications from Mailman 3 being sent out to list owners if the list has bounce processing enabled (which, most list do by default). > > Postorius changes for new bounce processing options are coming out soon, I would like the current head to bake in a little longer since it went through bootstrap 4 upgrade recently. Expect it to be out in about a month. If your users would really care about bounce processing being enabled and not being able to tune threshold and notification parameters in the web interface, you might want to wait for Postorius's next release before upgrading. > > It also exposes all the remaining attributes of MailingList via REST API, so Postorius can expose them in the Web Interface. This should finally make all attributes of a MailingList manageable via Web Interface, without having to access command line interface. > > There has also been a whole lot of bug fixes. A full list of changes can be found at: > > https://mailman.readthedocs.io/en/latest/src/mailman/docs/NEWS.html#rc1 > > The release is available via PyPI: > > https://pypi.org/project/mailman/3.3.1rc1/ > > To install this release via pip, you can run: > > $ pip install --upgrade --pre mailman > > Note the `--pre` flag because this is a pre-release. > > If you can, I encourage you to try this out with your environment and report any major breakage to us. We have been running this code on the server hosting this list, so it has already seen some testing, but it is always nice to have some more. > > If there aren't any major breaking changes reported, the final release will be identical to this one. > Well this is exciting and timely. I plan on upgrading Mailman core on my development server today to 3.3.1rc1 so we can start implementing the new REST API elements into Affinity. I will keep you posted via Gitlab if we run into any issues. Thanks! -- 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, 7 months

Re: Database running VERY hot

by Abhilash Raj

On Fri, Mar 9, 2018, at 9:11 AM, Darren Smith wrote: > Abhilash, > > Thanks for the response. I'm going over to lists.fedoraproject.org to > see if they have done any fine tuning.> > Our installation is at https://lists.rootsweb.ancestry.com, if you're > interested in seeing an installation with over 32,000 mailing lists. > As I mentioned, it was big enough that we have disabled the browse > experience in Postorius and are hosting our own pages for browsing to > a new list. Please keep us posted if you have other unique challenges for operating this high number of lists, other than this particular one. We'd love to be able to support high number of lists efficiently :) > If we get time to work on this we will certainly create a pull > request. :)> > > On Thu, Mar 8, 2018 at 11:49 AM, Abhilash Raj > <maxking(a)asynchronous.in> wrote:>> Hi Darren, >> >> >> On 3/8/18 9:43 AM, Darren Smith wrote: >> >>> Hello all, >>> >>> We had an old installation of Mailman 2.1 across three servers >>> with over>>> 32,000 mailing lists on them. Due to circumstances beyond my >>> control, we>>> had to shut them down and quickly set up Mailman 3 on a new server.>>> >>> We have Mailman3 set up on a single server this time, as we were >>> having>>> problems with a 3-server setup and Hyperkitty and archives. Long >>> story>>> short, it is up and running, and our users are starting to come >>> back.>>> >>> However, we do not have very many users hitting Postorius and >>> Hyperkitty>>> yet, and we are seeing a distressing number of 504 gateway >>> timeouts.>>> >>> We noticed that there is a significant number of queries to the API>>> whenever hitting Postorius's front page to load the mailing lists, >>> and then>>> on every load. It looks as if it makes a single call to the API >>> to get>>> information about a single list, and does this 10 times - once >>> for each>>> list - to render the page. This gets much worse when users set the >>> view to>>> 200 per page, as they are inclined to do with 32,000 mailing >>> lists...>>> >>> What we've done, actually, is to override the front page and >>> point the>>> users to a different set of static pages where we have all of our >>> lists>>> categorized and searchable, and when they find the list they are >>> looking>>> for, we have a link back to postorius. It has taken a lot of the >>> stress off>>> of the server. >>> >>> However, I still see where the database at times can run VERY hot.>>> >>> We have set up this server to run with PostgreSQL. When I do a ps >>> aux |>>> grep postgres, I find a lot of processes that have been spawned >>> to take>>> care of mailman - a dozen or so. However, one of the threads is >>> taking up>>> about 85% of the load, another thread about 14%, and little >>> dribbles here>>> and there from the rest of the threads. >>> >>> Here are the questions: >>> >>> 1) Has anyone run into problems like these? I would think that >>> maybe this>>> is an issue having so many mailing lists, but honestly there >>> aren't that>>> many people using the system yet. It is going to ramp up as the >>> users>>> realize that we are live again, but we aren't getting that much >>> traffic.>> >> I can say that in general, Postorius doesn't really optimize REST API >> queries and so loading a single page can sometimes make things bad.>> >> Currently, the largest installation of Mailman 3 that we know of >> runs at lists.fedoraproejct.org and the administrators of the list >> would know how well does our Web UI scale.>> >> However, I don't think we have anyone actively working on trying to >> fix this particular issue. Pull Requests and fixes are welcome :) >> >>> >>> 2) Is there any configuration that I can set, especially with >>> regards to the database, so that it can be used more efficiently >>> and not throttle through one or two threads?>> >> There isn't any configuration that would change how databases are >> used in Mailman Core. Django *may* have some, but I don't know about >> any of them of the top of my head.>> >> thanks, >> Abhilash -- Abhilash Raj maxking(a)asynchronous.in

8 years, 8 months

Mailman-users search results for query "Postorius"