Search results for "Postorius" - Mailman-users

Re: Postorius permissions granularity

by Odhiambo Washington

On Thu, Dec 11, 2025 at 11:43 AM Liam Reilly <l.reilly(a)ucl.ac.uk> wrote: > Hi, > > Is there a way to have more granular permissions in Postorius than either > User or Superuser? The user permissions that are configurable under > /admin/auth/user/ do not seem to have any effect. > > We have a helpdesk team that would benefit from being able to access all > list pages in the same way as a Superuser, but without the ability to > accidentally delete the mail domain for example. > > Thanks, > > Liam > You can create several superusers. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

6 months, 1 week

Re: hidden list is hidden even to the owner

by Mark Sapiro

On 7/2/20 8:10 AM, Mohsen Masoudfar wrote: > > This is after a long fight with AWS and Redhat versions, I ended up installing the mailman3-full package on Ubuntu18. Installation was straight forward and easy, but it seems it is not easily possible to update/upgrade Postorius alone in this configuration, is it? You can't upgrade Postorius alone in any configuration because the latest Postorius requires recent Mailman core, mailmanclient and django-mailman3. Depending on how the Debian/Ubuntu package installs these things, it may be possible to upgrade them with pip3, but as I don't know the details of how they are installed in this package, I can't say how to do this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

Re: Postorius permissions granularity

by Liam Reilly

Stephen J. Turnbull wrote: > Liam Reilly writes: > > Is there a way to have more granular permissions in Postorius than > > either User or Superuser? > > Not without additional code. It couldn't be a plugin. It would have > to be a fork of the main Postorius code at first (ie, you would be > responsible for patching it and merging our public releases, there > would not be regular releases). I doubt it would be merged in a near- > future release, at least I wouldn't be confident enough to do that > myself without beta testing on a branch. > I don't think it would be hard to implement a "restricted superuser" > role. The annoying part would be figuring out where to apply it, as > the "authenticated user", "moderator", and "superuser" roles are > implemented via Python "decorators" applied to the functions > implementing the various features. And the changes would likely need > to be pervasive in page templates, forms, and functional code. > > The user permissions that are configurable under /admin/auth/user/ > > do not seem to have any effect. > > As far as I know the only bit that has big effects is "superuser", and > there's a "staff" bit that has some effect on the superuser IIRC. > Everything else is implemented in Postorius. > > We have a helpdesk team that would benefit from being able to > > access all list pages in the same way as a Superuser, but without > > the ability to accidentally delete the mail domain for example. > > I almost started on this two years ago, but that customer wanted it > for individual lists rather than a helpdesk team, and realized that > all the relevant owners would be satisfied with promoting moderators > to owner. So it didn't happen. > Footnotes: > [1] There are several consultants who would be capable of maintenance > in the consultant list on the wiki, and more than one who would be > able to design and implement the code if you're in a we-want-it-enough- > to-pay hurry. > -- > GNU Mailman consultant (installation, migration, customization) > Sirius Open Source https://www.siriusopensource.com/ > Software systems consulting in Europe, North America, and Japan Thanks Stephen. It looks like we're going to take the simple route of the helpdesk using existing screen sharing tools to assist list owners, rather than providing elevated access in Postorius. Many of our list owners are not technical and so the transition from Mailman 2 to 3 has been challenging for some.

6 months, 1 week

Re: Unknown attribute: process_bounces

by Mark Sapiro

On 5/18/21 1:29 AM, xlefloch--- via Mailman-users wrote: > Hello, > > I've upgraded my Mailman installation from those versions: > mailman==3.2.2 > postorius==1.2.4 > mailmanclient==3.2.2 > > To those ones: > mailman==3.3.0 > postorius==1.3.3 > mailmanclient==3.3.2 > > I'm having issues in Postorius in the settings section: Unknown attribute: process_bounces. > When i'm printing the settings list for the concerned list retrieved by the REST API, i'am missing all the parameters related to the management of bounces. In the "mailinglist" table of the Mailman database, i have the columns managing these parameters. > > Anyone have any ideas? Postorius 1.3.3 requires Mailman core >=3.3.1 How did you upgrade?. If this was a package upgrade, your packager has produced an incompatible set of components. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

Postorius not HTML-decoding < to "<" characters

by Ron / BCLUG

Andy Smith wrote on 2024-10-30 20:59: > # Block access to the signup form from Tor exit nodes. > <Location /mailman/accounts/signup> > <RequireAll> > Require all granted > Include /etc/apache2/tor-exit-list.conf > </RequireAll> > </Location> If we look at the above message, there are less-than and greater-than symbols around the Apache keywords in the email as expected. If we look at the archived version of the message, we see a slightly mangled representation: # Block access to the signup form from Tor exit nodes. <Location /mailman/accounts/signup> <RequireAll> Require all granted Include /etc/apache2/tor-exit-list.conf </RequireAll> </Location> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Hopefully I've assigned the blame to Postorius accurately and no formatting nor archiving issues make the issue difficult to understand. Thanks.

1 year, 7 months

Re: Postorius admin/user guide

by Odhiambo Washington

On Fri, Nov 8, 2024 at 5:55 PM Florin Pasăre via Mailman-users < mailman-users(a)mailman3.org> wrote: > Hello, > We're trying to update mailman to version 3 from version 2, and I can't > seem to find some non-technical guide for Postorius, something like an > owners manual for all the configurations available in Postorius. > Is there such a thing? > > Thank you, > > Florin > Hi Florin, You cannot "update" Mailman from version 2 to version 3. You will install version 3 and then migrate your lists/archives from version 2 into the version 3 install. That, I think is an "upgrade". The recommended installation method is documented here: https://docs.mailman3.org/en/latest/install/virtualenv.html Once you've completed the installation, you need to create the superuser. The command is: ``` mailman-web createsuperuser ``` The username you create here will be used to log in to Postorius. You can also use the same username/password to login to the Django Admin web UI - https://list-url/admin/ What goes on in Postoirius isn't complex, so do not fear. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 7 months

Re: Customise Postorius templates?

by Philip Colmer

My apologies. I misunderstood what you were trying to achieve. Apologies for the noise :-) On Mon, 7 Feb 2022, 11:57 Duane Raymond, <duane(a)fairsay.com> wrote: > > > 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/ >> >

4 years, 4 months

Re: Mailman notify generating emails for request that aren't visible.

by Simon Coggins

Oops sorry I hit send to soon. If I try to go to /lists/listname.example.com/unsubscription_requests<http://listname.example.com/unsubscription_requests> I get a 404, it looks like unsubscription_requests<http://listname.example.com/unsubscription_requests> isn’t in my urls.py list for Postorius? (venv) [mailman@mailman postorius]$ grep version __init__.py # Software Foundation, either version 3 of the License, or (at your option) # any later version. __version__ = '1.3.4' (venv) [mailman@mailman postorius]$ grep _requests urls.py url(r'^subscription_requests$', list_views.list_subscription_requests, name='list_subscription_requests'), I’m upgrading this week to: django-mailman3 1.3.7 mailman 3.3.5 mailman-hyperkitty 1.2.0 mailmanclient 3.3.3 postorius 1.3.6 And I’ve just confirmed that 1.3.6 does have the url endpoint. So I’m guessing it came in in 1.3.5+? (venv) [mailman@mailman-dev postorius]$ grep version __init__.py # Software Foundation, either version 3 of the License, or (at your option) # any later version. __version__ = '1.3.6' (venv) [mailman@mailman-dev postorius]$ grep _requests urls.py re_path(r'^subscription_requests$', list_views.list_subscription_requests, name='list_subscription_requests'), re_path(r'^unsubscription_requests$', list_views.list_unsubscription_requests, name='list_unsubscription_requests'), -Simon --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 On 1 Nov 2021, at 12:15 pm, Simon Coggins <s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au>> wrote: The version of postorius is 1.3.4 django-mailman3 1.3.5 mailman 3.3.4 mailman-hyperkitty 1.1.0 mailmanclient 3.3.2 postorius 1.3.4 --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 On 1 Nov 2021, at 12:04 pm, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: On 10/31/21 6:11 PM, Simon Coggins wrote: > Hi, > > We’re running mailman 3.3.4 (about to upgrade to 3.3.5 this week). I enabled mailman notify cron a few weeks ago to email out any pending requests for admins. I’ve now got multiple lists that keep emailing out the same outstanding holds but they can’t visible in the GUI. The requests are all duplicates as well. This is a redacted example email: > > -----Original Message----- > From: mailman-alerts(a)example.com<mailto:mailman-alerts@example.com><mailto:mailman-alerts@example.com> > Sent: Monday, 1 November 2021 8:10 AM > To: somelist-owner(a)lists.example.com<mailto:somelist-owner@lists.example.com><mailto:somelist-owner@lists.example.com> > Subject: The somelist(a)lists.example.com<mailto:somelist@lists.example.com><mailto:somelist@lists.example.com> list has 4 moderation requests waiting. > > The somelist(a)lists.example.com<mailto:somelist@lists.example.com><mailto:somelist@lists.example.com> list has 4 moderation requests waiting. > > Held Unsubscriptions: > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com><mailto:john.smith@maildomain.com> > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com><mailto:john.smith@maildomain.com> > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com><mailto:john.smith@maildomain.com> > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com><mailto:john.smith@maildomain.com> > > Please attend to this at your earliest convenience. Your lists are configured with Un-Subscription Policy moderate or confirm, then moderate so unsubs require Moderator approval. What Postorius version is this? Prior to 1.3.3, unsubsubscription requests were not visible in Postorius. In 1.3.3_+ they are available in the Subscription requests dropdown at https://example.com/mailman3/lists/listname.example.com/unsubscription_requ…<https://example.com/mailman3/lists/listname.example.com/unsubscription_requ…> although they may not be counted in the Subscription requests count badge. -- Mark Sapiro <mark(a)msapiro.net<mailto:mark@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<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org>

4 years, 7 months

Re: 12/24 hour clock ?

by Mark Sapiro

On 11/28/20 7:18 AM, Per Jessen wrote: > Hi all > > at openSUSE we have recently migrated to mailman3, and we seem to be > having a couple of teething issues: > > a) hyperkitty and postorius both seem to insist on using a 12 hour clock > format, no matter what the user has set. Is there a way of changing it > system-wide ? This is a Django setting. Try TIME_FORMAT = 'H' in settings_local.py. See https://docs.djangoproject.com/en/3.1/ref/settings/#time-format and https://docs.djangoproject.com/en/3.1/ref/templates/builtins/#std:templatef… > b) overriding the default set of footers - despite having set the > template "list:member:regular:footer" to empty for a specific list, I > am still getting the default footers attached. How did you set the template to empty? it works for me in Postorius from the HEAD of the gitlab branch and should work with any Postorius >= 1.3.0 Note that when you set a template in Postorius, it sets the URI in Mailman core for that template to https://<HOST>/<PATH>/api/templates/list/<LIST-ID>/<TEMPLATE-NAME> where the https://<HOST>/<PATH> part is the Django setting for POSTORIUS_TEMPLATE_BASE_URL. Is that URI accessible from the Mailman core host machine? -- 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: Time Zone Issue in Postorius

by Henrik Rasmussen

> -----Oprindelig meddelelse----- > Fra: Mark Sapiro <mark(a)msapiro.net> > Sendt: 8. februar 2022 07:48 > Til: mailman-users(a)mailman3.org > Emne: [MM3-users] Re: Time Zone Issue in Postorius > > It should be TIME_ZONE = 'UTC' > > Times passed from Mailman core are naive times, I.e. they don't have > time zone info, but they are in UTC. Thus for Django to get the correct > time with time zone you need USE_TZ = True (without that, Django will > throw an exception about naive times) and the TIME_ZONE to apply is UTC. As https://stackoverflow.com/questions/29311354/how-to-set-the-timezone-in-dja… seems to say otherwise ("You can use TIME_ZONE = 'Europe/Istanbul'"), to make sure, am I right to understand it as for Mailman, Danish time should be stated as "TIME_ZONE = 'UTC+1' " with use of "USE_TZ = True"? /Henrik Rasmussen

4 years, 4 months

Mailman-users search results for query "Postorius"