Search results for "Postorius" - Mailman-users

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

4 months, 2 weeks

Re: Confirm and Moderate Unsubscribe Requests

by Brian Carpenter

On 10/21/20 5:39 PM, Mark Sapiro wrote: > On 10/21/20 12:14 PM, Brian Carpenter wrote: >> >> Well I can't dictate that to my list owners and there is no confirm >> token sent with the moderation notice. Why include this option in >> Postorius when it can't be properly handled? > > Postorius is still a work in progress. The unsubscription policies are > in core and are exposed in Postorius. Certainly the ability to moderate > an unsubscription should be in Postorius, but it isn't yet. We are an > all volunteer project and there aren't that many of us, and perhaps I'm > overreacting, but the tone of some of your recent posts seems a bit > demanding. I apologize. I didn't think I was coming across demanding but I am somewhat exasperated at some of these issues. I have a list owner who is now going to get a moderated request notice everyday that he can't do anything about it. But my question still remains: why is this option in Postorius when it can't be handled properly? Surely the option can be easily removed, right? Is the ability to list (via the pending moderation notices tab) and handle (as in the List owner can decide a moderation response) an unsubscribe moderation request there in Mailman core so that I can properly address it via Affinity? -- Brian Carpenter Harmonylists.com Emwd.com

5 years

Re: Editing "automatic responses" tab i Postorius does not work

by Mark Sapiro

On 5/21/17 5:22 AM, David Krantz wrote: > > I am trying to change e.g. the value of "notify admin on membership > changes" through postorius. There are still many settings not yet exposed in Postorius. We are painfully aware of this and will probably be working on some of this at the PyCon sprints starting tomorrow. Until we get more of these addressed, you will need to use tools like "mailman withlist" to set these things. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 5 months

Re: Acceptable aliases defaults to []

by Simon Hanna

>> * Docker-mail 0.1.1 >> * Mailman 3.1 >> * Postorius 1.1.1 >> * Hyperkitty 1.1.1 >> >> Minor issues: >> >> Settings -> Message Acceptance -> Acceptable aliases has a default of [] resulting in "An error occured: [u'[]']" when saving. This fiend should be empty by default or at least accept the default when saving. > Hi. Could you explain where this error happens? Is it in Postorius or the core/REST API? I assume it's Postorius. There is an open issue regarding the aliases: https://gitlab.com/mailman/postorius/issues/58

8 years, 2 months

Re: Postorius 1.1.2 security release

by Marvin Gülker

Am 29. Dezember 2017 um 21:19 Uhr +0100 schrieb Simon Hanna: > The issue is that django 2.0 doesn't support [python2, corrected by me] anymore. Fine, but why does pip then still try to download it? Shouldn't there be a constraint in the metadata for django and/or postorius somewhere that prevents that and forces it to a lower version? Note: The problem is solved for me, see my last post. Greetings Marvin -- Blog: https://mg.guelker.eu PGP/GPG ID: F1D8799FBCC8BC4F

7 years, 10 months

Re: Postorius performance with over 1000 pending users

by Nick

On 06/08/19 at 18:06, Mark Sapiro <mark(a)msapiro.net> wrote: > mailman shell -l your.list.id > util = getUtility(IPendings) > for token, data in util.find(mlist=m, pend_type='subscription'): > util.confirm(token, expunge=True) Thanks! In trying to learn more about preventing spam registrations, what methods does Postorius successfully employ to reduce spam signups through the "anonymous_subscribe" form?

6 years, 4 months

Mailman-users search results for query "Postorius"