Search results for "Postorius" - Mailman-users

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, 8 months

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

8 years, 11 months

Re: How to subscribe members without sending unsubscribe message

by Flo

On 9/15/25 14:25, Mark Sapiro wrote: > On 9/15/25 14:11, Flo via Mailman-users wrote: >> Hi, >> >> I need to remove subscribed members without sending them an >> unsubscription message. Despite of my research I haven't figured out >> how to do this using the GUI. > > With Postorius, you can do it by first setting the list's Automatic > Responses -> Send goodbye message to No, and then doing the unsubscribe. > > From the command line, you can use the `mailman delmembers` command > which has options to control the sending of the admin notice and the > goodbye message. > Thank you. I don't why I don't find these things in Postorius easily? Flo

10 months, 3 weeks

Customizing Postorios web templates

by Stefan Bethke

Hi, I have two list servers that I would like customize the web pages for, specifically I need to add some legal information to the footer, and I might want to apply some light branding to the site. I can't find any hints on how to do that, maybe I'm looking in the wrong place? If Postorious does not currently allow that outright, it seems I would need to fork mailman/postorious, replace templates like https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/templates/…, and build the package myself. Is this assessment correct? If so, would there be interest in adding a feature to define some blocks that can be overridden more easily, especially during deployment and without having to build custom Python packages? Stefan -- Stefan Bethke <stb(a)lassitu.de> Fon +49 175 3288861

5 months, 2 weeks

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, 3 months

Help with Configuring Mailman3 for Multiple Mailing Lists on a Single Server

by peterrflores＠hotmail.com

Hello Everyone, I’m currently working on setting up Mailman3 on a server to manage several different mailing lists for a project. I’ve successfully installed Mailman3 and Postorius, and I can create and manage individual mailing lists through the Postorius web interface. However, I’ve encountered a couple of challenges that I need assistance with: Multiple List Management: I’m trying to configure Mailman3 to handle multiple lists for different projects. While individual lists seem to work fine, I’m unsure about best practices for managing multiple lists on a single server. Specifically, how can I ensure each list has its own distinct set of configurations (e.g., moderation settings, privacy settings, and membership options), but still manage them efficiently from the same instance of Postorius? Integrating with External Services: We plan on integrating Mailman with a few external services for better automation, including a CRM system and a custom registration platform. Does Mailman3 provide APIs or any documentation that can help with integrating mailing list functionality into other applications? If anyone has experience with these types of integrations, any advice or resources would be greatly appreciated. I checked this: https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ https://www.igmguru.com/machine-learning-ai/generative-ai-training https://lists.mailman3.org/mailman3/lists/test2.mailman3.org/ Security and User Privacy: Since we’ll be dealing with sensitive data from subscribers, what security measures should we consider to ensure the privacy and safety of the mailing list subscribers? Any suggestions regarding encryption, access control, or secure email practices within the Mailman ecosystem would be helpful. I’d greatly appreciate any insights or advice the community can offer. Thanks in advance for your time!

1 year, 8 months

Re: Help with Configuring Mailman3 for Multiple Mailing Lists on a Single Server

by Mark Sapiro

On 11/28/24 12:01 AM, peterrflores(a)hotmail.com wrote: > > Multiple List Management: I’m trying to configure Mailman3 to handle multiple lists for different projects. While individual lists seem to work fine, I’m unsure about best practices for managing multiple lists on a single server. Specifically, how can I ensure each list has its own distinct set of configurations (e.g., moderation settings, privacy settings, and membership options), but still manage them efficiently from the same instance of Postorius? This is how things work. See for example https://mail.python.org/mailman3/?all-lists - each of those lists has its own settings. There are also `unadvertised` lists on that server, e.g. https://mail.python.org/mailman3/lists/capi-sig.python.org/ > Integrating with External Services: We plan on integrating Mailman with a few external services for better automation, including a CRM system and a custom registration platform. Does Mailman3 provide APIs or any documentation that can help with integrating mailing list functionality into other applications? If anyone has experience with these types of integrations, any advice or resources would be greatly appreciated. Mailman core provides a REST API for list management. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… - this interface is only protected by a user name and password, so it is normally only available via `localhost` as wider access is not very secure. Postorius uses this API via the python bindings described at https://docs.mailman3.org/projects/mailmanclient/en/latest/ > Security and User Privacy: Since we’ll be dealing with sensitive data from subscribers, what security measures should we consider to ensure the privacy and safety of the mailing list subscribers? Any suggestions regarding encryption, access control, or secure email practices within the Mailman ecosystem would be helpful. A list can be anonymous id desired which means the sender of a post is not identified in any headers of the distributed email. HyperKitty archives can be private, i.e. accessible only to list members. The membership list can be restricted to only list owners/moderators or available to list members as well via list settings. There is currently no support for encrypted email. Full access to a list's settings and other info via Postorius is limited to logged in users who are either a `superuser` or an owner of the list. moderators have more limited access, list members may be allowed to see the membership. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

Re: Easiest way to install a new mailman3 deployment?

by Mark Sapiro

On 1/5/21 3:37 PM, Ruth Ivimey-Cook wrote: > > I have only split mailman in two: mailman-core with the email-related > parts, and postorius for the UI. As yet, although Hyperkitty "works", I > haven't addressed the fact that mails get archived in folders on the > email host and so (for me) hyperkitty can't see them. Ideally, they > would be on the postorius/hyperkitty host, or possibly network shared The emails that get archived in folders on the Mailman core host are archived by the 'prototype' archiver, not by HyperKitty. HyperKitty archived emails are in tables in Django's database. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

Re: Help needed to create filters that were working in Mailman 2.

by Mark London

Mark - I'm an idiot. I previously had modified some of the text in Postorius to be shorter, and somehow had deleted the Accept feature! I hope not to ever have to upgrade our email server ever again. It took much years off my life. In any event, here's one of the text that I modified to be briefer. Perhaps you can see why I shortened it. Besides which, who goes on vacation these days, and disables emails from any source? I have users that literally have tens of thousands of unread email. They don't bother to delete it. Grrr... - Mark help_text=_( 'Set this option to Enabled to receive messages posted to this ' 'mailing list. Set it to Disabled if you want to stay subscribed, ' "but don't want mail delivered to you for a while (e.g. you're " "going on vacation). If you disable mail delivery, don't forget " 'to re-enable it when you come back; it will not be automatically ' 're-enabled.' On 6/21/2023 4:21 PM, Mark Sapiro wrote: > On 6/21/23 11:36 AM, mrl(a)psfc.mit.edu wrote: >> I'm using version 1.3.8 Which I installed on Ubuntu 22 on April >> 18. I'm guessing this feature was installed in 1.3.9? > > The attached screenshot (which may not make it to the list but should > be in your direct copy) is from Postorius 1.3.8 installed via pip. If > you don't see this, possibly you have installed the Debian/Ubuntu > package and this is a Debian issue. >

3 years, 1 month

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, 4 months

Mailman-users search results for query "Postorius"