Search results for "Postorius" - Mailman-users

Re: Localization of auto-responses, question marks in welcome message

by Claus-Justus Heine

Am 25.04.22 um 08:41 schrieb Stephen J. Turnbull: > Claus-Justus Heine via Mailman-users writes: > > > Kind thanks for the response. I have to apologize: my "test user" had > > its preferred language set to en_US, so that was the reason for the > > question marks. So this was indeed a user-error (i.e. my fault). > > But we'd like to have that user get the English version of the > message. One of two things seems reasonable: > > 1. You have customized the German template, but not the English > template. In that case, I think it makes sense for Mailman to > assume the German template has important information that the > English does not, and send the German template with its > appropriate encoding (UTF-8, nowadays). The fact that en_US can > be encoded in ASCII should not affect the encoding of the de > template, ever.[1] I have installed custom templates using the REST API and pointing MM3 to some download URIs. So MM3 has custom templates for particular lists, but I did not yet install different templates for different languages. Still I would also prefer that MM3 would assume that all template text are UTF-8, independent from the language. > > 2. You have not customized the German template. In that case the > user should get the default English template. > > How do those sound to you, as goals for Mailman behavoir? > > So ISTM this is a Mailman issue, if Mailman is sending out the German > message with question marks substituted for non-ASCII characters, or > if Mailman is sending out the German message with US-ASCII as the > Content-Type charset parameter. The only way I can see this as a user > (admin) issue is if you overwrote the English template with German > (and even then, it's nuts for Mailman not to use UTF-8 for English > what with directed quotes, emoji, and all the other enhancements to > the character repertoire that US English speakers use). > > Can you tell me a little more about whether you configured any custom > templates, and if so, how? That is, did you use the Postorius text > field or overwrite files directly? I am installing download URLs pointing to a Nextcloud via the REST API described here: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… However, I did not care to use URL placeholders for the language which probably I should have done. However, the RTD page only talks here about the list's preferred language, not the user's preferred language. What strikes me more that for the localization of the auto-response subjects the global setting default_language of the server seems to be relevant and not the particular list's preferred language. Claus > > Steve > > > Footnotes: > [1] Note to self: perhaps the admin UI can check the list of > supported languages and warn if some but not all are customized. > > _______________________________________________ > 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/ -- Claus-Justus Heine himself(a)claus-justus-heine.de http://www.claus-justus-heine.de/ Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de

3 years, 3 months

Re: Sending a message to a subscription applicant when a subscription request is made

by Allan Hansen

Thank you, Mark. That makes sense. And, as you suggested, this will not work for me, because a lot of people log in and then apply to more lists. I can't exhort them to get the accounts set up and do their subscription maintenance while logged in, and they tell them that if they want to sign up for another list they have to log out first. __ I do need to find another way. I suggested these options: a. That we change the lines in the Python program in our installation that send 'list:admin:action:subscribe' to the list admins to instead send the template to the applying subscriber. b. That we change the lines in the Python program in our installation that send 'list:user:action:subscribe' to the subscriber with an unverified address to always do this, even when the incoming address has already been verified. c. That the current 'list:user:action:subscribe' be changed in published Mailman 3 source to 'list:user:action:confirm' and a new template ''list:user:action:subscribe' be set up to be sent when any subscribe request is made. This is more work, of course, so not likely a good thing to hack locally. It could be useful to other users. Of course, (a.) and (b.) are preferred in the short term, as I'd like to get our procedure simplified. Any idea which file to change for either, and some suggestion as to what to change? Yours, Allan On 3/28/23, 10:18, "Mark Sapiro" <mark(a)msapiro.net <mailto:mark@msapiro.net>> wrote: On 3/28/23 09:19, Allan Hansen wrote: > Mark, > > I tried doing this. > I unsubscribed myself from a list, set the policy as you suggest and re-applied. > I got no confirmation messages but as moderator I got the moderate message. How did you reapply? with the subscribe policy confirm then moderate a new subscriber should get the list:user:action:subscribe message and have to confirm before the request waits moderation? However, see below. > I then tried a bogus email and saw that a message was sent to that and no moderator message to me. > Would the server skip the verification message because I'm a moderator/admin? It's not because you are an admin. It's because you were logged in when you subscribed from the list's info page. You will need to confirm if you subscribe anonymously without logging in or subscribe via email, but if you are logged in to Postorius when you request subscription, that is sufficient confirmation that the request really comes from you, so you don't get an email confirmation. So, depending on your circumstances, this may or may not work for you. -- 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/> Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org <mailto:mailman-users@mailman3.org>/message/D4WXXVOHXTDLRDGXV66GV4BAMWBRYEPF/ This message sent to hansen(a)rc.org <mailto:hansen@rc.org>

2 years, 4 months

Importing Mailman 2 Lists apart from Django

by Brian Carpenter

Hello Mailman Users, Are there instructions on importing a Mailman 2 list into a Mailman 3 core installation only? Does the import21 script not need Django/Postorius/Hyperkitty? It seems Django is required to import archives I guess because of the use of Hyperkitty. How about importing archives without having a Django installation? Is that what the prototype archiver for? We are getting ready to start working on a custom forum application for Mailman 3 (called Empathy) and I am would like to import some mailman 2 archives into the development server to work with. Thanks. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

5 years, 3 months

Re: Mailman REST API not available. Please start Mailman core.

by Mark Sapiro

On 7/26/20 12:00 AM, joseverde(a)gmail.com wrote: > Okay, so I got the webservice of Mailman3 up and running, but when I go to mailman3/postorius/lists/, I get the following error: > > Something went wrong > Mailman REST API not available. Please start Mailman core. Do your settings in the webservice section of mailman.cfg for things like: admin_pass: restpass admin_user: restadmin hostname: localhost port: 8001 (Defaults shoun) match your Django settings MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = 'restpass' MAILMAN_REST_API_URL = 'http://localhost:8001' Also, is Mailman's `rest` runner running ps -fwwA|grep runner=rest should show 3 processes. The runner and 2 workers. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

changing default preferred language of list

by Paul Paulchen

Hi MM community, need a little advise. We're running mailman in a Docker Container (maxking) Mailman Core Version GNU Mailman 3.3.5 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.8.10 (default, May 6 2021, 06:30:44) [GCC 9.3.0] As far as I understood, it should be pretty easy. My wish: every new list we create has a default value for the preferred language: de (instead of us) Like described here: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… We put the values in: [mailman] default_language: de "/etc/mailman.cfg" and "/opt/mailman/mailman-extra.cfg" Nothing changes. When I create a new list via Postorius, is see the preferred language is US. Am I missing something? Is the default always US? And I have to change it manually? Cheers in advance! Paul

3 years, 4 months

lists.mailman3.org web site.

by Mark Sapiro

I have just upgraded the lists.mailman3.org Mailman 3 installation to the heads of the GitLab mailman* branches. A major change is the switch from Persona to Django Allauth. This requires some configuration which isn't yet complete. Hopefully it will all be working very soon. In the mean time if you want to log in to Hyperkitty/Postorius you should be able to log in with your email address. The first time you do this, Mailman probably won't even know your password so you'll have to request a reset. Once you have reset your password, you should be able to log in. I hope to have several social auth choices working very soon. -- 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: Hiding an ML from a site

by Odhiambo Washington

On Thu, Feb 8, 2024 at 4:57 PM Jeremy Stanley <fungi(a)yuggoth.org> wrote: > On 2024-02-08 10:43:37 +0300 (+0300), Odhiambo Washington wrote: > [...] > > Looking at Postorius, they do have different mail hosts. > [...] > > Are you using the magic SITE_ID=0 in your settings file? For our > deployments, that was necessary to get it to auto-detect which > filter to apply based on the domain name used by the browser. > -- > Jeremy Stanley > Yes, I do have that in settings_local.py -- 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]

1 year, 5 months

Re: Join a Mailman 3 list?

by Stephen J. Turnbull

Hi, Although I'm replying to Thomas, I'm going to address this message to Cathy. Thomas Ward via Mailman-users writes: > You'll have to talk to EMWD to see if your archives will be kept > with the migration. They have a completely custom web interface for > archival. When I talked with Brian several years ago he emphasized that moving to Mailman 3 at EMWD would be seamless. Presumably that would include moving the archives, which is quite straightforward if you're starting from a stock Mailman 2.[1] > EMWD uses their **own custom UI** for management and archiving. > This means that we can't give you any real guidance on EMWD and > such for how it relates to user management, etc. This isn't really a problem though. Either way, the new UI will be new to your administrators, and EMWD has historically had an extremely good reputation for working with administrators on such things.[2] But your *subscribers* are *not* using the web interface. Perhaps that will change, but you aren't worried about that, rather that Mailman 3 will enforce use of a web UI. It won't -- if your users don't personalize their profiles in Mailman 2, there's no need for them to start in Mailman 3. The intermediate case is the moderators, but I bet you are doing little or no moderation, and again, EMWD is probably happy to help their clients with that level of education. Also, you did mention the archives. If users are using the archives, the UI will change (either EMWD or HyperKitty). I would expect that could be an issue. As far as that going, EMWD probably has client- focused lists that use their web UIs that you could subscribe to, or perhaps are already subscribed to! I haven't looked at the mockups of Affinity etc that Brian published in years, but at the time they seemed streamlined compared to Postorius and HyperKitty. Between the fact that the "email-only" day-to-day operation you have with Mailman 2 will continue without a hitch with either stock Mailman 3 web UIs or EMWD web UIs, and Brian's pride in his work, I think that you should run, not walk, to EMWD and ask them the same questions. Of course all of my estimates of what EMWD would or would not be happy to do should be confirmed by asking them! Moving to a different hosting service or setting up your own server would be another matter, but as long as you're continuing to work with EMWD whom you find trustworthy, the sooner you move the better. Steve Footnotes: [1] There were enough differences between the Mailman 2 and 3 web UIs that he wasn't going to force anyone to upgrade. Organizations that depend on using the web UIs for their daily workflow could have their efficiency degraded while people learned the new system. This is especially true for the new EMWD web UIs for configuration and archives. But he was confident that the transition would not cause long interruptions in service or changes in the way you send, receive, and work with mail. [2] Working with even dozens of users is another matter, and I can imagine that EMWD would draw the line there. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

2 months

Re: How to change the language in mailman3

by Mark Sapiro

On 7/22/20 2:45 PM, Massimo Zappalà wrote: > OK thanks, > I solved it by creating the paths > > /usr/lib/python3/dist-packages/mailman/locale/it/LC_MESSAGES > /usr/lib/python3/dist-packages/django_mailman3/locale/it/LC_MESSAGES > /usr/lib/python3/dist-packages/postorius/locale/it/LC_MESSAGES > /usr/lib/python3/dist-packages/hyperkitty/locale/it/LC_MESSAGES > > Then I run this command: > sudo msgfmt django.po -o django.mo Except, based on paths above, Mailman Core's message catalog is not /usr/lib/python3/dist-packages/mailman/locale/it/LC_MESSAGES/django.*. It is /usr/lib/python3/dist-packages/mailman/messages/it/LC_MESSAGES/mailman.* There should already be a mailman.po there which can be translated with msgfmt mailman.po -o mailman.mo -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

Re: Mailman 3 installation from latest Debian packages

by Brian Carpenter

On 2/12/21 7:49 AM, Matthew Blissett wrote: > I found https://lists.gem5.org/archives/list/gem5-announce@gem5.org/ > which is running the same version, but presumably not using these > Debian packages as the Javascript is slightly different. > > Could this be a problem with the Debian packaging, or perhaps my > configuration -- which is very close to the defaults (i.e. Mailman and > Apache configuration generated by dpkg). > > Has anyone set up a working installation using these packages? The above reference URL is actually one of our clients running on one of our Mailman 3 shared servers. Mailman 3/Postorius/Hyperkitty were all installed using a virtual environment via pip. I don't use packages at all for our Mailman 3 installations. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 5 months

Mailman-users search results for query "Postorius"