Search results for "Postorius" - Mailman-users

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/

4 years, 6 months

Changing default language for lists

by Stephen J. Turnbull

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://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

7 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

6 years

Re: postorius ssl-certificates for virtual hosts

by Mark Sapiro

On 11/15/19 3:45 AM, Wolfgang Bock via Mailman-users wrote: > > That doesn't solve the problem. I changed that in mailman-web.py > (MAILMAN_REST_API_URL = https://localhost:8001) and after that in > mailman.cfg (use_https: yes). But got the same errormessage on postorius > website. You posted this log excerpt: Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - "GET /3.0/lists?advertised=true&count=0&page=1 HTTP/1.1" 200 90 Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - "GET /3.0/lists?advertised=true&count=10&page=1 HTTP/1.1" 200 606 Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - "GET /3.1/domains HTTP/1.1" 200 1438 Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - code 400, message Bad HTTP/0.9 request type The first 3 GETs are a normal sequence of GETs from Postorius when you go to the Mailing Lists view. That should be followed by a GET like "GET /3.1/domains/domain.tld HTTP/1.1" where domain.tld is a configured domain. Do you have any domains configured?/0.9'? I'm not sure what the issue is. You have an older version of mailmanclient < 3.2.3a1 which uses httplib2 rather than requests. https://pypi.org/project/httplib2/ says: HTTP and HTTPS HTTPS support is only available if the socket module was compiled with SSL support. but I don't think this can be the issue because the first 3 GETs work. You might try upgrading mailmanclient to 3.3.0. I don't know if that will help, but it may. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 11 months

More Mailman releases!

by Abhilash Raj

Hello Everyone, I am pleased to announce several new releases for GNU Mailman project. Thanks to all the contributors for making these releases possible! 1. Postorius 1.3.10 [1] 2. Hyperkitty 1.3.8 [2] 3. Django-mailman3 1.3.10 [3] 4. Mailman-web 0.0.7 [4] All the releases are published to PyPI and you can find links to all the PyPI projects: https://docs.mailman3.org/en/latest/ A full list of change logs are available below: [1]: https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-10 [2]: https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-8 [3]: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst [4]: https://gitlab.com/mailman/mailman-web/-/blob/master/README.rst Do note that for Postorius, I released 1.3.9, but I forgot to update dependency metadata to require `django-mailman3>=1.3.10` (which is required for the new bootstrap 5 upgrade across packages) and so I also released Postorius 1.3.10 just after. Installation documentation is available at https://docs.mailman3.org/en/latest/install/install.html and if you are upgrading an existing virtualenv install you can refer https://docs.mailman3.org/en/latest/upgrade-3.2.html If you find any issues, you can report them at the respective bug tracker for the projects. The links to issue trackers are available at https://docs.mailman3.org/en/latest/. Finally, similar to Mailman Core, note that PyPI doesn't accept signatures anymore so each packages' release page now has the tarball uploaded to them along with the signature: Django-mailman3: https://gitlab.com/mailman/django-mailman3/-/releases/v1.3.10 Hyperkitty: https://gitlab.com/mailman/hyperkitty/-/releases/v1.3.8 Postorius: https://gitlab.com/mailman/postorius/-/releases/v1.3.10 Mailman-web: https://gitlab.com/mailman/mailman-web/-/releases/0.0.7 -- thanks, Abhilash Raj (maxking)

3 years

Re: Problems getting started with postorius

by Mark Sapiro

On 11/13/24 16:46, Alain D D Williams wrote: > > I eventually tracked it down. The problem was that I had signed in with an > account "addw@localhost". That, for some reason, failed validation above. > I hacked the database and changed to "addw(a)localhost.localdomain" and creating > the new domain worked. > > I could send email to addw@localhost - so at the MTA level it is correct. > > So please can the initial account creation do the same validation as does > adding a new domain. Mailman doesn't allow local, unqualified addresses, see https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/email/validate… and https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/emai… On the other hand, Account creation/validation is done by django-allauth over which we have no control. > I have looked but cannot find any documentation on postorius than > https://docs.mailman3.org/projects/postorius/en/latest/ > which is not helpful for a user or system admin. Can you point me to something > better. Unfortunately, there is not user/list owner documentation for Postorius. As I said at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… You just have to page through the settings to see what's there. Hopefully the various categories are clear enough that if you're looking for something specific, you can find it easily. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

Re: Setting moderation_action when approving a message from a non-member fails

by Mark Sapiro

On 6/13/23 05:15, Tom Smyth wrote: > > When a message is held due to it being from a non-member, I notice that > Mailman creates a non-member record for the sender automatically. This is > great! > > But if I try to set their moderation action while approving the message in > Postorius, I get: > > Failed to set moderation action: xxx(a)gmail.com is not a member address of > xxx(a)xxx.org > > Is this expected? I would like to be able to set the moderation action for > the non-member that has already been created. > > I am on Postorius v1.3.2. This is <https://gitlab.com/mailman/postorius/-/issues/448>, apparently filed by you, fixed in Postorius 1.3.4 by <https://gitlab.com/mailman/postorius/-/merge_requests/558>. Until you upgrade, you will have to set the non-member's moderation action separately from handling the held message. -- 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: 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

9 years, 5 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

9 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

8 years, 10 months

Mailman-users search results for query "Postorius"