Search results for "Postorius" - Mailman-users

Re: only show mail domains from web host on web-host-url

by Mark Sapiro

On 3/19/21 11:14 AM, Jens Günther wrote: > Just checked again and saw: > > - in the setup it works perfectly in Hyperkitty, that's nice > > - for the first web host I have 2 mail domains registered, so it also > matches (unfortunately) with what you said :-( > > Anyway, I dceleted one of it, still both lists are shown on either web > host, so it's generally not working. I don't know why this didn't work. If there is only one mail host in the domains that has the current web host as its web host, it should work. > If I can do something on this issue, please advise me. Thanks. The issue is that neither Postorius or HyperKitty as a direct way of getting lists by web host as the web host information is not an attribute of the list. We have to see which mail hosts are associated with the current web host and then display only those lists that match one of those mail hosts. The issue with Postorius is if there was more than one mail host associated with the web host, this code https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/views/list… could be relatively easily made to work by extending all_lists to include all the mail hosts, but it wasn't clear to me how to fix https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/views/list… in the case where there was more than one mail host. If you can suggest a fix, that would help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

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]

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.

10 months, 4 weeks

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

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

5 years

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, 9 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]

2 years

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, 5 months

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.

2 years

Re: Changing default language for lists

by Wessel Kraaij

Hi, thanks for your response. I realize my question was underspecified. What happened: I changed several defaults in mailman core (e.g. preferred language). However, Postorius (maxking version) initializes the defaults for new lists and overrides the core defaults using a PATCH call on the REST API. With the aid of some gentle AI chatbot, I was able to fix the problem in Postorius, by patching the list.py file to read and apply defauls from the config file (in maxking's version that is setting_local.py). I am talking about Dutch. Here is the code snippet that solved my issue from django.conf import settings as django_settings for key, value in getattr(django_settings, 'DEFAULT_LIST_SETTINGS', {}).items(): list_settings[key] = value list_settings.save() (added in list_new) I added the following 'defaults' in my settings file: DEFAULT_LIST_SETTINGS = { 'preferred_language': 'nl', 'subscription_policy': 'confirm', 'default_member_action': 'defer', 'default_nonmember_action': 'hold', 'reply_goes_to_list': 'point_to_list', 'reply_to_address': '', 'max_message_size': 10240, 'anonymous_list': False, 'dmarc_mitigate_action': 'munge_from', 'collapse_alternatives': False, 'dmarc_mitigate_unconditionally': True, } This way each new list is properly initiated. Best regards, Wessel > -----Oorspronkelijk bericht----- > Van: Stephen J. Turnbull <steve(a)turnbull.jp> > Verzonden: zaterdag 11 april 2026 19:25 > Aan: Wessel Kraaij <wessel.kraaij(a)outlook.com> > CC: mailman-users(a)mailman3.org > Onderwerp: [MM3-users] Changing default language for lists > > Wessel Kraaij writes: > > > How can I change the default language for lists (and other > defaults)? I > changed it in mailman-core but Postorius overrides > these core defaults with > a patch. > > You need to be more specific about what you did, what you expect to happen > in various cases, and what you mean by "patch". > > Specifically, what language do you want as default, how did you spell it in > mailman.cfg, have you checked that there are no list-specific settings (that > override the default), is the problem in distributed posts, in Mailman- > generated notifications, or in web pages? > Specifically which part of posts, notifications, or web pages have unexpected > languages? What language are they supposed to be, and what > language(s) do you see? > > For context, here is how language setting works: > > In mailman.cfg (usually located at /etc/mailman3/mailman.cfg), there is a > `default_language` variable in the [mailman] section (hardcoded to "en" if not > overridden). This can be overridden on a per-list basis, usually configured > using Postorius. Postorius has read-only access to the default_language > setting, I believe, but I am not aware of any way for Postorius to set it. > > The settings in Mailman core directly control which language's templates and > gettext substitutions are used in emails generated by Mailman and in footers > and the like added to posts distributed by Mailman. In any given context, for > each substitution, the list's language is checked for a translation, then the site's > default language, then English is the fallback. You can end up with mixed > languages if some contexts have not been translated. > > Postorius and HyperKitty both use their own templates which are separately > provided in those packages. As far as I know they do not have a default > language setting of their own (although the Django framework probably does, > we don't use that). Instead, through the `mailmanclient` library they read the > current list's preferences (and Postorius can change the list preference but not > the site default), and fetch templates and variable substitutions in the same > way. It is quite possible that the language you specified is missing the > translations you're looking for, or that the language code you specified is not > one that Mailman recognizes. > > > I am using the docker version of maxking > > I don't think that matters, but Abhilash (maxking) is the only real expert on > docker-mailman, and he's not following this list closely at this time. Check the > docker-mailman documentation for the preferred method of communicating > with him if it seems to be relevant. > > Regards, > Steve > > -- > GNU Mailman consultant (installation, migration, customization) > Sirius Open Source > https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fww > w.siriusopensource.com%2F&data=05%7C02%7C%7Ca86b6a6a504d4285dc > 8508de97ef499c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C6 > 39115251139974756%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGki > OnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjo > yfQ%3D%3D%7C0%7C%7C%7C&sdata=EBR2PY36Mm5nldbPpSwT%2FgEuIe > CnuD6JqHUhGEE6GEM%3D&reserved=0 > Software systems consulting in Europe, North America, and Japan

7 months

Mailman-users search results for query "Postorius"