Search results for "Postorius" - Mailman-users

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/

4 years

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

3 years, 4 months

Re: Changing default language for lists

by Wessel Kraaij

Thanks Stephen, I see your point. I am aware of the limitations of the patched list.py, but it is documented for myself (and uses the bind volume mechanism to persist). I lack the time to develop a plugin for my purposes. I basically want to set defaults my lists and this mechanism is simple and works. I am not sure how such a new plugin should be combined with my stack, perhaps an additional docker package. Seems overkill. Kudos to the mailman community that this software is still maintained. Best regards, Wessel > -----Oorspronkelijk bericht----- > Van: Stephen J. Turnbull <steve(a)turnbull.jp> > Verzonden: zondag 12 april 2026 19:42 > Aan: Wessel Kraaij <wessel.kraaij(a)outlook.com> > CC: mailman-users(a)mailman3.org > Onderwerp: [MM3-users] Re: Changing default language for lists > > Wessel Kraaij writes: > > > I changed several defaults in mailman core (e.g. preferred > language). > > Do you mean "default_language"? There is no default "preferred language"; > that's a list-specific setting. > > And what do you mean by "changed in mailman core"? Settings in > mailman.cfg? Source patches? > > > However, Postorius (maxking version) initializes the defaults for > new lists > and overrides the core defaults using a PATCH call on the > REST API. > > I don't understand why that would happen. The core defaults are the source > of the initial values in the create list form. Specifically, when Postorius creates > a list, it initializes a proxy object in mailmanclient, which talks REST API to > Mailman core, which creates an actual MailingList object. This uses the > defaults from the system_defaults object or default style if one is defined. This > is reflected in Postorius's proxy MailingList, which is used to initialize values in > the form presented to the administrator. Then they can change various > aspects of the list's identity including preferred language from that form. > > So if you have set default_language in the [mailman] section of mailman.cfg, > you should get the desired initial preferred language for your lists. > > As far as I know, this hasn't been reported before. It's not happening to most > installations (and many of them do specify default_language). It's true that > docker-mailman is not the most common configuration, but it does use stock > mailman and postorius from PyPI. So I really don't understand why you have > a problem if you are creating mailman.cfg correctly. > > > With the aid of some gentle AI chatbot, > > Heaven preserve us from *all* AI chatbots, gentle or violent. All are sources of > bad advice and annoyance to volunteer software maintainers. > > You absolutely should not need to patch any code to do what you want to do > with preferred_language. > > > Here is the code snippet [added to list_new in > postorius/views/list.py] > that solved my issue > > This is a bad idea. You will have to remember to patch Postorius again if you > ever update it. Also, if for some reason you ever create lists using the > `mailman create` utility, `mailman shell`, or a REST API client, these settings will > not be applied to those lists. > > > 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, > > } > > Most of the settings above cannot currently be changed in mailman.cfg. > However, you can create a plugin to do this without patching any sources. The > example plugin > <https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit > lab.com%2Fmailman%2Fexample-mailman- > plugin&data=05%7C02%7C%7C4de498f0fbc14109513f08de98bada66%7C8 > 4df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C639116125477808558 > %7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAu > MDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C > %7C%7C&sdata=qVKt2jUFxn7mHxRWi1%2FstTE18d6rbG4VNJPlPkYPP0I%3D > &reserved=0> shows how to create a trivial style (as well as several > components you don't need). > See documentation in > https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdoc > s.mailman3.org%2Fprojects%2Fmailman%2Fen%2Flatest%2Fsrc%2Fmailman > %2Fplugins%2Fdocs%2Fintro.html&data=05%7C02%7C%7C4de498f0fbc141 > 09513f08de98bada66%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0 > %7C639116125477828811%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1 > hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIl > dUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=NUT4CJaIVuKuN08asfLm7Z6bn > N7i0PI4TPOYccC5xgY%3D&reserved=0. > For examples of styles, see mailman/styles/default.py. To change the default > style, edit (or add) the "default" setting in the "[styles]" > section of mailman.cfg. > > 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%7C4de498f0fbc1410951 > 3f08de98bada66%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C6 > 39116125477844590%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGki > OnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjo > yfQ%3D%3D%7C0%7C%7C%7C&sdata=WkOqcCK3aQR1pAc79rzJKQN4%2B > MR%2B7DbAmnUIx3z%2FDA4%3D&reserved=0 > Software systems consulting in Europe, North America, and Japan

3 weeks, 5 days

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

6 years

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

8 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

4 years, 2 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

2 years, 7 months

[MM3-users]Re: mailman 2 vs. mailman 3: what happened to multipart/digest?

by Simon Hanna

On 05/14/2016 07:11 AM, Mark Sapiro wrote: > On 5/13/16 5:05 PM, Simon Hanna wrote: >> On 05/12/2016 09:26 PM, Barry Warsaw wrote: >>> On May 12, 2016, at 12:18 PM, Mark Sapiro wrote: >>> >>>> It is the intent that Postorius will eventually expose all these >>>> settings. We're not there yet. At present you could possibly do this by >>>> interacting with mailmanclient, although I'm not certain the settings are >>>> exposed there. >>> >>> I'm not sure if they're exposed in mailmanclient, but they are exposed in the >>> core's REST API, on the member resource. It's the `delivery_mode` attribute >>> and it takes as legal values one of 'regular', 'plaintext_digests', >>> 'mime_digests', and 'summary_digests' (IOW, the enum item names for the >>> DeliveryMode enum). > >> They are exposed in mailmanclient and are used in postorius. They can be >> found in the users personal subscription settings >> https://lists.mailman3.org/mailman3/accounts/mailmansettings/ > > > You are correct. When I checked this before my initial reply, I never > pulled down the Delivery Mode list to see all the options. My bad. > > However, please correct me if I'm wrong, but there does not appear to be > a way in Postorius to set a list's mime_is_default_digest attribute. > You've got that one right. But I don't think core is exposing this through rest. At least it's not exposed via mailmanclient.

9 years, 11 months

Re: Splitting hosts: mta&core vs postorius

by Ruth Ivimey-Cook

Stephen, On 6/22/20 6:23 PM, Stephen J. Turnbull wrote: > By design, Mailman core doesn't need to talk to the Internet or to the > secure internal network -- Internet functions are delegated to the MTA > and the webapps, and local configuration is via shell access which in > principle could be console. Sorry, I missed this earlier. Ironically I am doing exactly what you are suggesting -- splitting the django frontend web app from the mailman core. In my current case I have put the mailman core on the same host as my mailserver, but that was for the sake of simplicity while I got that split sorted -- I am using exim and there is a big benefit when exim can see the list directory names. I may eventually move mailman-core elsewhere. However, I find the mailman shell program not very intuitive, and so would prefer to have the web app for admin purposes. Regards, Ruth

5 years, 10 months

Mailman-users search results for query "Postorius"