Search results for "Postorius" - Mailman-users

Re: MM3 on debian - redirect problem

by Mark Sapiro

On 4/27/20 8:17 AM, Gelpi Andrea wrote: > Hi, > on a debian10 I have mm3 installed via apt-get > > apt-get install mailman3-full > dpkg-reconfigure mailman3 > dpkg-reconfigure mailman3-web > > I have this minor issue > > https://webserver/mailman3 redirects to > http://webserver/mailman/postorius/lists/ > > that doesn't exist. > > The same problem form django admin page to return to lists > > https://website/mailman3/admin/sites/site > > In the upper right corner I have a link to https://webserver/mailman3 > that redirects to https://mailman/postorius/lists/ > > I searched for a redirect but without success. The redirection must be a web server issue. There is a urls.py file probably in the same directory as your django settings - probably /usr/share/mailman3-web/urls.py in your case. You can make a URL like http://webserver/mailman/postorius/lists/ work by adding url(r'^mailman/postorius/', include('postorius.urls')), to the urlpatterns list in the urls.py file. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

Re: Mailman backend maintenance task

by Abhilash Raj

> On Aug 24, 2021, at 8:33 AM, Stephen J. Turnbull <stephenjturnbull(a)gmail.com> wrote: > > Hi, Eugenio, > > I wrote this earlier but am in the middle of moving my office so my > mail has been intermittent. I have been following your discussion > with Abhilash, and he's definitely the expert, especially if you are > using the containers he creates and distributes. But there's some > information here he hasn't mentioned yet. > > Please consider the following discussion to be background that allows > you to understand some of the considerations. I've only run the > Mailman 3 suite with all three running constantly on the same host, so > I have no experience with this kind of issue. > > eugenio.jordan(a)esa.int writes: > >> Our customer is currently using PostGRESQL as backend, and we would >> like to perform some maintenance tasks, namely running vacuum full, >> or at least trying to rebuild hyperkitty_email primary key related >> index. We have been asked on the real impact of putting in place >> such initiative. Though the latter is related to archiving, I >> haven't found a way to stop just Hyperkitty or Django related >> processes other than stopping Mailman's core, hence preventing >> mails addressed to distribution lists from being delivered, could >> you please confirm if I am correct? > > Mailman core can certainly run without either Postorius or HyperKitty. > Controlling Mailman core (moderation, helping users) without Postorius > is annoying, but it can be done. If you stop the HyperKitty process, > what should happen, I believe, is that posts for archiving will > accumulate in the 'archive' queue until HyperKitty is available again. > > It's been a while since I studied this so I could be completely wrong, > but as I understand it HyperKitty and Postorius are not daemon > processes. Rather, they are WSGI applications, which means they are > subprocesses spawned by your webserver, and controlled by it. In > order to keep them from running, you would reconfigure the webserver > to not call those WSGI applications. How that is done is specific to > the webserver and the WSGI module. If you are running from Docker > containers, most likely, you can just stop their containers. Yeah, Postorius and Hyperkitty themselves aren’t daemons, but they run inside WSGI servers like uwsgi/gunicorn which are typically separate daemons than webserver like Nginx which sits in the front. However there are common webserver modules like mod_wsgi (for apache2) which will let you run without managing a separate WSGI server. So, it depends on the setup, you can either just stop the WSGI server or stop the web server. For, containers, the WSGI server (uwsgi) runs in the container and you can just stop the mailman-web container. -- thanks, Abhilash Raj (maxking)

4 years, 2 months

Re: Patch/kludge suggestion and a question on adding accepted addresses

by Mark Sapiro

On 04/24/2017 07:07 AM, David Krantz wrote: > On Sun, Apr 23, 2017 at 11:04 PM, Barry Warsaw <barry(a)list.org> wrote: >> On Apr 23, 2017, at 10:33 PM, David Krantz wrote: > >>> I have another question: In the old mailman you could add accepted >>> senders without adding them to the list. Is that possible in Mailman >>> 3/Postorius? >> >> You do this by creating a "nonmember" subscription for the sender, and then >> setting that member's moderation_action to Action.accept. > > Okay. I see no way of doing that in my instance of Postorius but in > this case it is okay to do it in the command prompt. Yes. There are still quite a few things that aren't yet exposed in Postorius and probably some not yet exposed in the rest API. In these cases you have to resort to mailman shell (aka mailman withlist). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 6 months

Re: Core, Hyperkitty and Postorius releases

by Mark Sapiro

On 5/13/21 2:27 PM, Odhiambo Washington wrote: > On Wed, Feb 3, 2021 at 5:00 AM Abhilash Raj <maxking(a)asynchronous.in> wrote: > >> Hey Everyone, >> >> I am pleased to announce new stable releases for Mailman Core, Postorius, >> Hyperkitty. >> >> These include both new features and bug fixes. Complete change log for >> each components: >> >> Mailman Core 3.3.3: >> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… > > > May I ask if this is a typo? > I am asking because Mailman Core 3.3.4 was announced on Marc 22nd. > So is this new one version 3.3.3 or 3.3.5? The text you are quoting is from the Feb 2 announcement <https://mail.python.org/archives/list/mailman-announce@python.org/message/N…> of the release of Mailman core 3.3.3. Mailman 3.3.4 was released and announced at https://mail.python.org/archives/list/mailman-announce@python.org/message/H… on March 21 and is the current release. There is no "new one". -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

Re: Splitting hosts: mta&core vs postorius

by Stephen J. Turnbull

Ruth Ivimey-Cook writes: > On 6/22/20 6:23 PM, Stephen J. Turnbull wrote: > > By design, Mailman core doesn't need to talk to the Internet or to the > > secure internal network -- Internet functions are delegated to the MTA > > and the webapps, and local configuration is via shell access which in > > principle could be console. > > Sorry, I missed this earlier. I was more or less trying to describe what I thought you were trying to do, and noting that Mailman is designed for it. Thank you for the confirmation. > I am using exim and there is a big benefit when exim can see the > list directory names. Indeed. (I wrote the proof of concept Exim config for Mailman 3 on Debian.) But that's *all* it needs to see. It should be possible to get that information to Exim in some other way, perhaps through a small app that talks to the REST API. If that's generalizable to other MTAs (especially Postfix, but also Sendmail and maybe qmail) it's worth us looking into (and if it's Exim-specific, at this stage I'd say "patches welcome"). This is also the kind of thing that an NFS read-only mount does fine (of course you may not want NFS on a system in the DMZ :-/ ). > However, I find the mailman shell program not very intuitive, and so > would prefer to have the web app for admin purposes. By "local configuration" I mean anything that requires access to the .cfg files or installing code. Anything you can do via Postorius (or soon, via Affinity, hi Brian!) is not local configuration in this sense.

5 years, 4 months

Re: "Something went wrong | Mailman REST API not available. Please restart Mailman core.

by Hirayama, Pat

Ah, thanks for the reply, Mark. Forgot to include Traceback: Traceback (most recent call last): File "/usr/local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 670, in urlopen httplib_response = self._make_request( File "/usr/local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 426, in _make_request six.raise_from(e, None) File "<string>", line 3, in raise_from File "/usr/local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 421, in _make_request httplib_response = conn.getresponse() File "/usr/local/lib/python3.8/http/client.py", line 1347, in getresponse response.begin() File "/usr/local/lib/python3.8/http/client.py", line 307, in begin version, status, reason = self._read_status() File "/usr/local/lib/python3.8/http/client.py", line 276, in _read_status raise RemoteDisconnected("Remote end closed connection without" http.client.RemoteDisconnected: Remote end closed connection without response During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.8/site-packages/requests/adapters.py", line 439, in send resp = conn.urlopen( File "/usr/local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 726, in urlopen retries = retries.increment( File "/usr/local/lib/python3.8/site-packages/urllib3/util/retry.py", line 403, in increment raise six.reraise(type(error), error, _stacktrace) File "/usr/local/lib/python3.8/site-packages/urllib3/packages/six.py", line 734, in reraise raise value.with_traceback(tb) File "/usr/local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 670, in urlopen httplib_response = self._make_request( File "/usr/local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 426, in _make_request six.raise_from(e, None) File "<string>", line 3, in raise_from File "/usr/local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 421, in _make_request httplib_response = conn.getresponse() File "/usr/local/lib/python3.8/http/client.py", line 1347, in getresponse response.begin() File "/usr/local/lib/python3.8/http/client.py", line 307, in begin version, status, reason = self._read_status() File "/usr/local/lib/python3.8/http/client.py", line 276, in _read_status raise RemoteDisconnected("Remote end closed connection without" urllib3.exceptions.ProtocolError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.8/site-packages/mailmanclient/restbase/connection.py", line 91, in call response = request( File "/usr/local/lib/python3.8/site-packages/requests/api.py", line 61, in request return session.request(method=method, url=url, **kwargs) File "/usr/local/lib/python3.8/site-packages/requests/sessions.py", line 530, in request resp = self.send(prep, **send_kwargs) File "/usr/local/lib/python3.8/site-packages/requests/sessions.py", line 643, in send r = adapter.send(request, **kwargs) File "/usr/local/lib/python3.8/site-packages/requests/adapters.py", line 498, in send raise ConnectionError(err, request=request) requests.exceptions.ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.8/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/lib/python3.8/site-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/usr/local/lib/python3.8/site-packages/postorius/views/generic.py", line 74, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/usr/local/lib/python3.8/site-packages/django/views/generic/base.py", line 97, in dispatch return handler(request, *args, **kwargs) File "/usr/local/lib/python3.8/site-packages/postorius/views/list.py", line 288, in get return render(request, 'postorius/lists/summary.html', data) File "/usr/local/lib/python3.8/site-packages/django/shortcuts.py", line 19, in render content = loader.render_to_string(template_name, context, request, using=using) File "/usr/local/lib/python3.8/site-packages/django/template/loader.py", line 62, in render_to_string return template.render(context, request) File "/usr/local/lib/python3.8/site-packages/django/template/backends/django.py", line 61, in render return self.template.render(context) File "/usr/local/lib/python3.8/site-packages/django/template/base.py", line 171, in render return self._render(context) File "/usr/local/lib/python3.8/site-packages/django/template/base.py", line 163, in _render return self.nodelist.render(context) File "/usr/local/lib/python3.8/site-packages/django/template/base.py", line 936, in render bit = node.render_annotated(context) File "/usr/local/lib/python3.8/site-packages/django/template/base.py", line 903, in render_annotated return self.render(context) File "/usr/local/lib/python3.8/site-packages/django/template/loader_tags.py", line 150, in render return compiled_parent._render(context) File "/usr/local/lib/python3.8/site-packages/django/template/base.py", line 163, in _render return self.nodelist.render(context) File "/usr/local/lib/python3.8/site-packages/django/template/base.py", line 936, in render bit = node.render_annotated(context) File "/usr/local/lib/python3.8/site-packages/django/template/base.py", line 903, in render_annotated return self.render(context) File "/usr/local/lib/python3.8/site-packages/django/template/loader_tags.py", line 62, in render result = block.nodelist.render(context) File "/usr/local/lib/python3.8/site-packages/django/template/base.py", line 936, in render bit = node.render_annotated(context) File "/usr/local/lib/python3.8/site-packages/django/template/base.py", line 903, in render_annotated return self.render(context) File "/usr/local/lib/python3.8/site-packages/django/template/library.py", line 234, in render return t.render(new_context) File "/usr/local/lib/python3.8/site-packages/django/template/base.py", line 173, in render return self._render(context) File "/usr/local/lib/python3.8/site-packages/django/template/base.py", line 163, in _render return self.nodelist.render(context) File "/usr/local/lib/python3.8/site-packages/django/template/base.py", line 936, in render bit = node.render_annotated(context) File "/usr/local/lib/python3.8/site-packages/django/template/base.py", line 903, in render_annotated return self.render(context) File "/usr/local/lib/python3.8/site-packages/django/template/defaulttags.py", line 309, in render return nodelist.render(context) File "/usr/local/lib/python3.8/site-packages/django/template/base.py", line 936, in render bit = node.render_annotated(context) File "/usr/local/lib/python3.8/site-packages/django/template/base.py", line 903, in render_annotated return self.render(context) File "/usr/local/lib/python3.8/site-packages/django/template/defaulttags.py", line 309, in render return nodelist.render(context) File "/usr/local/lib/python3.8/site-packages/django/template/base.py", line 936, in render bit = node.render_annotated(context) File "/usr/local/lib/python3.8/site-packages/django/template/base.py", line 903, in render_annotated return self.render(context) File "/usr/local/lib/python3.8/site-packages/django/template/base.py", line 986, in render output = self.filter_expression.resolve(context) File "/usr/local/lib/python3.8/site-packages/django/template/base.py", line 697, in resolve new_obj = func(obj, *arg_vals) File "/usr/local/lib/python3.8/site-packages/postorius/templatetags/nav_helpers.py", line 74, in held_count return mlist.get_held_page().total_size File "/usr/local/lib/python3.8/site-packages/mailmanclient/restobjects/mailinglist.py", line 132, in get_held_page return Page(self._connection, url, HeldMessage, count, page) File "/usr/local/lib/python3.8/site-packages/mailmanclient/restbase/page.py", line 37, in __init__ self._create_page() File "/usr/local/lib/python3.8/site-packages/mailmanclient/restbase/page.py", line 62, in _create_page response, content = self._connection.call(self._build_url()) File "/usr/local/lib/python3.8/site-packages/mailmanclient/restbase/connection.py", line 119, in call raise MailmanConnectionError( mailmanclient.restbase.connection.MailmanConnectionError: ('Could not connect to Mailman API: ', "ConnectionError(ProtocolError('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')))") web logs: 10.9.253.147 - - [29/Oct/2025:18:54:41 +0000] "GET /hyperkitty/list/obfuscated.name(a)lists.fhcrc.org/ HTTP/1.1" 404 6305 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/141.0.0.0 Safari/537.36" "-" 10.9.253.147 - - [29/Oct/2025:21:03:52 +0000] "GET /postorius/lists/obfuscated.name.lists.fhcrc.org/ HTTP/1.1" 503 6310 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/141.0.0.0 Safari/537.36" "-" 10.9.253.147 - - [29/Oct/2025:21:06:37 +0000] "GET /postorius/lists/obfuscated.name.lists.fhcrc.org/ HTTP/1.1" 503 6310 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/141.0.0.0 Safari/537.36" "-" 10.9.253.147 - - [29/Oct/2025:21:24:25 +0000] "GET /postorius/lists/obfuscated.name.lists.fhcrc.org/ HTTP/1.1" 503 6310 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/141.0.0.0 Safari/537.36" "-" 10.9.253.147 - - [29/Oct/2025:22:11:56 +0000] "GET /postorius/lists/obfuscated.name.pattest.lists.fhcrc.org/ HTTP/1.1" 404 6305 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/141.0.0.0 Safari/537.36" "-" 10.9.253.147 - - [29/Oct/2025:22:12:03 +0000] "GET /postorius/lists/obfuscated.name.lists.fhcrc.org/ HTTP/1.1" 503 6310 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/141.0.0.0 Safari/537.36" "-" Thanks, -p Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering Fred Hutchinson Cancer Center O 206.667.4856 phirayam(a)fredhutch.org ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, October 29, 2025 15:12 To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: "Something went wrong | Mailman REST API not available. Please restart Mailman core. CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. On 10/29/25 14:31, Hirayama, Pat wrote: > > The weird thing is that it is not all lists. Most of them seem to be fine. Which suggests to me that the issue is with a few lists, but not systemwide, so I think my settings in mailman.cfg, settings.py, settings_local.py are likely correct. So Postorius can connect to Mailman core's API on behalf of some, but not all lists. This is very strange. > For the problem lists, I see this in the log: > > ERROR 2025-10-29 18:38:56,784 7 postorius Mailman REST API not available > ERROR 2025-10-29 18:38:56,790 7 django.request Service Unavailable: /postorius/lists/obfuscated.name.lists.fhcrc.org/ > ERROR 2025-10-29 18:38:56,790 7 django.request Service Unavailable: /postorius/lists/obfuscated.name.lists.fhcrc.org/ > > So, Postorius can't communicate with the API, I guess? These are the normal messages when the REST API is not available. But it apparently is available for at least some API endpoints. What is the traceback from the ERROR 2025-10-29 18:38:56,784 7 postorius Mailman REST API not available error and what is in the web server logs? -- 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://urldefense.com/v3/__https://lists.mailman3.org/mailman3/lists/mailm…<https://urldefense.com/v3/__https:/lists.mailman3.org/mailman3/lists/mailma…> Archived at: https://urldefense.com/v3/__https://lists.mailman3.org/archives/list/mailma…<https://urldefense.com/v3/__https:/lists.mailman3.org/archives/list/mailman…> This message sent to phirayam(a)fredhutch.org

6 days, 12 hours

Re: template head/footer questions.

by Mark Sapiro

On 4/8/22 11:04, bob B via Mailman-users wrote: > I migrated from mailman 2 to mailman3 and had head/footer questions. > > In the mailman 3 GUI see the templates section, so where do those files get edited/stored? in the postorius_emailtemplate table in the database. > I added a footer to a list via the GUI, but I do not see it in: > /var/templates/lists/[listNAME]/en Because when you set a template in Postorius it makes an entry in the template table in the database with a URI pointing to its own API to retrieve the template. > I see some directories corresponding to list names in /var/templates/lists/ But I do not have a directory for all my lists and for the footer one I just added. > > Bottom line, > > I assume I should not edit or create any files in /var/templates/lists/ and just use the GUI? That's up to you. The default search path for templates in the absence of a template table entry (or even with one with a mailman:/// URI) includes the var/templates/lists/list_id directory. is this directory leftover from migrating from mailman 2 to 3? No I have a list admin who has made some head and footer files and wants me to put them in /var/templates/lists/[listNAME]/en/.... but I think that may not be the best option. Again, it's up to you. If you have Postorius and want list admins to be able to create, modify, break, etc. templates without involving you, then Postorius is a good option, but it isn't in all cases. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

Re: Mailman, etc. upgrade woes and persistent bugs

by Mark Sapiro

On 2/11/21 10:22 PM, hansen(a)rc.org wrote: > I just had my Mailman suite upgraded. When it got started, I starting receiving messages that hundreds of subscribers to the lists had been disables, including several of the list moderators. This version started supporting bounce processing, but how in the world was this upgrade allowed to act on bounces that were being collected PRIOR to enabling bounce processing?? I'm sorry about that. It's too late now, but the avoidance is discussed at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>. > I got many angry emails, messages and phone calls asking what was going on, as they were bona fide list members. I was very surprised myself. > > I then looked at several of the disabled accounts, but the subscription info page in Postorius had no information about whether an account was enabled or disabled. Why is this not displayed???. The members can't see if their account is enabled. Is this another example of the disconnect between Mailman and Postorius? If the user has a Django account, she can see all that info at (e.g. for this list) <https://lists.mailman3.org/mailman3/accounts/subscriptions/> She gets there from `Mailman settings` in the dropdown under her user name. She can also get there via the `Manage Subscription` button on the list's Info page. That takes her to `List-based preferences` for the list. Any setting not selected there is inherited from the Address-based preferences or Global Mailman preferences > Further, even after the upgrade, the moderators still cannot access the list memberships even though all the lists are set to allow that. I would have asked the moderators to do this if this access bug had been fixed, but they can't get there. You've already reported this at <https://gitlab.com/mailman/postorius/-/issues/462>, and it's been previously reported at <https://gitlab.com/mailman/postorius/-/issues/369>. > As a result of these bugs, after consulting with Brian, who helped with the upgrade, I spent many hours re-enabling the several hundred accounts that had been disabled. I had to go through each email notification to find the address of a disabled account, then find the list, then the member, in Postorius, and finally enable the account (at which time Postorius DID show the enabled status). I'm sorry you had to go through this. The potential issue and the avoidances should be better documented. Unfortunately, they aren't. > Please, can the next upgrade include these very basic fixes/enhancements, which I requested a long time ago: > > a. The ability of moderators to see the list membership (a bug). As I note above, this is a known issue. We are a small project with very feew core developers, all of whom are volunteers. There is a merge request at <https://gitlab.com/mailman/postorius/-/merge_requests/423> which purports to fix <https://gitlab.com/mailman/postorius/-/issues/369>, but as you can see from the comment thread, it is not complete and the author has apparently disappeared. If you would like to take it over and address the deficiencies, we would welcome that. > b. The ability of members to change their addresses for all lists they are subscribed to. Users can add addresses to their account and can then change their subscribed address at (again, e.g. for this list) <https://lists.mailman3.org/mailman3/accounts/list-options/mailman-users.mai…> (Get there via the `Manage Subscription` button on the list's Info page.) If one is subscribed to lists via their `primary` address, one can go to `E-mail Addresses` in their account settings and make a new address `primary` and that will change all their subscriptions. > and further, now: > > c. That when members go to look at their subscription info, they can actually see the settings. They can if they go to `Mailman settings` in the dropdown or the `Manage Subscription` button on the list's Info page and look at all the tabs. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

"Something went wrong | Mailman REST API not available. Please restart Mailman core.

by Hirayama, Pat

Greetings, Some of my lists have started displaying this behavior — when you try to access the list page(s), you get a page with this message: Something went wrong Mailman REST API not available. Please restart Mailman core. My mailman-core docker container is running, as are mailman-django-uwsgi, mailman-nginx and mailman-postfix. Restarting the containers doesn't change this behavior. Google suggests restarting mailman core. Or that we might not be using the correct account name, password or port. The weird thing is that it is not all lists. Most of them seem to be fine. Which suggests to me that the issue is with a few lists, but not systemwide, so I think my settings in mailman.cfg, settings.py, settings_local.py are likely correct. For the problem lists, I see this in the log: ERROR 2025-10-29 18:38:56,784 7 postorius Mailman REST API not available ERROR 2025-10-29 18:38:56,790 7 django.request Service Unavailable: /postorius/lists/obfuscated.name.lists.fhcrc.org/ ERROR 2025-10-29 18:38:56,790 7 django.request Service Unavailable: /postorius/lists/obfuscated.name.lists.fhcrc.org/ So, Postorius can't communicate with the API, I guess? I look at settings_local.py: MAILMAN_REST_API_URL = 'http://mailman-core:8001' I believe 8001 is the default, and since I haven't specified one in the [webservice] section of mailman.cfg, I'm assuming 8001 is correct (plus, it works for other lists). There are a few messages waiting for moderator approval — otherwise, I'd probably try just deleting the list and recreating it. Anyone have any suggestions on what else I should look at? Thanks! -p Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering - Infrastructure Fred Hutch Cancer Center O 206.667.4856 phirayam(a)fredhutch.org<mailto:phirayam@fredhutch.org>

6 days, 14 hours

Re: customized welcome message

by Nils

Forget the previous message. Thank you very much for your help, Mark. I looked at the configuration files once more, and changing POSTORIUS_TEMPLATE_BASE_URL in mailman-web.py fixed the issue for me. Kind regards On 12/7/23 23:09, Nils wrote: > On 12/7/23 22:40, Mark Sapiro wrote: >> How and to what did you set the URL for the template? What does the >> database query >> >> SELECT uri FROM template WHERE name = 'list:user:notice:welcome'; >> >> show? > http://localhost/postorius/api/templates/list/testliste.lists.DOMAIN.TLD > > This value can't work. Now it makes sense that it gets redirected and > the use of localhost also explains why it didn't show in any of the > virtual hosts log files that I was checking until it was redirected. > > However, I didn't set that value. I edited the template at > postorius/lists/testliste.lists.DOMAIN.TLD/templates and there I can > just select a template type and then I get one textarea input field > for the content. > The value in the database is set automatically, when I create a > template in postorius (and is also automatically removed when I delete > a template there). I can't edit this value without manually changing > it in the database. > >> This is very old. Current Postorius is 1.3.10. 1.2.4 is from February >> 2019. The Debian/Ubuntu packages are out of date. We recommend >> installing via the doc at >> https://docs.mailman3.org/en/latest/install/virtualenv.html > > The server will be updated from Ubuntu 20.04 (focal) to 22.04 (jammy) > very soon. The Debian/Ubuntu packages sure have their downsides but > once they work, they update automatically and require very little > maintenance.

1 year, 10 months

Mailman-users search results for query "Postorius"