Search results for "Postorius" - Mailman-users

Disabling "delete account" option

by Hitashi mancho

Dear all, Recently, I have migrated from Mailman2 to Mailman3 GNU Mailman 3.3.10 (Tom Sawyer) Python 3.11.9 Some of the list users logged into Postorius and went to profile settings. Over there, they found an option "Delete Account". Without any discussion, they deleted their account and all their list membership. How can we prevent this from happening? Is it possible to disable this "Delete Account" option, or can we add some admin approval? Regards, Hitachi. ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firefox_lMnN5UcNTB.png Replaced multipart/alternative part with first alternative.

1 year, 6 months

Re: Log Owner/Moderator actions ban address matching.

by Stephen J. Turnbull

Odhiambo Washington via Mailman-users writes: > So this issue can be addressed by making Postorius to log user logins, > right? > However, I don't have the patch :) I would guess it's probably possible to get Django to do this, quite possibly using standard configuration to do so. I just don't know where to look offhand. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

1 year, 6 months

Re: Django-allauth compatibility (ACCOUNT_AUTHENTICATION_METHOD and ACCOUNT_EMAIL_REQUIRED)

by Mark Sapiro

On 6/16/25 15:26, Eggert Ehmke via Mailman-users wrote: > I have django-allauth 65.9.0 and still the same problem. mailman-web runjobs minutely throws it each minute, which is annoying. Do you have ``` ACCOUNT_LOGIN_METHODS = {'email', 'username'} ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*'] ``` in your django settings? What releases of HyperKitty, Postorius and Django-Mailman3 are you running? Current releases do not have any minutely jobs. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

Re: mailman addmember/syncmember commands print undecoded UTF-8 [ADD] or [DEL] mail addresses in its messages like "[ADD] =?utf-8?q?John_=....."

by Wikinaut

I have such entries again in the postorius list "=?utf-8?q?Alexandro....", even after having deleted the user twice (there were no entries), the text file has nothing special, uchardet says "UTF8".

1 year, 3 months

Re: Website 404 error

by Mark Sapiro

On August 11, 2025 1:06:18 PM GMT, peter(a)pi4cc.nl wrote: > >There's something strange, and I can't find a source/solution. >When I first access the website domain.nl/mailman3, it's redirected to domain.nl/mailman/postorius/lists/, resulting in a 404 error (3 after mailman is missing). >When I accessed it a second time with the same link (domain.nl/mailman3), I was redirected to domain.nl/mailman3/postorius/lists and the welcome page appeared. See the post at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> or perhaps the entire thread. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

1 year, 2 months

Re: Internal Server Error: /mailman3/postorius/lists/.../held_messages - humanize: where to put?

by leonard＠penzer.de

Also using debian and had the same issue after upgrade to trixie. I had to add 'django.contrib.humanize' to /etc/mailman3/mailman-web.py /usr/share/mailman3-web/settings.py seems to be only a fallback, settings are overwritten in /etc/mailman3/mailman-web.py, so adding it here (it is already there), may does not have any effect.

1 year, 1 month

Re: Internal Server Error: /mailman3/postorius/lists/.../held_messages - humanize: where to put?

by Flo

On 9/12/25 12:46, leonard--- via Mailman-users wrote: > Also using debian and had the same issue after upgrade to trixie. > > I had to add 'django.contrib.humanize' to /etc/mailman3/mailman-web.py > /usr/share/mailman3-web/settings.py seems to be only a fallback, settings are overwritten in /etc/mailman3/mailman-web.py, so adding it here (it is already there), may does not have any effect. > This made my setup work as well. Thank you so much for posting the solution! This saved lots of hours for me. Flo

1 year, 1 month

Re: Can't subscribe on new site/domain

by Mark Sapiro

On 10/10/25 10:29 AM, Flo via Mailman-users wrote: > > Postorius Version 1.3.13, > /usr/share/mailman3-web/settings.py: FILTER_VHOST = True , however, this > is set for the whole server and not for single domains/sites, right? Right. > In my case mail_host is the same as web_host so I shouldn't be touched > by that problem anyway. What do you get from the following database query SELECT * from django_mailman3_maildomain JOIN django_site ON site_id = django_site.id; -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

custom css?

by jamie＠mayfirst.org

I've installed the mailman3, mailman3-full, mailman3-web, and python3-django-mailman3 packages on Debian trixie. Everything is working - thank you developers! However, I would like to modify how the web pages look (both postorius and hyperkitty). I noticed that the web interface on this server (lists.mailman3.org) looks much nicer than the one showing on my server. For one, on my installed instance, the left and right margins are not set, so content is flush with the edge of the screen. What is the easiest/most maintainable way to add my own css code and/or files to adjust how the web interface is displayed? Is that possible? Thank you! jamie

11 months, 4 weeks

Re: Internal Server Error: /mailman3/accounts/fedora/login/

by Bernie Hoeneisen

Look like a crawler-bot (e.g. for Search-Engines) is triggering this. HTTP_USER_AGENT = 'Mozilla/5.0 (compatible; SemrushBot/7~bl; +http://www.semrush.com/bot.html)' Not sure though, how they harvested the URL that is triggering the error. Maybe that URL is exposed somewhere, e.g. in Postorius or Hyperkitty. Easy mitigation is to add a robots.txt with the following content to your site: ``` User-agent: * Disallow: / ``` i.e. 'https://<your_site_url>/robots.txt' should return the above (or sth. alike). I added an Alias pointing to a 'robots.txt' file to the apache2 config, e.g.: ``` Alias /robots.txt /var/www/robots/robots.txt ```

11 months, 2 weeks

Mailman-users search results for query "Postorius"