Search results for "Postorius" - Mailman-users

Postorius Suggestion: Give owner a view of all users of all owned lists

by Stephen J. Turnbull

Andreas Vetter writes: > A list of all addresses subscribed to all lists owned by the logged > in person. This is starting to take a better form. It's still very specialized, so I'm starting to wonder if trying to add it to Postorius is a great idea. Of course if people are coming in over the network, you don't want to reproduce all the authentication and authorization logic implemented in Django and Postorius. That may as well be done in Django, and if you're doing Django it may as well be Postorius too. But if you're in a single sign-on environment so presence in the network implies strong authentication, you will get more flexibility from local scripts using mailmanclient, or if you're confident in security access to the REST API directly. Just putting that out for your consideration, since implementing what is taking shape here would take quite some time as the folks skilled with Postorius are not so active these days. > Owner is the primary target group for that. But since it should be > a tool for managing subscriptions in a simple way, it might also be > of interest for superusers. For me as a superuser it would make > life easier. [...] > Ah, I see the problem and agree: So, the presentation should have a > sorted and searchable list of addresses and a Button next to each > address, maybe labeled "Subscriptions". Looking at your description above, for superusers that is basically the Users tab, though. Users are identified by primary address, and you'd not see alternate addresses in the list. But presumably your internal users use their @your.org addresses as primary. Can you make clear what could be more streamlined for your use cases as superuser? I give one example below, maybe that's what you're mostly interested in. The caveats about access to User objects still apply for owners, so even if they look the same (which is a good UX idea if owner functionality is a subset of superuser functionality, also they might even be able to share the basic page templates), the implementation is going to be rather different. I suspect you superusers would be quite frustrated if using the "subscribe all these lists" functionality meant you couldn't get at the User object without going to a different page. I do see one weird thing: you can't manipulate subscription itself from the User page as seen by the superuser from that list, only toggle moderation and delivery mode. I guess that's reasonable for a lot of use cases, though. I've never wanted to do a subscribe or unsubscribe from there. I always have a long list of users to subscribe to specific lists, never a list of lists a specific user should belong to, > The presentation given when above "Subscriptions" Button is clicked > should contain the address as kind of Headline. Then a table of > all lists of the logged in owner and next to each mailing list an > indication, if the address is subscribed or not and a Button to > toggle subscription/unsubscription. May be a single Toggle Button > or (maybe better) two buttons, a suscribe and a unsubscribe button, > where one is greyed out. This would not work with the current User page as presented to a superuser, that's true. The current presentation is quite suited to its purpose, with sections for Addresses, Subscriptions, Ownership, and Delete User in that order. But especially for superusers, there are plenty of sites with thousands, even tens of thousands of lists, and even a paged or scrollable presentation would be awful UI, and the potential for a disastrous mistake using "do all" is high. > In addition my owners would like to have a "unsubscribe from all my > lists" button. And a "subscribe to all my lists" button. This might > be visually nicer, when having the two-button approach above. I wonder if your owners really want "subscribe all". "Unsubscribe all" does make sense for separations, of course, and they wouldn't necessarily be terminations. It would be useful in an internal transfer where "delete user" is not a solution. But in my experience specialized channels tend to proliferate but the same people are likely to be running them as run the department-wide lisst. > In our case we would want to (un-)subscribe the address in a "do > it, don't ask anyone" fashion, but maybe this is not a good idea in > general. What do you think? I think we would implement it similarly to the mass subscribe for multiple addresses case, where the list owner can decide how much bureaucracy to require of the subscriber. You'd want to be careful to make sure address verification is done at most once (for your use case, probably not at all). And there would be some things that could be done to arrange that most lists would have sensible defaults. > Yes, I agree, but policy here is to get rid of subdomains, and that > falls on our feet now. Well, once we figure out how to implement domain ownership, it wouldn't be hard to adapt that technology to "departments" that are administratively distinct but share mail and/or web domains. The main problem would be deciding whether and how to nest them. Superuser > domain owner > list owner > moderator is pretty obvious, but how "department owner" would fit in is less so.

4 months, 3 weeks

Re: MM3 does not receive gmail-Members!

by Mark London

On 4/24/2023 5:11 PM, mailman-users-request(a)mailman3.org wrote: > The Postorius Domains view will show you the SITE_ID for your domain. > In /etc/mailman3/settings.py you probably have > SITE_ID = 1 > Change that to the value from the Postorius Domains view. > If you have more than one domain, you can set > SITE_ID = 0 > and that should show the domain from the http request. Mark - I encountered the same problem and it wasn't clear from the documentation what to do about it. So I eventually changed the name from example.com using the /admin link. But if I now set SITE_ID = 0, and restart the server, it is not happy and tells me it encountered an error. raise self.model.DoesNotExist(django.contrib.sites.models.Site.DoesNotExist: Site matching query does not exist. I guess I should just let it be set to 1 and be done with it? - Mark

2 years, 3 months

Re: combine postorius and hyperkitty into one Apache vhost

by Mark Sapiro

On 12/29/22 12:58, Eggert Ehmke via Mailman-users wrote: > So you prefer Gunicorn over uWSGI? When I have a working installation that > uses uwsgi, should I reconfigure for Gunicorn? At the moment I see no reason > for this, and while I am open for alternate solutions, ... No, don't change. If uWSGI is working for you, it's fine. I prefer Gunicorn and recommend it for new installations because it's already installed as a dependency of Mailman core, at least if the web UI is on the same machine as Mailman core, and because I think its configuration is simpler than uWSGI. uWSGI does have an advantage in that it can be configured to start qcluster eliminating the need to do that separately. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

Mailman3 stopped working after Upgrade to Ubuntu 21.04

by Thomas Möhle

Hey, I have set up mailman3 with mailman3-web on my mailserver and after upgrading to Ubuntu 21.04 my setup stopped working. I can see repeating log entries of mailman trying to reach something within hyperkitty and getting an error. The same constant repeating cycle of log entries is visible in my log files. I have attached my config files as well as the logfiles for mailman3 and mailman-web. As you can see, I'm not really getting many errors, yet within 5 seconds there are almost 2000 lines of log entries where mailman tries to reach something within hyperkitty over and over and over again. One thing I did to create an error message is start up both services, then edit a test list, that I created, in the web interface. This is the error you can find in the logs then: ERROR 2021-08-07 12:50:26,932 2343625 postorius Un-handled exception: HTTP Error 404: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/postorius/views/generic.py", line 74, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 97, in dispatch return handler(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/postorius/views/list.py", line 301, in get primary_email = set_preferred(request.user, mm_user) File "/usr/lib/python3/dist-packages/postorius/utils.py", line 77, in set_preferred mm_user.preferred_address = primary_email.email File "/usr/lib/python3/dist-packages/mailmanclient/restobjects/user.py", line 57, in __setattr__ super(User, self).__setattr__(name, value) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py", line 131, in __setattr__ return super(RESTObject, self).__setattr__(name, value) File "/usr/lib/python3/dist-packages/mailmanclient/restobjects/user.py", line 145, in preferred_address response, content = self._connection.call(url, {'email': email}) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 127, in call raise HTTPError(url, response.status_code, urllib.error.HTTPError: HTTP Error 404: WARNING 2021-08-07 12:50:26,938 2343625 django.request Not Found: /mailman3/postorius/lists/test.lists.example.com/ Can anyone here help me debug this? I'm working on this problem for days now and can't seem to find a solution. Thanks so much in advance, Thomas

3 years, 11 months

Re: add custom styles to postorius list creation menu

by mhazan＠mandint.org

Le 2022-05-03 09:44, mhazan(a)mandint.org a écrit : > Le 2022-05-02 17:32, Mark Sapiro a écrit : >> On 5/2/22 06:39, Michael Hazan wrote: >>> Hello, >>> >>> When creating a list via postorius, i can see 3 style appear >>> (announce, discussion, private). Is it possible to either create a >>> new style and add it to that list or modify one of those style ? >> >> >> See this thread >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… >> >> > > Thanks i will look into setting up that plugin, hopefully an easier > way to do that can make it's way to the default install. working on that plugin, i have found where to inserts the various setting, however it's not clear what types and possibles value are excepted for each ? ie "advertised" is bool True/false, but what about "default_member_action" ? i've tried hold 'hold' "hold" all throw error when trying to apply the style. i cannot find the types in the documentation and all the other non bool settings. >>> Also, coming from mailman2, you could directly set the members post >>> moderation action when subscribing, now you can only do it via the >>> user menu, is there a way to automate this in mm3 ? >> >> >> I don't understand what you mean here. In MM 2.1 a member had only one >> setting - moderated yes or no and if moderated there was a list >> setting for the moderation action. There was also a list setting for >> whether new members were moderated by default. How were you setting >> the new member's moderation when subscribing? >> >> You are correct that when subscribing a new member, the member gets >> the default action for members and different action has to be set in a >> separate operation. I don't think this is significantly different from >> MM 2.1. Also, can you describe what you mean by "automate this". > > in MM2.1, if you set the list to moderated and default action to hold > posting, you can set a some member to be un-moderated (mod bit off) to > automatically allow their posting. In the web interface of MM2.1 there > is a checkbox with moderated bit on/off on the member list itself, in > the postorius interface for MM3 you have to open each members settings > page to access that. For automation, as list owner, upon registering a > member (via mass subscription) the possibility to change that ? also > the me too/dupe setting for example. > > Thanks > _______________________________________________ > 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/

3 years, 2 months

Re: hyperkitty web site

by Gelpi Andrea

Il 28/04/20 19:10, Mark Sapiro ha scritto: > On 4/28/20 9:40 AM, Gelpi Andrea wrote: >> >> If in django administration I rename that site it works. >> >> But having more than one domain this is not a solution. >> >> what i need is to separate different domains >> >> https:/website1/mailman3/hyperkitty shows some lists >> https:/website2/mailman3/hyperkitty shows other lists > > > There are issues with FILTER_VHOST. See > <https://gitlab.com/mailman/postorius/-/issues/394> for the Postorius > issue. This will be fixed for Postorius in the next release. > > For HyperKitty, the issue is > <https://gitlab.com/mailman/hyperkitty/-/issues/254>. This is not yet fixed. > > Currently, if FILTER_VHOST is True, HyperKitty only shows lists in the > index for which the list's domain matches the domain in the accessing > url with a leading 'www.' stripped. > > E.g. list(a)example.com will only show on the index if the accessing URL's > host is example.com or www.example.com, but not if it is say > lists.example.com. > Thank You I just discovered it. I put a workaround for now in index.py so also list.example.com works. # Domain filtering if settings.FILTER_VHOST: domain = request.get_host().split(":")[0] if domain.startswith("www."): domain = domain[4:] #gg# Added by Gelpi if domain.startswith("list."): domain = domain[5:] domain = "@%s" % domain mlists = mlists.filter(name__iendswith=domain) Regards -- Gelpi ing. Andrea -------------------------------------------------------------- It took the computing power of three C-64s to fly to the Moon. It takes a 486 to run Windows 95. Something is wrong here. --------------------------------------------------------------

5 years, 3 months

Re: best pratice - set default MM settings and make them update-save

by Mark Sapiro

On 5/16/22 07:16, Stefan Bauer wrote: > > Is there also a way to have this box checked by default or do not request a > verifcation at all? > Could not find any flag in base.py. To have the box checked by default would require a patch to Postorius like this. ``` --- a/src/postorius/forms/list_forms.py +++ b/src/postorius/forms/list_forms.py @@ -1073,7 +1073,7 @@ class ListMassSubscription(forms.Form): pre_verified = forms.BooleanField( label=_('Pre Verified'), - initial=False, + initial=True, required=False, help_text=_( 'If checked, users will not have to verify that their ' ``` Not requiring verification at all would require patching Mailman core but would be a bad idea as it could allow someone to subscribe anyone without that person's consent. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

Re: FILTER_VHOST = True doesn't work fine with alias_domain

by Mark Sapiro

On 2/17/22 15:15, Élodie BOSSIER via Mailman-users wrote: > Hello, > > My mailman3 installation is now functional, but the config "FILTER_VHOST > = True" doesn't work fine when I define "alias_domain" for the 2 > domains. I need to define that because I need to get "postfix_vmap" file. > > As you can see, list from others domains are visible on this URL : > https://ml.franceserv.fr/postorius/lists/ > > I would like https://ml.franceserv.fr/postorius/lists/ and > https://ml.viticreation.fr/postorius/lists/ with their own lists. There are issues with FILTER_VHOST due to the fact that mailing lists do not have a web host attribute. This means when you go to HyperKitty or Postorius when FILTER_VHOST is True, we look up the domain record for the web host you are visiting and show you all the lists whose mail host matches the mail host for the web host domain. This has nothing to do with alias domains. What that means is if all your domains records have a unique mail host, FILTER_VHOST will work as you expect, but if multiple domains have the same mail host FILTER_VHOST will show you the lists for the current web host plus all those with a matching mail host. I.e. if in your case, the ml.franceserv.fr domain and the ml.viticreation.fr domain have the same mail host, FILTER_VHOST won't separate them. If they have different mail hosts FILTER_VHOST will separate them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

Re: Deactivate list without deleting it?

by Colin Watson

On Wed, Jan 17, 2018 at 04:34:48PM +0900, Stephen J. Turnbull wrote: > Colin Watson writes: > > I possibly should have explained our situation in a little more > > detail. > > Well, I was pretty clear on your requirements, it turns out. I don't, > and I believe I'm in agreement with the rest of the team here, need to > know why you want something (at least not at this "let's see if we can > hash out the requirements and the design a bit" stage). After all, > even if we end up WONTFIXing it, it's open source and we're happy to > talk about how you might do something even if we won't do it for you! I appreciate that approach. At the same time, I also asked because I suspected I didn't quite understand the design principles involved. Thanks to both you and Barry for clarifying the intent of IArchiver; I'll drop that idea. > > Postorius wouldn't come into it in our case > > That's an interesting detail. Thing is, at present Postorius *is* the > "control panel" for the whole suite (all the best bands are run by > their bassists, you know), so we would bring it up if you left it out. I'm not ruling out using it in future, but right now I think we'd prefer to stick with the approach of having the "control panel" integrated tightly into LP. > However, if you don't want to use Postorius, I think the > mailman-client functionality will make it strightforward to implement > your UI within Launchpad, and it now includes a nicer CLI so if you > prefer to implement core and Hyperkitty functionality before the > Launchpad side, mailman-client will allow you to test core features at > that stage. Indeed. And I'd managed to miss the existence of mailmanclient, so thanks for bringing that up. > > I'd been thinking more of a new enum in HyperKitty for the visibility > > state, since it does seem like quite an archiver-specific thing. > > Well, there is an enum in core for it already. I'm not sure how that > works currently (specifically, how you go about telling Hyperkitty if > that changes). Keeping that in sync is an issue (at least for us), > since Postorius can query it, IIRC. I just looked into what HK does, and I notice that it syncs the archive policy from Core as part of a regular update job. So I think the answer is that we just use that: perhaps set the ArchivePolicy to private and arrange that nobody has the ability to view it other than maybe list owners, or possibly add a new item to ArchivePolicy that's something like "deactivated" or "hidden". At any rate that looks a lot more tractable since most of the mechanism already exists. Thanks, -- Colin Watson [cjwatson(a)ubuntu.com]

7 years, 4 months

Re: Mailman3 on virtual domains

by Lars Bjørndal

[Mark] [...] > > Ok, so I have to create an alias_domain in Mailman. Is it possible to do that from the web interace? > > It has been in postorius since 1.2.0. Mine is 1.3.8. > > > I find an Edit button for each domain, and then I may change name and description. But I can't find an option to add an alias_domain. As I'm blind, and using a text only browser, some information may have been missing. Or can I do it from the command line? > > If your Postorius is >=1.2.0, there should be 3 fields on the Edit domain > page - Description, Alias Domain and Web Host. The whole page looks > something like: [...] Thanks, got it. I was confused becasue there are two Edit buttons on the prior page, one right above SITE_ID number and another (the button I had to use) inbetween Templates and Delete. Thanks a lot for your assistance! Lars

1 year, 9 months

Mailman-users search results for query "Postorius"