Search results for "Postorius" - Mailman-users

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

8 months, 2 weeks

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/ >

2 years, 9 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/

2 years, 6 months

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

4 years, 1 month

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

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

7 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

6 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?

5 years, 5 months

Re: Postorius performance with over 1000 pending users

by Mark Sapiro

On 6/11/19 5:05 AM, Nick wrote: > > In trying to learn more about preventing spam registrations, what methods does > Postorius successfully employ to reduce spam signups through the > "anonymous_subscribe" form? Only those implied by the list's Subscription Policy. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

Create new list styles via Postorius

by Torge Riedel

Dear all, I have found this documentation on list styles: https://mailman.readthedocs.io/en/latest/src/mailman/styles/docs/styles.html Is there any way to create and configure list styles via Postorius web interface? Thanks in advance Torge

5 years

Mailman-users search results for query "Postorius"