Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: New year releases!

by Mark Sapiro

On 1/4/23 14:41, Mark Sapiro wrote: > On 1/4/23 13:54, Dan Caballero wrote: ... >> File "/var/www/mailman-www/urls.py", line 20, in <module> >> from django.conf.urls import include, url >> ImportError: cannot import name 'url' from 'django.conf.urls' >> (/opt/mailmanve/lib/python3.9/site-packages/django/conf/urls/__init__.py)" > > > In Django 3.1 django.conf.urls.url was a deprecated alias to > django.urls.re_path and in Django 4.0 it was removed. See, e.g. > <https://docs.djangoproject.com/en/3.2/ref/urls/> and > <https://docs.djangoproject.com/en/4.0/ref/urls/>. > > However, the above Traceback doesn't identify which module contains the > > from django.conf.urls import include, url Looking more closely, I see that it does. It is /var/www/mailman-www/urls.py. That file probably has contents like ``` from django.conf.urls import include, url from django.contrib import admin from django.urls import reverse_lazy from django.views.generic import RedirectView urlpatterns = [ url(r'^$', RedirectView.as_view( url=reverse_lazy('list_index'), permanent=True)), url(r'^postorius/', include('postorius.urls')), url(r'^hyperkitty/', include('hyperkitty.urls')), url(r'', include('django_mailman3.urls')), url(r'^accounts/', include('allauth.urls')), # Django admin url(r'^admin/', admin.site.urls), ] ``` That needs to be changed to ``` 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), ] ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: Converting discussion list to read-only list (settings)

by Mark Sapiro

On 10/14/19 5:40 PM, Paul Arenson wrote: > > Uh-oh: I AM LOST AGAIN. (will all caps give me a larger font?) Messages in HyperKitty on this list (but probably not yours as this is still an experimental feature) are rendered with a subset of Markdown (see, e.g., <https://en.wikipedia.org/wiki/Markdown>) If you look at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>, the things which are in large font are that way because you underlined them with hyphens as in Second Level Heading -------------------- This only affects rendering in HyperKitty. I read this list by email so the posts I receive are plain text and I see the above as something like Second Level Heading -------------------- -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

[MM3-users] Re: re-sending confirmation mails (was Re: Re: pending subscriptions lost?)

by Mark Sapiro

On 3/15/22 15:20, Andreas Barth wrote: > > Debian (as all distributions) freezes their packages when releasing, > that's why it's called stable. If someone wants newer packages, it's > possible to use stable-backports (see below). > > Debian oldstable has mailman3 version 3.2.1. > Debian stable has mailman3 version 3.3.1. > > So, in this case, the version in Debian oldstable is used. Which is, > well, a bit behind stable, because oldstable is one release behind > from the current stable. I understand that, but even Debian sid has mailman3 3.3.3-1 and mailman3-web 0+20200530-2 which are quite old for a package like Mailman 3 which is still in active development. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: Migrating from mailman-suite to mailman-web

by Mark Sapiro

On 6/4/22 09:09, Andrew Hodgson wrote: > Hi. > > Any pointers in migrating from Mailman-suite to Mailman-web? I'm interested specifically in configuration changes required to Gunicorn in order to bring up the Django project using Mailman-web. mailman-suite is really just an example containing a Django settings file and urls.py and wsgi.py. mailman-web is a package which installs Mailman's web UI including HyperKitty and Postorius. Neither of these addresses the wsgi server per se. It could be Gunicorn, uWSGI, Apache mod_wsgi or possibly something else. Apparently you are using Gunicorn and want to continue to do so. I think the only required changes to Gunicorn might be file system paths. What specifically are you concerned about? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

[MM3-users] Re: Which file does 'account_login' in login.html point to?

by Mark Sapiro

On 5/8/25 09:31, Kim Sunggun via Mailman-users wrote: > In /opt/mailman/venv/lib/python3.9/site-packages/django_mailman3/templates/account/ > > <form class="login form-horizontal" method="POST" action="{% url 'account_login' %}"> #<-----------Here See /opt/mailman/venv/lib/python3.9/site-packages/allauth/account/urls.py which contains ``` urlpatterns = [ path("login/", views.login, name="account_login"), path("logout/", views.logout, name="account_logout"), path("inactive/", views.account_inactive, name="account_inactive"), ] ``` and the `account_login` url points to `login` /opt/mailman/venv/lib/python3.9/site-packages/allauth/account/views.py The templates in /opt/mailman/venv/lib/python3.9/site-packages/django_mailman3/templates/account/ are essentially all redefinitions of those in /opt/mailman/venv/lib/python3.9/site-packages/allauth/templates/account/ for the purpose of adding django_mailman3 styling. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

[MM3-users] Re: Missing Archived emails - Hyperkitty - CERT Issue

by Mark Sapiro

On 7/28/25 7:07 AM, willie.castillo(a)caemilusa.com wrote: > Looks like "hyperkitty" stopped archiving right after the CERT for the mailman3 website expired, How can I make the missing archives visible on the website? I see there "*pck" files in the/opt/mailman/mm/var/archives/hyperkitty/spool/ directory. The list archive does not show that last posting [of 25 July 2025. > > ~$ ll -t /opt/mailman/mm/var/archives/hyperkitty/spool/ > -rw-rw---- 1 mailman mailman 98215 Jul 25 12:01 1753459289.7901242+f3fd7ee77272862f8c1023394bf88d0d4bbe9053.pck > -rw-rw---- 1 mailman mailman 98109 Jul 25 12:01 1753459289.7726512+ee1264c36a194eb0ec1a52089f053e6963f24369.pck > -rw-rw---- 1 mailman mailman 88479 Jul 25 12:01 1753459289.7564857+2e27f35a57f757f058dc95e34c56722a76307900.pck > > The CERT on the website is now up-to-date Those queued messages will be reprocessed on the next post. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: Is logging.subscribe working in /etc/mailman.cfg?

by Mark Sapiro

On 12/11/18 2:11 AM, ktso(a)cuhk.edu.hk wrote: > I have put the following in /etc/mailman.cfg and restart mailman. An empty file can be created but nothing can be logged when admin or non-member subscribe/unsubscribe. Anything I have missed? So far I can only see log appear in mailman.log and smtp.log. Thanks. > > [logging.subscribe] > path: subscribe.log > level: debug The above is correct. As far as not seeing things in the log, very little is logged in the subscribe log. Only (un)subscription requests held for moderator approval and moderator approval of held unsubscribes but not subscribes. In other words, unless your list's subscription police includes 'moderate' nothing will be logged in subscribe.log. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 8 months

[MM3-users] Re: mailman shell

by Mark Sapiro

On 1/2/19 7:12 PM, Alan So wrote: > Sorry for my ignorance. May I know what should be imported before using mailman shell within Python? > > $ python3.6 > Python 3.6.6 (default, Aug 13 2018, 18:24:23) > [GCC 4.8.5 20150623 (Red Hat 4.8.5-28)] on linux > Type "help", "copyright", "credits" or "license" for more information. >>>> command = cli('mailman.commands.cli_withlist.shell') > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > NameError: name 'cli' is not defined > > Link to documentation: https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/shell.ht… That's too complicated. Just run mailman shell as a command. If you want to operate on a single list, run mailman shell -l <list_id> Also see mailman shell --details -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 7 months

[MM3-users] Re: User settings triggers error

by Mark Sapiro

On 6/18/20 2:23 PM, Mark Dadgar wrote: > > There is definitely something sketchy going on here. As an admin, I am not getting accurate subscription status about people on a list. For example, I search for a list member, find their listing, check the box and click Unsubscribe Selected, and get an error because it turns out that they had already unsubscribed themselves previously. But Postorius thought they were still subscribed. > ... > Could this somehow be related to my recent migration from sqlite3 to postgres? I think it's quite likely that that migration is involved and your database is now corrupted in some way. Exactly how or in what way, I don't know, but it seems likely to me that that's the issue. -- 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

[MM3-users] Re: Cron Error: <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs monthly

by Mark Sapiro

On 2/5/23 01:13, Odhiambo Washington wrote: > > So in my case, I should at least increase the value of > HYPERKITTY_JOBS_UPDATE_INDEX_LOCK_LIFE to, say, 1800? It probably isn't even set in your case and defaults to 900 if it isn't set. Yes, you can set it to a larger value. If your archive search engine is woosh and your archive is even moderately large, 1800 probably isn't nearly enough. There was no indication of timing in your OP, but you should determine when that cron job started and when the error was reported. The difference is the absolute minimum you should set for HYPERKITTY_JOBS_UPDATE_INDEX_LOCK_LIFE, but you should add some margin to that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

Search results for query "sapiro"