Search results for "Postorius" - Mailman-users

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

9 years, 3 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, 10 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

6 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

5 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

4 years, 10 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 > } > >

4 years

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

6 years, 1 month

Re: at the finish line of mailman3 docker, but can't sign in.

by bob B

ok ./manage was the piece I was missing so getting closer :). I set the MAILMAN_ADMIN_EMAIL in the .yaml, but what url do I use to login ? http://mailman.domain.com/postorius/lists/. **This url does not like the email address I used for forget password. or http://mailman.domain.com/admin **** this url has no password reset option I added that environment variable "MAILMAN_ADMIN_EMAIL" after i already upped my containers, But I then ran "docker-compose down" then "docker-compse up -d". Does that reload and setup everything again? or could that be the issue? When I tried to send the test email it said "socket.gaierror: [Errno -2] Name does not resolve" sp maybe my mailman-web container can get dns???

4 years, 4 months

Re: mailman3 on new Debian 12 installation, got ssl apache working on all URLs except /mailman3

by Stephen J. Turnbull

Philip Bondi writes: > Again. We're almost there with ssl apache configs. You're done with the Apache configuration for Mailman suite, it's working. That's what the error message "Service Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later." means: "We got through to your server, but it is having problems right now." The problem arises after successfully connecting to the WSGI service. Since everything but location /mailman3 (including /postorius, which invokes the same views as /mailman3) is working, then most likely the configuration for /mailman3 in urls.py is either missing or corrupted. Steve

8 months, 3 weeks

Re: still up to date?

by Abhilash Raj

On Tue, Aug 27, 2019, at 7:14 AM, mailman3(a)malevil.cc wrote: > I have subscribed to the following rss feeds to keep track of updates: > > https://libraries.io/pypi/mailman/versions.atom > https://libraries.io/pypi/mailman-hyperkitty/versions.atom > https://libraries.io/pypi/HyperKitty/versions.atom > https://libraries.io/pypi/postorius/versions.atom > https://gitlab.com/mailman/mailman-suite/commits/master?feed_token=yitiVdhX… > > but none of them was updated for half a year, is that actually the > status? No current releases or updates for mailman3? I am planning a new release, but waiting to find some time to fix a blocker issue in Hyperkitty. > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking)

6 years, 3 months

Mailman-users search results for query "Postorius"