Search results for "Postorius" - Mailman-users

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

4 weeks, 1 day

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

8 years, 11 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

8 years, 8 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, 4 months

Re: Postorius performance with over 1000 pending users

by Nick

On 06/08/19 at 18:06, Mark Sapiro <mark(a)msapiro.net> wrote: > mailman shell -l your.list.id > util = getUtility(IPendings) > for token, data in util.find(mlist=m, pend_type='subscription'): > util.confirm(token, expunge=True) Thanks! In trying to learn more about preventing spam registrations, what methods does Postorius successfully employ to reduce spam signups through the "anonymous_subscribe" form?

6 years, 10 months

Re: Postorius performance with over 1000 pending users

by Mark Sapiro

On 6/11/19 5:05 AM, Nick wrote: > > In trying to learn more about preventing spam registrations, what methods does > Postorius successfully employ to reduce spam signups through the > "anonymous_subscribe" form? Only those implied by the list's Subscription Policy. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

Create new list styles via Postorius

by Torge Riedel

Dear all, I have found this documentation on list styles: https://mailman.readthedocs.io/en/latest/src/mailman/styles/docs/styles.html Is there any way to create and configure list styles via Postorius web interface? Thanks in advance Torge

6 years, 5 months

Re: Create new list styles via Postorius

by Mark Sapiro

On 11/23/19 3:50 AM, Torge Riedel wrote: > > Is there any way to create and configure list styles via Postorius web > interface? Not currently. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

Re: Postorius confirmation mails shown in uwsgi-error.log but not sent

by Ralph Seichter

* Abhilash Raj: > Have you setup email settings for Postorius separately? Yes, I forgot to include that information: $ grep ^EMAIL settings.py EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_PORT = 25 As I said, the MTA does not log connection attempts from the Suite, nor do I find evidence that Django actually tries to send out email. Weird. -Ralph

6 years, 1 month

Mailman-users search results for query "Postorius"