Search results for "Postorius" - Mailman-users

Re: Customise Postorius templates?

by Abhilash Raj

> On Feb 7, 2022, at 4:35 AM, Duane Raymond <duane(a)fairsay.com> wrote: > > On Mon, 7 Feb 2022 at 00:56, Abhilash Raj <maxking(a)asynchronous.in> wrote: > >>> On Feb 1, 2022, at 11:01 AM, Mark Sapiro <mark(a)msapiro.net> wrote: >>> >>> On 2/1/22 09:47, Duane Raymond wrote: >>>> Hi, >>>> I'm looking to do some radical customisation of the Postorius (and >> Hyperkitty) templates over the next 6 ish months and was wondering if there >> is a 'best practice' way to do this that will survive updates to MM3. I've >> searched around and not found much and also tested copying >>>> >> venv/lib/python3.7/site-packages/postorius/templates/postorius/lists/summary.html >>>> to >>>> var/templates/lists/summary.html >>>> As suggested in some posts - but it didn't seem to pick up the >> customisation - only customisations in the venv path worked - and they get >> overwritten on update. > > >> The best way to do this would be utilize Django’s template loader. See >> here[1] for the documentation on how you can do this. You want to put the >> path where you are putting the templates under `DIRS` option of the >> `TEMPLATES` section. >> >> Do make sure that you are keeping the directory structure correct so that >> Django can discover them. Like, Hyperkitty’s base.html should be in >> `/custom/path/hyperkitty/base.html`, where `/custom/path` is what you’ve >> setup in DIRS setting above. >> > I hadn’t tried it when I sent email, but when I tried it locally on Postorius, it seems to work for me. > This looks promising! I've not got it working yet, but this is what I've > tried: > > 1. Created folder 'custom' in the mm root (in my case: /opt/mailman/mm/) > 2. Copied the files and folders from postorius/templates/postorius/* and > hyperkitty/templates/hyperkitty/* to the custom/ folder (not the > full postorius/templates/postorius/ match, just evening in the > second postorius/ dirrectory) Note that you want to copy from “src/postorius/templates” directory to your "/opt/mailman/mm/custom” directory. It is important that you retain the “postorius” and “hyperkitty” directories. Here is what I have in my settings.py: - 'DIRS': [], + 'DIRS': ['/Users/maxking/Documents/mm3/postorius/example_project/templates’], And here is the structure of the templates directory you are seeing above: $ tree /Users/maxking/Documents/mm3/postorius/example_project/templates /Users/maxking/Documents/mm3/postorius/example_project/templates └── postorius └── lists └── summary.html Note that I am only overriding the Summary page here. > 3. Recursive update of permissions of the custom/ folder and files to be > mailman > 4. Updated /opt/mailman/mm/settings.py by changing "'DIRS': []" > to "'DIRS': [BASE_DIR, '/custom/']" in the "TEMPLATES =" section Note that you don’t want [“BASE_DIR”, “/custom/“] here, the comma is the wrong value here. The docs I mentioned have a “/“. Although, it is possible that even “/“ since that needs BASE_DIR to be a Path datatype and not string. Easiest thing with least surprise would be to use the full path, atleast to ensure that template discovery works as expected. > 5. Edited the original AND copied postorius/lists/summary.html to have a > small change in the footer of each so I know what version it is serving Since I was running a dev server, it doesn’t need restart, but simply restarting gunicorn should should do it. You don’t need to restart anything else. > 6. Restarted: gunicorn qcluster mailman nginx and cleared browser cache > 7. Reloaded the 'info' page of a few lists to see which version ti was > serving > > Variants: I've also changed the DIRS value to the hard-coded path: > /opt/mailman/mm/custom > > Result: it is still serving the default/original Postorius template vs the > custom one. > > Any suggestions for things I should do to make it use the /custom/ folder > instead? Any recompiling or other actions beyond just restarting? (I > probably don't need to restart qcluster and maybe not even mailman core for > this to take effect but I do it just in case!) Hope that helps. -- thanks, Abhilash Raj (maxking)

4 years, 9 months

Re: FILTER_VHOST fix - was: Postorius & multi domain

by Gelpi Andrea

Il 23/04/20 01:08, Mark Sapiro ha scritto: > On 4/22/20 11:52 AM, Mark Sapiro wrote: >> >> I'm currently working on a better fix. I'll post here on my progress. > > > I've got a tentative fix at > <https://gitlab.com/mailman/postorius/-/merge_requests/500/>. You can > see the changes there to the file src/postorius/views/list.py. > > This fix is limited in that it should enable FILTER_VHOST work in an > environment where there are domains with web host different from mail > host, but if there are multiple domains with the same web host but > differing mail hosts, going to that domain's Postorius lists view will > show all domains as if FILTER_VHOST is False. > > I.e. consider the following set of domains: > > mail host web host > example.com lists.example.com > example.net example.net > example.org lists.example.org > example.edu lists.example.org > > With the fix installed and FILTER_VHOST = True > > https://lists.example.com/postorius/lists/ will show only the > example.com lists > > https://example.net/postorius/lists/ will show only the example.net lists > > but https://lists.example.org/postorius/lists/ will show all lists, not > just the example.org and example.edu lists. > I saw the change in the file. As I'm not a programmer How can I test your fix? My system was installed via Debian 10 stable repository. I upgrade with testing repository postorius, django and mailmanclinet Postorius V 1.3.2 Django V. 2.2.12 Django filters V 2.1.0 Djanog mailman V 1.3.2 mailmanclient V 3.3.0 Thnak You -- Gelpi ing. Andrea ************************************************** I documenti vitali dimostreranno la loro vitalitˆ spostandosi spontaneamente da dove li avevate lasciati a dove non riuscirete a trovarli. **************************************************

6 years, 6 months

Re: mailman3 postorius cannot retrieve template

by Wolfgang Bock

Dear Mark, you wrote: "When you create a template in Postorius, that uri becomes something like `https://example.com/mailman3/api/templates/list/<list_id>/<template_name>` which basically says get the template from Postorius, and the template if any in var/templates is ignored." In my case that is not true. I get an db-entry in the mailman3 table template which doesnt lead to a suitable link: https://localhost/postorius/api/templates/list/testliste01.mydomain.de/list: member:regular:footer In the next stept it leads to a flood of entries in my syslog because django is asking for a certificate match for "localhost": Nov 2 11:47:49 myserver mailman3[175334]: Nov 02 11:47:49 2021 (175334) Certificate did not match expected hostname: localhost. Certificate: ... Letsencrypt cannot deliver this match for "localhost", it is impossible to configurate letsencrypt to do so. The running script must create a postgres INSERT database command which includes the correct domain-name including the correct path .../mailman3/api/templates .... and not ... postorius/api/.... I dont know, where is the place to correct this. - in mailman-web.py ?? ... ALLOWED_HOSTS ... '*' or MAILMAN_REST_API_URL = 'http://localhost:8001' or POSTORIUS_TEMPLATE_BASE_URL = 'https://localhost/mailman3/' - in mailman.cfg ?? the [paths.debian] section the [webservice] section - or elsewhere Thanks in advance for your reply. Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Sonntag, 31. Oktober 2021 19:15 An: mailman-users(a)mailman3.org Betreff: [MM3-users] Re: mailman3 postorius cannot retrieve template at ... (<no authorization>) On 10/29/21 3:41 AM, Wolfgang Bock via Mailman-users wrote: > > the question is: postgres - mailman3web-postorius_emailtemplate table > vs > mailman3 - templates table > > I installed a brand new mailman3 with mailman Core 3.3.3, Api 3.1, > Core Python 3.9.2 postgres12 nginx on debian bullseye. > > I created a template via postorius -> lists -> (testliste01) -> > templates > -> new template -> [list:member:regular:footer] and > [list:member:digest:footer] > > They are shown in the postgres database mailman3 table templates: > id name context uri username password > 14 list:member:digest:footer testliste01.mydomain.de > http://localhost/postorius/api/templates/list/testliste01.mydomain.de/ > list:m > ember:digest:footer > 15 list:member:regular:footer testliste01.mydomain.de > http://localhost/postorius/api/templates/list/testliste01.mydomain.de/ > list:m > ember:regular:footer > > First there where no templates in the /var/lib/mailman3/templates > folder, which was empty after installation. This is expected. That is one place where you can put custom templates. > Later I created in /var/lib/mailman3/templates theses folders and the > files /list/testliste01.mydomain.de/list:member:digest:footer + > list:member:regular:footer owned by list:list 644 > > A testmail went through but instead of the default footer no footer > was shown. By default Mailman searches for templates first in the var/templates directory and then in the templates directory in the Mailman installation. The details are described at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n. py#L44. However, the default search is only applied if there is matching entry for the template name and context in the `templates` table in the database or if the uri in the entry is a `mailman://` uri. When you create a template in Postorius, that uri becomes something like `https://example.com/mailman3/api/templates/list/<list_id>/<template_name>` which basically says get the template from Postorius, and the template if any in var/templates is ignored. > In the sys.log I found the following error message: > Oct 29 11:28:04 myserver mailman3[33015]: Message: 'Cannot retrieve > template at > http://localhost/postorius/api/templates/list/testliste01.mydomain.de/ > list:m ember:regular:footer (<no authorization>)' So Mailman is trying to get the Postorius template. What is in the web server logs for this retrieval? > How can I solve this problem? What kind of authorisation is meant? list? > restadmin? > > I read in > https://docs.mailman3.org/en/latest/config-core.html#configure-templates > ... list specific templates invar/templates/lists/LIST-ID/LC/ ... > I guess the LC means Language Code. But in the database table templates no > LC subdirectory is mentioned (in my case must be de). If you delete the Postorius template, The entry in the templates table will be removed and the search will revert to var/templates, etc. > And I read (dont know where) .... The templates created in Postorius are > created in the postorius_emailtemplate table in Mailman's database and > referenced via URLs like > 'https://example.com/mailman3/api/templates/list/<list-id>/<template-name>'. > I.e., they are not stored in the file system. ... > > That's true. I found in postgres database mailman3web in the table > mailman3web postorius_emailtemplate my > > id name data language created_at modified_at > context identifier > 15 list:member:digest:footer postorius footer digest 1x linefeed > 2021-10-29 11:17:40.664689+02 2021-10-29 11:26:48.692628+02 list > testliste01.mydomain.de > 16 list:member:regular:footer postorius footer non-digest 1x > linefeed 2021-10-29 11:18:29.166241+02 2021-10-29 11:27:24.519024+02 list > testliste01.mydomain.de > > But my question is how to integrate this into the mailman3-system. The > language isn't set either. It is integrated. The language isn't set because you are getting the template from Postorius and Postorius knows the language. On 10/31/21 4:13 AM, Wolfgang Bock via Mailman-users wrote: > regarding my mail before, here an additional information. > > I can show the templates with following command (anonymized): > https://active_domain.de/postorius/api/templates/list/testliste01.active_dom ain.de/list:member:regular:footer As it should be. > The complete syslog > (edited and reformatted by me) ``` > --- Logging error --- > Traceback (most recent call last): Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3/dist-packages/mailman/model/template.py", line 110, in get > contents = protocols.get(actual_uri, **auth) > File "/usr/lib/python3/dist-packages/mailman/utilities/protocols.py", line 39, in get > response.raise_for_status() > File "/usr/lib/python3/dist-packages/requests/models.py", line 943, in raise_for_status > raise HTTPError(http_error_msg, response=self) > requests.exceptions.HTTPError: 404 Client Error: Not Found for url: http://localhost/postorius/api/templates/list/testliste01.active_domain.de/l ist:member:regular:footer > During handling of the above exception, another exception occurred: > Traceback (most recent call last): > File "/usr/lib/python3.9/logging/__init__.py", line 430, in format > return self._format(record) > File "/usr/lib/python3.9/logging/__init__.py", line 426, in _format > return self._fmt % record.__dict__ > KeyError: 't' > During handling of the above exception, another exception occurred: Your template is malformed. You have $ strings that are not defined as Mailman substitution variables. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/t emplates.html#templated-texts -- 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years

Re: mailman3 postorius cannot retrieve template at ... (<no authorization>)

by Mark Sapiro

On 10/29/21 3:41 AM, Wolfgang Bock via Mailman-users wrote: > > the question is: postgres - mailman3web-postorius_emailtemplate table vs > mailman3 - templates table > > I installed a brand new mailman3 with mailman Core 3.3.3, Api 3.1, Core > Python 3.9.2 postgres12 nginx on debian bullseye. > > I created a template via postorius -> lists -> (testliste01) -> templates > -> new template -> [list:member:regular:footer] and > [list:member:digest:footer] > > They are shown in the postgres database mailman3 table templates: > id name context uri username password > 14 list:member:digest:footer testliste01.mydomain.de > http://localhost/postorius/api/templates/list/testliste01.mydomain.de/list:m > ember:digest:footer > 15 list:member:regular:footer testliste01.mydomain.de > http://localhost/postorius/api/templates/list/testliste01.mydomain.de/list:m > ember:regular:footer > > First there where no templates in the /var/lib/mailman3/templates folder, > which was empty after installation. This is expected. That is one place where you can put custom templates. > Later I created in /var/lib/mailman3/templates theses folders and the files > /list/testliste01.mydomain.de/list:member:digest:footer + > list:member:regular:footer owned by list:list 644 > > A testmail went through but instead of the default footer no footer was > shown. By default Mailman searches for templates first in the var/templates directory and then in the templates directory in the Mailman installation. The details are described at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n…. However, the default search is only applied if there is matching entry for the template name and context in the `templates` table in the database or if the uri in the entry is a `mailman://` uri. When you create a template in Postorius, that uri becomes something like `https://example.com/mailman3/api/templates/list/<list_id>/<template_name>` which basically says get the template from Postorius, and the template if any in var/templates is ignored. > In the sys.log I found the following error message: > Oct 29 11:28:04 myserver mailman3[33015]: Message: `Cannot retrieve template > at > http://localhost/postorius/api/templates/list/testliste01.mydomain.de/list:m > ember:regular:footer (<no authorization>)` So Mailman is trying to get the Postorius template. What is in the web server logs for this retrieval? > How can I solve this problem? What kind of authorisation is meant? list? > restadmin? > > I read in > https://docs.mailman3.org/en/latest/config-core.html#configure-templates > ... list specific templates invar/templates/lists/LIST-ID/LC/ ... > I guess the LC means Language Code. But in the database table templates no > LC subdirectory is mentioned (in my case must be de). If you delete the Postorius template, The entry in the templates table will be removed and the search will revert to var/templates, etc. > And I read (dont know where) .... The templates created in Postorius are > created in the postorius_emailtemplate table in Mailman`s database and > referenced via URLs like > `https://example.com/mailman3/api/templates/list/<list-id>/<template-name>`. > I.e., they are not stored in the file system. ... > > That`s true. I found in postgres database mailman3web in the table > mailman3web postorius_emailtemplate my > > id name data language created_at modified_at > context identifier > 15 list:member:digest:footer postorius footer digest 1x linefeed > 2021-10-29 11:17:40.664689+02 2021-10-29 11:26:48.692628+02 list > testliste01.mydomain.de > 16 list:member:regular:footer postorius footer non-digest 1x > linefeed 2021-10-29 11:18:29.166241+02 2021-10-29 11:27:24.519024+02 list > testliste01.mydomain.de > > But my question is how to integrate this into the mailman3-system. The > language isn`t set either. It is integrated. The language isn`t set because you are getting the template from Postorius and Postorius knows the language. On 10/31/21 4:13 AM, Wolfgang Bock via Mailman-users wrote: > regarding my mail before, here an additional information. > > I can show the templates with following command (anonymized): > https://active_domain.de/postorius/api/templates/list/testliste01.active_do… As it should be. > The complete syslog > (edited and reformatted by me) ``` > --- Logging error --- > Traceback (most recent call last): Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3/dist-packages/mailman/model/template.py", line 110, in get > contents = protocols.get(actual_uri, **auth) > File "/usr/lib/python3/dist-packages/mailman/utilities/protocols.py", line 39, in get > response.raise_for_status() > File "/usr/lib/python3/dist-packages/requests/models.py", line 943, in raise_for_status > raise HTTPError(http_error_msg, response=self) > requests.exceptions.HTTPError: 404 Client Error: Not Found for url: http://localhost/postorius/api/templates/list/testliste01.active_domain.de/… > During handling of the above exception, another exception occurred: > Traceback (most recent call last): > File "/usr/lib/python3.9/logging/__init__.py", line 430, in format > return self._format(record) > File "/usr/lib/python3.9/logging/__init__.py", line 426, in _format > return self._fmt % record.__dict__ > KeyError: `t` > During handling of the above exception, another exception occurred: ``` Your template is malformed. You have $ strings that are not defined as Mailman substitution variables. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… -- 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: per domain SITE_ID views?

by Mark Sapiro

On 12/28/21 1:14 PM, David Newman wrote: > Using FILTER_VHOST, I have two domains set up and working with MM3, > Postorius and Hyperkitty. However, because SITE_ID in settings.py points > to one of the domains, that domain name always appears on Postorius and > Hyperkitty pages. ... > How to get the correct domain to appear on that domain's Postorius and > Hyperkitty pages? I don't think the domain is actually displayed on Postorius pages. If I'm wrong, on what Postorius view do you see it? As far as HyperKitty is concerned, please file an issue for this at https://gitlab.com/mailman/hyperkitty/-/issues/new -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

CVE-2021-40347: New security release for Postorius

by Abhilash Raj

Everyone, A security vulnerability was reported against Postorius recently which allows any logged-in user to unsubscribe any other member on any other list on same Mailman installation using a specially crafted POST request due to a missing ownership check. This has been assigned CVE-2021-40347. This affects all past versions of Postorius including 1.0.0. Thanks to Kunal Mehta for the security report and a quick patch to fix the vulnerability. I am also attaching a minimal patch that fixes it along with this email, without tests and NEWS so that it applies to older versions of Postorius easily (I have tested the included patch with 1.3.3, 1.3.2 git tags). Upgrading to 1.3.5 release is highly recommended and it mostly includes the fix for this vulnerability (and a small compatibility fix for django-mailman3 1.3.6) so it shouldn’t introduce any other bugs. You can upgrade to this release by running: $ pip install postorius==1.3.5 A full change log is available here[1] as usual and can be downloaded from PyPI[2]. [1]: https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-5 [2]: https://pypi.org/project/postorius/1.3.5/ Since there aren't many changes, this release requires 3.5+ like 1.3.4. Although, note that the next release will drop support for 3.5 and will support 3.6 only. For those of you who use container images, I am working on 0.3.12 of container images right now, so look out for that announcement. For those of you using the rolling releases, you can already upgrade to the latest version of the rolling release as it has the fix. -- thanks, Abhilash Raj (maxking)

5 years, 2 months

Dropdown problem in postorius due to bootstrap

by Greg Newby

(My first post) As has been observed, the Ubuntu 24.04 LTS packaging for native Mailman3 can be challenging. I've been solving all kinds of issues, and I'm writing here about something I've so far been unable to solve. The problem: *In Postorius, dropdown menus are not working*. I.e., as a list admin you can click on a menu option like "Users" or "Mass operations," and nothing happens. As a regular user, the top-right icon to manage settings and logout does not do anything. The same behavior occurs regardless of which browser I use. The dropdown in HyperKitty works, and HyperKitty uses a different code base. In the browser developer console (Firefox & others), the error is: “Uncaught TypeError: n.createPopper is not a function.” I've dug deeply into this. The relevant <script> is bootstrap.min.js. Postorius (via django) is using version 5.3.1 via package libjs-bootstrap5: ** This is what django is using: /usr/share/bootstrap-html/js/bootstrap.bundle.min.js -- version 5.3.1, linked to: /usr/share/javascript/bootstrap5/js/bootstrap.bundle.min.js /usr/share/python3-django-postorius/static/postorius/libs/bootstrap/js/bootstrap.bundle.min.js Here is detail of the error from the Firefox developer console: Uncaught TypeError: n.createPopper is not a function _createPopper dropdown.js:241 show dropdown.js:139 toggle dropdown.js:121 <anonymous> dropdown.js:446 i event-handler.js:118 R event-handler.js:184 on event-handler.js:216 <anonymous> dropdown.js:444 <anonymous> bootstrap.bundle.min.js:6 <anonymous> bootstrap.bundle.min.js:6 By temporarily replacing /usr/share/python3-django-postorius/static/postorius/libs/bootstrap/js/bootstrap.bundle.min.js I have tried moving back to 4.6.1 (from libjs-bootstrap4). I have also retrieved the latest 5.3.1 from the CDN, which is slightly different but doesn't change the error: https://cdn.jsdelivr.net/npm/bootstrap@5.3.1/dist/js/bootstrap.bundle.min.js Here's the JavaScript section from the bottom of a sample page from my Postorius site (view-source: https://lists.ogf.org/mailman3/postorius/lists/gfsg.lists.ogf.org/held_mess… ): <script src="/mailman3/static/postorius/libs/jquery/jquery-3.6.0.min.js"></script> <script src="/mailman3/static/postorius/libs/bootstrap/js/bootstrap.bundle.min.js"></script> <script src="/mailman3/static/django-mailman3/js/main.js"></script> <script src="/mailman3/static/postorius/js/script.js" defer></script> <script> // Add the .js-enabled class to the body so we can style the elements // depending on whether Javascript is enabled. $(document).ready(function(){ $("body").addClass("js-enabled"); $(".gravatar").addClass("rounded-circle"); }); </script> I would appreciate suggestions about how to solve this problem. Thanks to everyone who is doing a great job building and supporting Mailman3. I've been using Mailman2 for a long time, and have dozens of lists on multiple servers. ~ Greg Newby

2 years, 4 months

Ann: Postorius 1.3.6 is now out

by Abhilash Raj

Hey Everyone, I just tagged and released Postorius 1.3.6. This release includes both bug fixes and new features. Some of the notable features include - Ability to list and handle un-subscription requests to the list - Option to choose delivery mode and delivery_status directly when subscribing to a list - Addition of a user management interface, which allows updating a users password, manually verifying their email addresses, update user’s Display Name etc. - Expose a number of Bounce processing related options in List’s settings A full list of changes is available here https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-6 You can install this release using pip $ pip install postorius django-mailman3 mailmanclient —upgrade Do note that this release requires Mailman Core 3.3.5, so you need to upgrade Core before upgrading Postorius. The release tarball is available on PyPI as usual: https://pypi.org/project/postorius/1.3.6/#files Please also ensure to run the post-install commands as per the upgrade documentation: https://docs.mailman3.org/en/latest/upgrade-3.2.html#post-upgrade Thanks to all the folks who helped with this release! Abhilash > Please also ensure to run the post-install commands as per the upgrade documentation[4] (commands _after_ pip install, needs a post-install heading/anchor in there :-). > On Sep 19, 2021, at 8:48 PM, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > Hey Everyone, > > I am pleased to announce that Postorius 1.3.6b1 is now out. This is the first pre-release for 1.3.6, which is slated to release next week soon after Mailman Core 3.3.5 release. > > This release requires Mailman Core 3.3.5 release, so if you are trying out this release, please also upgrade Mailman Core to 3.3.5rc1 (which was just released today). > > This release includes several new features and bug fixes. A full list of changes is available here[1]. > > With this release, we have also improved on the localization of the interface, if you want to help out before the release of the stable 1.3.6, please see the instructions for translators here[2]. We use Weblate for translations, so if you are familiar with that, you can directly head over there[3]. > > Since this is a pre-release version, you can install this using pip via: > > $ pip install --upgrade --pre postorius django-mailman3 mailmanclient > > Please also ensure to run the post-install commands as per the upgrade documentation[4] (commands _after_ pip install, needs a post-install heading/anchor in there :-). > > A release tarball is available on PyPI: > > https://pypi.org/project/postorius/1.3.6b1/#files > > Finally, thanks to all the folks who helped with this release in any capacity and made it possible. > > [1]: https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-6 > [2]: https://docs.mailman3.org/en/latest/translation.html > [3]: https://hosted.weblate.org/projects/gnu-mailman/postorius/ > [4]: https://docs.mailman3.org/en/latest/upgrade-3.2.html#virtualenv-install > > > thanks, > Abhilash -- thanks, Abhilash Raj (maxking)

5 years, 1 month

Re: postorius not displaying mailman logo

by Eggert Ehmke

Did you include the static subdirectory in your web server config? My apache config looks like this: Alias /mailman3/favicon.ico /opt/mailman/web/static/postorius/img/favicon.ico Alias /mailman3/static /opt/mailman/web/static # for hyperkitty Alias /static/admin /opt/mailman/web/static/admin Alias /static/CACHE /opt/mailman/web/static/CACHE Alias /static/django_extensions /opt/mailman/web/static/django_extensions Alias /static/hyperkitty /opt/mailman/web/static/hyperkitty Alias /static/mailman3 /opt/mailman/web/static/hyperkitty Alias /static/django-mailman3 /opt/mailman/web/static/django-mailman3 Alias /static/rest_framework /opt/mailman/web/static/rest_framework # for postorius Alias /static/postorius /opt/mailman/web/static/postorius <Directory /opt/mailman/web/static> Require all granted </Directory> <IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost </IfModule> If you use nginx, the config might look different. Am Dienstag, 22. März 2022, 10:34:21 CET schrieb sekamug--- via Mailman-users: > I successfully installed mailman3 but Postorius doesn't display images on > the web interface. I have checked and the files exist at at the location > /opt/mailman/web/static/postorius i have checked the logs and they appear > as follows: > [pid: 366783|app: 0|req: 43/104] () {34 vars in 687 bytes} [Tue Mar 22 > 09:36:30 2022] GET /static/postorius/js/script.js => generated 5280 bytes > in 43 msecs (HTTP/1.1 404) 6 headers in 197 bytes (1 switches on core 0) > [pid: 366783|app: 0|req: 44/105] () {34 vars in 715 bytes} [Tue Mar 22 > 09:36:30 2022] GET /static/postorius/img/favicon.ico => generated 5280 > bytes in 43 msecs (HTTP/1.1 404) 6 headers in 197 bytes (1 switches on core > 1) it seems the browser fails to access the directory where the pictures > are stored. I have checked and mailman is the owner of that directory. > Please advise. > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 7 months

Re: Set Postorius interface locale

by Mark Sapiro

On 3/2/21 7:55 AM, Duane Raymond wrote: > > The problems I've encountered so far are: > 1) Where do I set the local of the Postorius interface? > 2) Individual lists have a language setting, but it doesn't seem to reflect what the Postorius locales are as the only english option is "English (USA)" and none of the other English speaking locales and on the file system there is no en-us PO files....so I suspect I'm looking in the wrong place. Multiple things are required. In order to be able to set the list's preferred_language via Postorius, the language must be included in the LANGUAGES definition in postorius/utils.py. However, you can set the list's preferred_language in Mailman core via `REST` or `mailman shell` or direct update of the database. Then there must be message catalogs for the language in postorius/locale, django_mailman3/locale and hyperkitty/locale and these must be compiled by the Django management command `compilemessages`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

Mailman-users search results for query "Postorius"