Search results for "Postorius" - Mailman-users

Re: Understanding of members, accounts

by Mark Sapiro

On 5/11/20 5:15 PM, Peter Adebahr via Mailman-users wrote: > Is the solution to "sign up", using one's very e-mail address already in > the system? Yes. The address is in the Mailman Core part of the systen, but not in the web UI part. > I would like to understand why there is a difference between being > (only) a subscribed member and a member having an account - or, what > might be the advantage of being a member without an account? Being a mailing list member is a Mailman core concept. It usually says you receive posts from the list based on your delivery status and you can post based on your moderation status. Logging in to the web UI to access HyperKitty and Postorius is a Django concept and requires a Django account. If all you want is to post by email and receive messages from the list, you don't need a Django account, but to manage your user settings via Postorius and to visit private archives, you do. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

Re: After server upgrade debian 11→12 and reinstalling everything in (venv), I got this error when accessing → mailman3/lists

by Mark Sapiro

On 9/5/25 03:37, Wikinaut wrote: > It's going about the variable $mailinglist_url in footers. Mark exlained, that in mm >= 3.3.10 this placeholder can be used in footers, given, that you have set up $base_url. > > This does not work for me. I need to know, WHERE to set $base_url to make $mailinglist_url become working and replaced in footers. The base url setting for this is an attribute of the domain. Setting it in the Domains view of Postorius or via REST will not be available until the next release, I.e. Mailman core 3.3.11, Postorius 1.3.14, Mailman Client 3.3.6. In the mean time with Mailman core 3.3.10, you can set this via `mailman shell` or by directly updating the `domain` table in the database. In mailman shell >>> d = getUtility(IDomainManager).get('mydomain') >>> d.base_url = 'https://mydomain/mailman3/lists' >>> commit() -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months

Re: Multiple domain problem

by Lars Bjørndal

Hi, Marik! I realized that I had two variables in settings.py where the domains is listed, and one of them had a preceding https. I've now followed the documentation for configuring Apache here: https://docs.mailman3.org/en/latest/install/virtualenv.html#apache-configur…. I want both domains to start mailman3 when contacting example1.com/mailman3 and example2.com/mailman3. I have the sam configuration in both virtualhost section in Apache. For example1.com/mailman3, it works perfectly. For example2.com/mailman3 however, the browser (elinks), reports Host not found: example2.commailman3 e.g. without a slash after the domain name. What could cause this to happen? Thanks Lars On Fri, Feb 10, 2023 at 11:59:02AM -0800, Mark Sapiro wrote: > On 2/10/23 01:43, Lars Bjørndal wrote: > > On Thu, Feb 09, 2023 at 02:05:09PM -0800, Mark Sapiro wrote: > > > On 2/9/23 13:21, Lars Bjørndal wrote: > > > > > > > > If I connect to example2.com, the title is example2.com, without the > > > > preceding List index. And the body says Page not found. > > > > > > > > > What's in the browser's address bar for that page? > > > > It's https://example2.com/mailman3/lists/ > > And when you get the Page not found, is it a browser 404 error or a > Postorius error page? > > > > > > > What's in Postorius domains view? > > > > I realized that I have to change SIT_ID to 1 to be able to connect to http://localhost:8000/. Then, when checking Domains, I have both domains with different SIT_ID value (1 and 2). > > > Why are you going to http://localhost:8000/? You should be able to see the > domain's view at https://example1.com/mailman3/domains/ or > https://example1.com/mailman3/domains/ or by just clicking Domains in > Postorius top nav bar. > > > > Going to http://localhost:8000/admin and choosing Sites, I have both domains listed. > > > Again you should be able to go to https://example1.com/admin or > https://example2.com/admin. If these don't work, you need to add directives > in your web server to proxy them to http://localhost:8000/admin > > -- > Mark Sapiro <mark(a)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 > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to lars(a)lamasti.net

2 years, 9 months

Re: Introducing Mailman Web project

by Ralph Seichter

* Abhilash Raj: > For this reason, I decided to combine all the projects together into > a Django project which can be easily installed and run: > > $ pip install mailman-web > # Export Settings for commands to just work. > $ export DJANGO_SETTINGS=mailman_web.settings > $ django-admin migrate > $ django-admin runserver I've tried things a bit differently so I can use the latest version from GitLab, and Things Go Boom(TM): $ python3.7 -m venv venv $ . venv/bin/activate $ pip install -U pip setuptools $ git clone https://gitlab.com/mailman/mailman-web.git $ cd mailman-web/ $ cp docs/mailman-web-example.toml mailman-web.toml $ pip install . $ DJANGO_SETTINGS_MODULE=mailman_web.settings django-admin migrate Traceback (most recent call last): [...] File "/var/lib/nginx/mailman/venv/lib/python3.7/site-packages/postorius/views/user.py", line 34, in <module> from postorius.models import List, MailmanUser File "/var/lib/nginx/mailman/venv/lib/python3.7/site-packages/postorius/models.py", line 223, in <module> class EmailTemplate(models.Model): File "/var/lib/nginx/mailman/venv/lib/python3.7/site-packages/django/db/models/base.py", line 95, in __new__ "INSTALLED_APPS." % (module, name) RuntimeError: Model class postorius.models.EmailTemplate doesn't declare an explicit app_label and isn't in an application in INSTALLED_APPS. Did I miss something? -Ralph

6 years, 8 months

Re: Postorius no connection to REST API

by Mark Sapiro

On 8/12/21 12:01 AM, Richard Rosner wrote: > Mark Sapiro wrote: >>> But whatever is listening on port 8001 is apparently not Mailman's rest >> server. What does >> ps -fww 14080 >> or whatever PID is currently listening on port 8001 show. > > UID PID PPID C STIME TTY STAT TIME CMD > list 15972 15963 0 Aug11 ? Sl 0:13 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1 I had asked "What does ps -fwwa|grep rest show?" and it didn't find this. That was my error. I meant 'ps -fwwA|grep rest' >>> OK. >> Perhaps instead you should have >> uid: list >> gid: list >> in your uwsgi configuration if you don't already. > > Tried that while also switching mailman3-web.service to list:list, exactly the same error. Also, I have /run/mailman3-web/uwsgi.sock owned by list:list now instead of www-data:www-data. All the mailman processes should run as `list` and all mailman related things should be readable and writable by `list`. >>> I'm not familiar enough with this form of ProxyPass using sockets to >> understand what the localhost:8001 does in this context, but uwsgi >> should not be doing anything with port 8001. In a configuration using >> TCP, it would listen on port 8000. Port 8001 is where Mailman's REST API >> server listens. uwsgi should receive connects in your case via the unix >> socket and then pass them to Django via the application in wsgi.py >> Also, you may want other paths proxied to uwsgi, namely at least some of >> hyperkitty, postorius, archives, accounts, admin and user-profile. > > Ok, I removed that port again, now it's exctly like in the automatically generated config file. > And you mean like > > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > ProxyPass /hyperkitty unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > ProxyPass /postorius unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > ProxyPass /admin unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > ProxyPass /archives unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > ProxyPass /accounts unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > ProxyPass /user-profile unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > </IfModule> Yes, I meant if you want those URLs to work, you have to pass them to uwsgi. You don't need all of them. `mailman2` and `postorius` are synonyms as are `archives` and `hyperkitty` However, you could try using TCP to communicate with uwsgi rather than a Unix socket. This means replacing uwsgi-socket = /run/mailman3-web/uwsgi.sock with uwsgi-socket = 0.0.0.0:8000 in your uwsgi.ini file and using directives like ProxyPass "/postorius" "http://127.0.0.1:8000/postorius" ProxyPass "/hyperkitty" "http://127.0.0.1:8000/hyperkitty" ProxyPass "/accounts" "http://127.0.0.1:8000/accounts" ProxyPass "/django" "http://127.0.0.1:8000/django" ProxyPass "/user-profile" "http://127.0.0.1:8000/user-profile" ProxyPass "/mailman3" "http://127.0.0.1:8000/mailman3" ProxyPass "/archives" "http://127.0.0.1:8000/archives" in apache. I am not familiar enough with apache/uwsgi configuration to be of more help. Have you seen https://wiki.list.org/x/12812344 and have you asked Debian for help with their package. They are the ones who should be supporting it <https://www.debian.org/support>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

Re: Can't subscribe on new site/domain

by Mark Sapiro

On 10/10/25 3:46 PM, Flo via Mailman-users wrote: > > I found it, it's in a different directory: > > /var/lib/mailman3/web# sqlite3 mailman3web.db > SQLite version 3.46.1 2024-08-13 09:16:08 > Enter ".help" for usage hints. > sqlite> SELECT * from django_mailman3_maildomain JOIN django_site ON > site_id = django_site.id; > ... > ... > 8|lists.example.com|7|7|Lists of Example|lists.example.com > sqlite> > > The two working domains are first (...) . The problematic domain > (renamed to lists.example.com) appears when I create it in Postorius. > > For me the only conspicuous is that the numbers are 8|.|7|7 while at the > other two entries they are the same for the whole line: 2|.|2|2 and 4|.| > 4|4 . The fields in order are: 1. the id of the django_mailman3_maildomain entry 2. the mail_domain in the django_mailman3_maildomain entry 3. the site_id the django_mailman3_maildomain entry 4. the id of the django-site entry 5. the domain name in the django-site entry 6. the display name in the django-site entry The important things are 2. and 5. which are the mail host and the web host that you see in the Postorius domains view. 3. and 4. are what we joined on so they will always be the same. They aren't related to 1. which is just sequentially assigned when entries are created. 1., 3. and 4. being equal in some cases is a coincidence. The question is what are the other 2 entries. In particular are all 3 values for 2. different and all 3 values for 5. different or are some the same? If 2 of those entries have the same value for 5. and different values for 2., that explains the issue when accessing Postorius at 5. because that web host does not have a unique mail host. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 3 weeks

Re: More Mailman releases!

by Kyriakos Terzopoulos

Also looking good from here. Thanks to all involved for your great work! On Mon, 23 Oct 2023, 16:53 Jered Floyd, <jered(a)convivian.com> wrote: > > Everything looks good to me in my multi-site install! > > I've updated my simple container install to pin the new versions: > https://github.com/jeredfloyd/mailman-container > > --Jered > > > ----- On Oct 22, 2023, at 2:10 AM, Abhilash Raj maxking(a)asynchronous.in > wrote: > > > Hello, > > > > I missed one important merge request in django-mailman3, so here are a > > couple more versions. > > > > I've released Django-mailman3 1.3.11 and Mailman-web 0.0.8 (which > > requires django-mailman >= 1.3.11). > > > > Gitlab releases are available here: > > > > Mailman-web: https://gitlab.com/mailman/mailman-web/-/releases/0.0.8 > > Django-mailman3: > > https://gitlab.com/mailman/django-mailman3/-/releases/v1.3.11 > > > > I have also yanked mailman-web 0.0.7 since that'll cause spurious errors > > due to change in session serializer. > > > > Abhilash > > > > > > On 10/22/23 00:05, Abhilash Raj wrote: > >> 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) > > > > _______________________________________________ > > 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/ > > Archived at: > > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > > This message sent to jered(a)convivian.com > _______________________________________________ > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to kyriakos.terzopoulos(a)gmail.com >

2 years, 1 month

Re: Customise Postorius templates?

by Duane Raymond

Hi Stephan! On Tue, 8 Feb 2022 at 07:02, Stephen J. Turnbull <stephenjturnbull(a)gmail.com> wrote: > Duane Raymond writes: > > > Is anyone out there working on an overhaul of the web interface > > templates > > Yes. There's a big accessibility project being done by a > well-resourced organization. > Great - I'll follow up offlist > I'm not sure how much is still publicly available since the ownership > change, but you might want to look at the Affinity and Empathy > projects at emwd.com. The code is PHP but you may get some ideas from > the UIs. > Yes - that is one one the UIs I've been looking at (available via archive.org if it goes offline). I've also looked at https://gaggle.email and other platforms for UI ideas. I'm still in the scoping-out phase, but am thinking at adapting hyperkitty as the homepage as it has built-in all the variables for list activity (if archived) which means I can leverage the participation and message info to create an enticing, vibrant overview. and then deep link into the postorious interface for list management. subscription management. Cheers, Duane

3 years, 9 months

Re: Postorius 1.2.3 and MailmanClient 3.2.1 is now out

by Jonas Meurer

Abhilash Raj: > On Mon, Jan 28, 2019, at 2:39 PM, Jonas Meurer wrote: >> Abhilash Raj: >>> On Sat, Jan 26, 2019, at 5:10 AM, Jonas Meurer wrote: >>>> Hey Abhilash, >>>> >>>> Thanks a lot for your work on mailman3! >>>> >>>> Abhilash Raj: >>>>> I am very pleased to announce (a bit late) that Postorius 1.2.3 and MailmanClient 3.2.1 is now out. >>>>> >>>>> The full set of changelog can be found in the documentation[1][2]. The most notable feature that >>>>> I can think of is non-member management in Postorius. >>>>> >>>>> New releases are available on PyPI[3][4]. >>>> >>>> For earlier releases, you provided GnuPG signature files to >>>> cryptographically verify that the release files were not tampered with. >>>> >>>> I couldn't find such signature files for the two latest releases. Would >>>> you mind adding them? When packaging for Debian, I prefer to check the >>>> GnuPG signatures before uploading new releases. Also, the signature >>>> files get uploaded to the Debian archive as well so they can be checked >>>> by everybody. That way we can cryptographically proof that the Debian >>>> package is based on the original tarball that got packaged and signed by >>>> upstream. >>> >>> >>> Ah, sorry about that. I completely forgot about that. >>> >>> I am not sure if I can upload signatures after uploading the tarballs, I'll try to find out if that is possible. >> >> Thanks a lot, that would be awesome. I'll wait for it before doing the >> Debian package uploads. > > If it is not possible to upload signatures, I'll bump up patch versions > and push out new tarballs with signatures. Perfect, thanks a lot! >> Just to let you know: we're close to soft freeze in Debian, so in order >> to get those uploads into the next stable release (Buster), they'll have >> to be uploaded rather soon. > > Can you give a rough estimate on how long do we have before the freeze? See https://release.debian.org/buster/freeze_policy.html. For getting new releases into Buster, the full-freeze (2019-03-12) is relevant. Since packages per default take five days to transition from Unstable to Testing, 2019-03-06 would be the last day to upload. But given that we're all busy with other things and stuff, we better not calculate that tightly ;) >> The same holds for other pending releases of Mailman3 components: Just >> in case you plan to do new upstream releases anytime soon, it's still >> possible to upload them to Debian in time for Buster. > > I'll see if we can get other releases out too. Core doesn't yet have any backwards > incompatible changes, so I might end up bumping minor version and doing a > new release. Not sure much has changed in other components, but I can do > a release if there are enough changes. Sure, that would be awesome. Ideally after my recent merge requests got accepted ;) Cheers jonas

6 years, 10 months

Installed from Howto_Install_Mailman3_On_Debian10, web not quite working

by volkmar＠grote-family.com

Hi, today I installed MM3 with Nginx on Debian 11 following the document with a bit of "Mailman 3 installation experience" thrown in (many thanks to the authors!) with some minor changes, i.e. no encryption, and "re_path" instead of "url". I cannot get the web interface to run. "admin" is OK, but Postorius und Hyperkitty refuse to show up with > Page not found (404) > Request Method: GET > Request URL: http://127.0.0.1:8000/mailman3/lists/ > > Using the URLconf defined in urls, Django tried these URL patterns, in this order: > > ^$ > ^postorius/ > ^hyperkitty/ > ^user-profile/delete$ [name='mm_user_account_delete'] > ^user-profile/$ [name='mm_user_profile'] > ^accounts/ > ^admin/ > > The current path, mailman3/lists/, didn’t match any of these. > > You’re seeing this error because you have DEBUG = True in your Django settings file. Change that to False, and Django will display a standard 404 page. The error logs are all OK, the GET requests are logged without any error. My urls.py: > (venv) mailman@me:/opt/mailman/mm$ grep -v "^#" urls.py > from django.contrib import admin > from django.urls import include, reverse_lazy, re_path > from django.views.generic import RedirectView > > urlpatterns = [ > re_path(r'^$', RedirectView.as_view( > url=reverse_lazy('list_index'), > permanent=True)), > re_path(r'^postorius/', include('postorius.urls')), > re_path(r'^hyperkitty/', include('hyperkitty.urls')), > re_path(r'', include('django_mailman3.urls')), > re_path(r'^accounts/', include('allauth.urls')), > # Django admin > re_path(r'^admin/', admin.site.urls), > ] It must be something either really complex or, most likely, rather stupid. I switched from PC Assembler and C to Unix shell scripts some three decades ago, so I must admit that my Python skills are zero, my idea of the inner workings of all the packages is very vague. Any hints where I may look for installation errors? TIA Volkmar

2 years, 6 months

Mailman-users search results for query "Postorius"