Search results for "Postorius" - Mailman-users

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>

1 year, 7 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/

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

4 years, 4 months

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

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

9 months, 2 weeks

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

4 years, 4 months

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

3 years, 9 months

Re: nginx configuration on a multitasking server

by David Newman

On 12/10/21 12:57 PM, Mark Sapiro wrote: > On 12/10/21 10:22 AM, David Newman wrote: >> >> 1. At least on my system, the proxy_pass statement will only run >> without errors if I change this to a fully formed URL, e.g., >> 'proxy_pass http://127.0.0.1:8000'. Is this a typo in the docs? > > > I changed it at > https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura… > but I wonder if we shouldn't be using `uwsgi_pass` instead of proxy_pass. > > See https://nginx.org/en/docs/http/ngx_http_uwsgi_module.html#uwsgi_pass > > Are you using uwsgi or some other wsgi server. uwsgi, per the venv and PDF docs. Thanks for the fix. Regarding the uwsgi_pass docs, would 'uwsgi_pass_header' directives replace the 'proxy_set_header' ones in the venv doc? Looking at the uwsgi doc, it seems they might do different things. >> 2. What document root(s) and alias(es) to use for Postorius and >> Hyperkitty and the Django admin on a server that also runs other >> services (e.g., Postfix for non-list mail and Roundcubemail)? > > > If you can separate Mailman from other services by subdomain Alas, I can do that for all but one of the subdomains I have in production. For the past 15 or so years, users of that subdomain have used mail.domain.tld for MM2, roundcubemail, and an admin web UI that manages regular mail. The "/" has gone to roundcubemail, and users to go other directories for the other services. For example, MM2 users currently go to /mailman. , you can > configure them separately and for Mailman, root is irrelevant as > everything is proxied or aliased in a location directive. For example, > Mailman on the server that supports this list uses the > lists.mailman3.org domain and we have (excerpted) > ``` > server { > listen 443 default_server; > root /usr/share/nginx/html; > index index.html index.htm; > # root and index are probably irrelevant as we never go there > server_name lists.mailman3.org; > ssl on; > #ssl stuff > location / { > proxy_pass http://127.0.0.1:8000/; > # other proxy stuff In this example, / goes to MM3. The assumption here and in the MM3 docs is that we're standing up a dedicated server where MM3 pages should be served as the default. That's a totally valid design decision, and one could argue it's superior to running a bunch of other services on one machine. It's not the situation I have to deal with, though. Short of changing a long-standing URL, what I'm looking to do is have "/" continue to default to roundcubemail, and have users type in longer URLs for MM3 and other services. You're right that the root and index directives above are irrelevant since / goes to MM3 via proxy. What I'm asking is what root(s) and location(s) to use with nginx where MM3 isn't the default. Thanks again! dn > } > location /static/ { > alias /var/spool/mailman-web/static/; > } > location /robots.txt { > alias /usr/share/nginx/html/robots.txt; > } > location /favicon.ico { > alias /var/www/listorg/images/favicon.ico; > } > } > ``` > And for the other stuff we have > ``` > server { > listen 443; > server_name .list.org mirror.list.org mirror.mailman3.org; > root /var/www/listorg; > ssl on; > # ssl stuff > } > >

2 years, 11 months

Re: Chinese characters in list name shows question mark (?)

by Franklin Weng

Hi Mark, Thanks for your reply. Mark Sapiro 於 2019/10/24 上午6:10 寫道: > >> Is there any other setting I should look at? > > The list's preferred_language setting (Postorius -> Settings -> List > Identity -> Preferred Language. The list welcome message is encoded in > Mailman's character set for the list's preferred_language. If this is > English (USA), the character set is us-ascii. If it is set to Chinese > (Taiwan), the character set is utf-8, and it should work. However in my settings -> List Identity page I didn't see Preferred Language option. https://nextcloud.slat.org/index.php/s/45tGaE7ALgAFQFK What may be possible wrong that I couldn't see Preferred Language settings in the web interface? Thanks, Franklin

5 years, 1 month

Mailman-users search results for query "Postorius"