Search results for "Postorius" - Mailman-users

Re: Postorius: Show only own lists

by Thor Atle Rustad

2018-01-23 14:37 GMT+01:00 Simon Hanna <simon(a)hannaweb.eu>: > On 01/23/2018 12:10 PM, Thor Atle Rustad wrote: > >> Imagine an installation with 500+ mailing lists and almost as many local >> admins that are supposed to maintain their own local lists with a few >> local >> members. As site admin, I see all 500+ lists, but I was expecting *local* >> admins to see only the lists they maintain. I have set all lists to >> "advertised = False", so they are hidden from ordinary view. Is there a >> way >> to show only relevant lists to local admins? >> > Are we talking about Postorius or Hyperkitty? > There is no way for users that do not have the django superuser permission, > to see unadvertised lists in the Postorius list index. I just > doublechecked the source. > There is an issue about list filtering/search for the index page. > I believe I wrote Postorius in the subject line, but it may not be so obvious. So yes, in Posterius I would like to hide the lists from email harvesters, while relatively "untrusted" admins should have access to basic operations on the one list he/she "owns" (and without having to browse through 50 pages of mailing lists). Somehow I don't think 500 superusers in our system is a good idea!

7 years, 6 months

Slow performance when listing members on Postorius

by Alan So

We are about to upgrade to Mailman core 3.3.9 and Postorius 1.3.10. We notice that for setup with large number of members, the performance is much slower when listing members on web (Postorius). Further troubleshooting show that there are quite a number of API calls which do not appear in Mailman core 3.3.5 and Postorius 1.3.6 when we list members. [17/Apr/2024:14:12:22 +0800] "GET /3.1/members/33a6266d0a04472c8d5d6c78869a964c/preferences HTTP/1.1" 200 156 "-" "GNU Mailman REST client v3.3.5" [17/Apr/2024:14:12:22 +0800] "GET /3.1/members/7a18b7cb90a34ac98881a3f01b5488d1/preferences HTTP/1.1" 200 156 "-" "GNU Mailman REST client v3.3.5" [17/Apr/2024:14:12:22 +0800] "GET /3.1/members/61c6c3e2aaf443babd3bd191519b0424/preferences HTTP/1.1" 200 156 "-" "GNU Mailman REST client v3.3.5" [17/Apr/2024:14:12:22 +0800] "GET /3.1/members/8dd681165b8c436fac6793cae1ed2c27/preferences HTTP/1.1" 200 156 "-" "GNU Mailman REST client v3.3.5" Further tests showing that each database query using "_member_id" in table member can take as much as 0.3 to 0.5 seconds for some large installations. The default 25 members per page mean that it will take at least 7.5 to 12.5 seconds. Changing to 200 members per page will take even longer time. We wonder whether "_member_id" should be indexed just like most other id in the database mailman_core in order to solve the issue. Or are there any other workarounds? +----------------------+--------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra | +----------------------+--------------+------+-----+---------+----------------+ | id | int(11) | NO | PRI | NULL | auto_increment | | _member_id | char(32) | YES | | NULL | | | role | int(11) | YES | MUL | NULL | | | list_id | varchar(255) | YES | MUL | NULL | | | moderation_action | int(11) | YES | | NULL | | | address_id | int(11) | YES | MUL | NULL | | | preferences_id | int(11) | YES | MUL | NULL | | | user_id | int(11) | YES | MUL | NULL | | | bounce_score | int(11) | YES | | NULL | | | last_bounce_received | datetime | YES | | NULL | | | last_warning_sent | datetime | YES | | NULL | | | total_warnings_sent | int(11) | YES | | NULL | | +----------------------+--------------+------+-----+---------+----------------+

1 year, 3 months

missing graphics in Postorius

by David Newman

After installing MM3 on Debian 10 using the venv docs, no graphics appear in the admin or list pages, just broken links. The mailmanweb log has lines like this: ERROR 2021-12-07 06:04:10,002 18262 django.security.DisallowedHost Invalid HTTP_HOST header: '127.0.0.1'. You may need to add '127.0.0.1' to ALLOWED_HOSTS. which is odd because there is the line for "localhost" in settings.py, and /etc/hosts correctly ties this to 127.0.0.1. There are entries like this in /var/log/nginx/error.log saying the files just aren't there: 2021/12/06 22:00:30 [error] 18123#18123: *65 open() "/opt/mailman/web/static/postorius/img/mailman_logo_small_trans.png" failed (2: No such file or directory), client: x.x.x.x, server: somehost.example.com, request: "GET /static/postorius/img/mailman_logo_small_trans.png HTTP/2.0", host: "somehost.example.com", referrer: "https://somehost.example.com/mailman/lists/" (I've obfuscated names and addresses here, but "somehost.example.com" refers to a valid FQDN in the log.) I thought I'd followed all the venv docs, but the /opt/mailman/web/static/postorius directory doesn't exist. Did I miss something? Thanks. dn

3 years, 7 months

Re: Postorius 1.2.3 and MailmanClient 3.2.1 is now out

by Jonas Meurer

Hey Abhilash, Thanks a lot for your work on mailman3! Abhilash Raj: > I am very pleased to announce (a bit late) that Postorius 1.2.3 and MailmanClient 3.2.1 is now out. > > The full set of changelog can be found in the documentation[1][2]. The most notable feature that > I can think of is non-member management in Postorius. > > New releases are available on PyPI[3][4]. For earlier releases, you provided GnuPG signature files to cryptographically verify that the release files were not tampered with. I couldn't find such signature files for the two latest releases. Would you mind adding them? When packaging for Debian, I prefer to check the GnuPG signatures before uploading new releases. Also, the signature files get uploaded to the Debian archive as well so they can be checked by everybody. That way we can cryptographically proof that the Debian package is based on the original tarball that got packaged and signed by upstream. Cheers jonas

6 years, 6 months

Unwanted E-mail to Maillists Submitted via Postorius Interface

by matthew＠alberti.us

Hi Everyone, I’ve seen a recent uptick in SPAM messages making it into mailing lists. Looking at the raw, it seems that the e-mails are being submitted thru the Postorius/Hyperkitty “Start a New Thread” interface. Is there a way to turn that off? We would want people to only be able to post via e-mail. Part of the problem is that our anti-spam system RSPAMD trusts the mailman-web IP… so it doesn’t scan things originating from there.. ☹ Another uestion: Is there a way to implement captcha, or is there a recommended gate that can be put in the signup process? Apparently bots are finding a way thru the signup process, and then sending messages to the list via the Postorius web interface. There seems to be a Django plugin for it; but it appears the Mailman code would have to be adjusted to implement it. I’m open to any suggestions, including on places to check for misconfiguration. 😊 Thanks. - Matt Alberti

3 years, 11 months

Re: Set Postorius interface locale

by Abhilash Raj

On Tue, Mar 2, 2021, at 7:55 AM, Duane Raymond wrote: > Hi everyone, > > Thanks to Brian I'm up and running with my migrated mailman3 lists and > am now starting to get into customising the interface (styling and > content). I've been trying to figure out how to set/change the > Postorius locale - I specifically want to change some text strings on > the info page without breaking the i18n mechanisms. I've worked with po > and mo files before, so changing and compiling them isn't a problem. > The problems I've encountered so far are: > 1) Where do I set the local of the Postorius interface? The installation has a default Language setting which you can set in the settings.py LANGUAGE_CODE = "en" > 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. List level settings affect the Mailman level emails that go out, not the interface. The users can choose which language the interface shows up in using their browser settings. We primarily depend on the Accept-Language header in the request to determine the language of the response. While users do have a preffered-language setting, it currently isn't used to determine the language of the UI. Like list setting, it is only used to determine the language of the emails sent out (user's preferences override the list's default language). > > Am I looking at this all wrong? The documentation doesn't seem to have > any info about this and yet the mechanisms seem to be there. > > Once I learn more I'm quite keen to start working on improving the > documentation based on what I learn. > > Cheers, > > Duane > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking)

4 years, 4 months

Re: mm3 installation question

by Stephen J. Turnbull

Odhiambo Washington writes: > Mark Sapiro writes: > > Some of the `path` settings are probably not in the same order as > > in that file. The > > > > ``` > > path('mailman3/', include('postorius.urls')), > > path('archives/', include('hyperkitty.urls')), > > ``` > > settings should come after the > > ``` > > path('postorius/', include('postorius.urls')), > > path('hyperkitty/', include('hyperkitty.urls')), > > ``` > > settings (unfortunately, mailman-web 0.0.8 has these in the wrong > > order). Or you can just delete the 'postorius/' and 'hyperkitty/' > > ones or you can add > > ``` > > ProxyPass "/postorius" "http://127.0.0.1:8000/postorius" > > ProxyPass "/hyperkitty" "http://127.0.0.1:8000/hyperkitty" > > ``` > > to your Apache config. > The odd thing is that the HOWTO that he followed never involves the > manipulation of any urls.py at all - it's not even mentioned at any > point. So obviously the issue is caused by something else and I > suspect something within Apache needs to be re-evaluated in the > guide. I believe this is the Apache configuration the OP is using: <IfModule mod_proxy.c> ProxyPreserveHost On ProxyPass "/mailman3" "http://127.0.0.1:8000/mailman3" ProxyPass "/archives" "http://127.0.0.1:8000/archives" ProxyPass "/accounts" "http://127.0.0.1:8000/accounts" ProxyPass "/admin" "http://127.0.0.1:8000/admin" ProxyPass "/user-profile" "http://127.0.0.1:8000/user-profile" </IfModule> Note that Apache doesn't know about the "/postorius" and "/hyperkitty" URI paths. It is quite unclear to me how this works at all with either the path('mailman3/', include('postorius.urls')), path('archives/', include('hyperkitty.urls')), path('postorius/', include('postorius.urls')), path('hyperkitty/', include('hyperkitty.urls')), version of urls.py or the reverse order version path('postorius/', include('postorius.urls')), path('hyperkitty/', include('hyperkitty.urls')), path('mailman3/', include('postorius.urls')), path('archives/', include('hyperkitty.urls')), I think Mark must have a configuration with ProxyPass "/" "http://127.0.0.1:8000/" in the Apache configuration in mind? Or an alias or rewrite rule. Otherwise I don't see how "/postorius" and "/hyperkitty" paths ever get transmitted to the WSGI server. Steve

1 year, 4 months

Re: Customise Postorius templates?

by Duane Raymond

On Mon, 7 Feb 2022 at 08:46, Philip Colmer <philip.colmer(a)linaro.org> wrote: > The REST API provides a means to customise templates on a list, domain or > site context. > > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > Perhaps I misunderstood, but this seems to focus on the email message templates, and not html Postorius and Hyperkitty templates....or were you suggesting I adapt the script below for use with patches and Postorius and Hyperkitty templates? Seems like a plausible idea of the django template method Abhilash Raj pointed me to doesn't work. > We use a very simple script that takes a text file from the current > directory and, when run locally on a MM3 server, uses the REST API to > update the template on a site context, thus affecting all lists and all > domains on the same server. > > from mailman.testing.documentation import call_http > def update_template(template_name, template_file): > """ Update the specified template """ > print("Updating", template_name) > call_http( > 'http://localhost:8001/3.1/uris', > { > template_name: template_file > }, > method='PATCH', > username="restadmin", > password="restpass" > ) > update_template( > "list:admin:action:post", > "file:///home/ubuntu/mm3-templates/list:admin:action:post.txt" > ) > > The API documentation lists out the various template names that can be > used. > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

3 years, 5 months

Re: Templates do not work

by Eggert Ehmke

It seems my apache vhost settings are messed up. To access the postorius page, I have to use URLs like this: https://lists.[1]tld_/mailman3/mailman3/lists/_ That does not look right, and maybe is the cause of my problem. There are very few guides to set up apache virtual hosts with mailman virtualenv installation. Any hint? Am Donnerstag, 28. April 2022, 19:02:42 CEST schrieb Mark Sapiro: > On 4/28/22 02:50, Eggert Ehmke wrote: > > I created some templates in Postorius to get > > personalized notifications when there are > > moderator requests. The notifications I get seem to > > be the standard texts. When I look into mailman/ > > mm/var/templates > > the directory is empty. Nevertheless, the templates I > > create in Postorius seem to be stored (where?), they > > just do not work. > > As Steve said the templates are stored in the database. > > I suspect the issue is and incorrect value for > `POSTORIUS_TEMPLATE_BASE_URL` in your Django settings. This is used to > construct the URI to retrieve the template. The URI is stored in the > `template` table in the database. It is normally just `http(s)://host.name/` > > If this is the issue, after correcting the setting and restarting the > web service, you will need to delete and re-enter the template in > Postorius to correct the `template` table entry. -------- [1] https://lists.ftv-spandau.de/mailman3/mailman3/lists/

3 years, 2 months

Re: footer template priority

by Mark Sapiro

On 6/19/25 14:30, Sam Darwin via Mailman-users wrote: > Thanks. That fixed it. > > Comments: > 1. In the docs, the instructions say "POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000'. As a reader, you are thinking, I'm running both hyperkitty and postorius. Hyperkitty is at /archives/ and postorius is at /mailman3/ . What about the path '/mailman3/ for postorius? > The doc could mention the path even if it's to explain why it's not needed. (The reason perhaps it's not needed is root will redirect to '/mailman3/'.) I'm guessing you are looking at https://docs.mailman3.org/projects/mailman-web/en/latest/settings.html#mail… Although the name of the setting includes Postorius, the definition there says "Base URL where Django/Mailman-web would be listening for requests." I.e., the base URL for accessing Django, not Postorius. > 2. This all seems very self-referential. The setting goes into settings.py which is the website for postorius itself. It is accessing itself. > Given that's the case do you really need to tell Django about it's own URL? Doesn't it know it's own URL already? Could Django just contact itself without being configured? It and in this case Postorius know the /mailman3/... part, but they don't necessarily know the appropriate base url for accessing the Django WSGI. > 3. Logging... when it can't find the templates, does it log an error anywhere? Mailman's outgoing runner logs an error to the mailman.error log, usually written to mailman.log. The not at all descriptive log message says "Cannot connect to SMTP server <configured smtp_host> on port <configured smtp_port>", but it only logs it the first time and not again until there is a successful delivery. This issue is https://gitlab.com/mailman/mailman/-/issues/514 which I am in the process of fixing. > 4. The server had been up for a year. After I rebooted, the problem vanished, even after removing the new setting. So either it's caching the setting in Redis, or else the problem is really gone. Very strange. See https://gitlab.com/mailman/mailman/-/issues/514#note_101644301 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 1 week

Mailman-users search results for query "Postorius"