Search results for "Postorius" - Mailman-users

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

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

8 months, 1 week

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

7 years, 4 months

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

4 years, 4 months

Re: Disabling Mass operations

by Mark Sapiro

On 1/23/26 17:39, iMark wrote: > Hi All, > > Can anyone give me a pointer on disabling "Mass operations" > (subscribe/removal) in Postorius. > > Just removing the menu link from the list-owners administration pages > would be a good start. This patch will do that ``` --- a/src/postorius/templates/postorius/menu/list_nav.html +++ b/src/postorius/templates/postorius/menu/list_nav.html @@ -84,6 +84,7 @@ {% if user.is_superuser or user.is_list_owner %} <li class="nav-item"><a href="{% url 'list_template_list' list.list_id %}" class="nav-link {% nav_active_class current 'templates' %}">{% trans 'Templates' %}</a></li> <li class="nav-item"><a href="{% url 'list_settings' list.list_id %}" class="nav-link {% nav_active_class current 'list_settings' %} ">{% trans 'Settings' %}</a></li> + {% if user.is_superuser %} <li class="dropdown nav-item"> <a href="#" class="{% nav_active_class current 'list_mass_ops' %} dropdown-toggle nav-link" data-bs-toggle="dropdown" role="button" aria-haspopup="true" aria-expanded="false"> @@ -98,6 +99,7 @@ <li><a href="{% url 'mass_removal' list.list_id %}" class="dropdown-item">{% trans 'Mass removal' %}</a></li> </noscript> </li> + {% endif %} <li class="nav-item"><a href="{% url 'list_bans' list.list_id %}" class="{% nav_active_class current 'list_bans' %} nav-link">{% trans 'Ban List' %}</a></li> <li class="nav-item"><a href="{% url 'list_header_matches' list.list_id %}" class="nav-link {% nav_active_class current 'list_header_matches' %}">{% trans 'Header filters' %}</a></li> <li class="nav-item"><a href="{% url 'list_delete' list.list_id %}" class="{% nav_active_class current 'list_delete' %} nav-link">{% trans 'Delete' %}</a></li> ``` Some lines in the above may be wrapped but basically it just adds {% if user.is_superuser %} and {% endif %} around the Mass operations code. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 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

3 years, 1 month

Re: Core, Hyperkitty and Postorius releases

by Mark Sapiro

On 5/14/21 2:16 PM, Odhiambo Washington wrote: > > root@gw:/usr/home/wash # ls -al /usr/local/include/sass > total 104 > drwxr-xr-x 2 root wheel 512 Apr 16 16:49 . > drwxr-xr-x 176 root wheel 10240 Apr 19 18:05 .. > -rw-r--r-- 1 root wheel 2369 Apr 8 11:08 base.h > -rw-r--r-- 1 root wheel 10742 Apr 8 11:08 context.h > -rw-r--r-- 1 root wheel 6632 Apr 8 11:08 functions.h > -rw-r--r-- 1 root wheel 6489 Apr 8 11:08 values.h > -rw-r--r-- 1 root wheel 198 Apr 8 11:08 version.h > > I imagined I needed an executable. > > drwxr-xr-x 2 root wheel 512 Apr 16 16:49 sass Those are headers for compiling some sass. Possibly you actually have a `sassc` installed in which case you may need COMPRESS_PRECOMPILERS = ( ('text/x-scss', 'sassc -t compressed {infile} {outfile}'), ('text/x-sass', 'sassc -t compressed {infile} {outfile}'), ) in your settings_local.py. See https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html#instal… and the Sass compiler section at https://docs.mailman3.org/en/latest/install/virtualenv.html#dependencies. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

Re: Different Mail Domain Cause Key Error

by Mark Sapiro

On 4/21/20 10:12 PM, Torge Riedel wrote: > Am 21.04.20 um 23:08 schrieb Brian Carpenter: >> Maybe I can get the client to agree to use the web domain as part of >> their list address. > > Hi, > > maybe it is a solution for you what I did on my side (since it was > already the setup for mailman2 my customer is happy with it): > > Set everything up in mailman3 with lists.domain.com and define in > postfix (if you use postfix, others should support it also) aliases from > - let's say - list1(a)domain.com -> list1(a)lists.domain.com for each mail > list. > > In the list setup in mailman3 (available via postorius) define > list1(a)domain.com as an allowed alias for list1(a)lists.domain.com This is a good workaround, however to be complete, you may also want MTA aliases for the list1-*(a)domain.com addresses. Note, I'm currently working on a fix for <https://gitlab.com/mailman/postorius/-/issues/394>. Hopefully that will be in the next Postorius release. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

SSO

by Stephen J. Turnbull

bryan.kartzman(a)yu.edu writes: > Is it possible to set up SSO so that once users (owners,moderators) > set up an account in Postorius on the mailman3 server we have > created , they can authenticate against Azure to login instead of > the password for the local account Postorius created? Probably yes. This depends on how Azure passes on authentication data. I've done this with Shibboleth as the SAML 2.0 Service Provider. It's basically one line in /etc/shibboleth/attributes.xml[1], one line in the httpd conffile, and a short Python library wrapping Django's backend and middleware for the RemoteUser[2] class. I also populate the Mailman User profile with display name, email, etc, from the Identity Provider requiring one line per additional attribute in the same places. If this basic architecture works for you, depending on your WSGI provider, you may be able to eliminate the httpd conf. If you don't care about anything but the user id, you may be able to use the stock RemoteUser class. But I know nothing about how Azure does authentication, so I'll leave it there for now. Footnotes: [1] I've probably spelled that incorrectly, but you'll know it when you see it. :-) [2] This one, too. :-/

3 years

Mailman-users search results for query "Postorius"