Search results for "Postorius" - Mailman-users

Re: broken route to accounts

by Thomas Krichel

I guess our email crossed each other. The joy of working in close time zones. Stephen J. Turnbull writes > What will match with that prefix is determined by the content of the > URLconf (../site-packages/mailman_web/urls.py). But you probably > haven't touched that file (I didn't realize that was a Python module > rather than the reference to a filesystem path). Probably that file > contains: > > urlpatterns = [ > path( > '', > RedirectView.as_view(url=reverse_lazy('list_index'), permanent=True), > ), > path('mailman3/', include('postorius.urls')), > path('archives/', include('hyperkitty.urls')), > path('', include('django_mailman3.urls')), > path('accounts/', include('allauth.urls')), > path('admin/', admin.site.urls), > # Include alternate Postorius and HyperKitty URLs. > path('postorius/', include('postorius.urls')), > path('hyperkitty/', include('hyperkitty.urls')), > ] Yes, I installed this as /etc/mailman3/urls.py, and the salient parts are mailman@darni:~$ cat /etc/mailman3/urls.py | grep path\(\' path('postorius/', include('postorius.urls')), path('hyperkitty/', include('hyperkitty.urls')), path('mailman3/', include('postorius.urls')), path('archives/', include('hyperkitty.urls')), path('', include('django_mailman3.urls')), path('accounts/', include('allauth.urls')), path('accounts', include('allauth.urls')), path('admin/', admin.site.urls), So my fix is appending a second 'accounts' router *after* the one with the slash. Inserting it before does not fix. The only thing I could imagine that leads to my mess is that I have a RewriteRule "^/?$" "https://lists.repec.info/mailman3/lists/" [R] Otherwise it shows me the "Debian Apache works" page. Further tests I have conducted now suggests that if I rewrite that rule as RewriteRule "^/?$" "https://lists.repec.info/mailman3/lists/" [END] this supposedly stops further processing of the request URL at that top point. Then the initial configuration works, and to answer your question, > What does "GET http://127.0.0.1:4386/accounts/confirm-email/" respond > with? (Don't omit the trailing "/".) root@darni ~ # GET http://127.0.0.1:4386/accounts/confirm-email/ | grep Verif Verify Your Email Address Verify Your Email Address It works. To make progress from this mess, I suggest to insert a suggestion to redirect the top level page into the documented apache configuration, something like RewriteRule "^/?$" "https://lists.example.com/mailman3/lists/" [END] So that apache non-wizards (like most of us) can use the provided sample more readly. Thank you so much. I am now turning to my other mailman installation, the one had the Debian version installed before. More fun! -- Written by Thomas Krichel http://openlib.org/home/krichel on his 22211th day.

2 months, 4 weeks

Re: Template Ignored?

by Mark Sapiro

On 2/17/22 10:10, Stephen Daniel wrote: > Fixed the POSTORIUS_TEMPLATE_BASE_URL. Doesn't fix the issue. > I've been playing with wget, and no matter what I put, I keep getting a 404 > error. > > So: this works: > > wget -O wget.out --user restadmin --password restpass ' > http://localhost:8001/3.1/lists/list.example.com' > > but this does not (404 error): > > wget -O wget.out --user restadmin --password restpass ' > http://localhost:8001/3.1/templates/list/list.example.com/list:user:notice:… You are using Mailman core's REST API which is wrong. You need to get the template from Postorius. Maybe something like http://localhost/postorius/api/templates/list/list.example.com/list:user:no… Where http://localhost/postorius/ is the URL you use to access Postorius, maybe mailman3 instead of postorius. Once you figure that out, POSTORIUS_TEMPLATE_BASE_URL is just the scheme and domain part of that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

Can login at /admin, but cannot login at the account/login page.

by Stephen J. Turnbull

I'm sorry, I'm in a "second vaccination" fog at the moment (mending but concentration lasts only about 10 minutes), so I'll answer what I know offhand since Abhilash is busy and Mark is probably offline for vacation by now. Perhaps later somebody can give a fuller answer. pabsta(a)gmail.com writes: > In comparison to the walkthrough, I did two changes; First, I used > different port numbers , as it would otherwise conflict with other > services on the server. Thank you for the very precise description. It's very helpful. > Second, I disabled the social accounts authentification mechanisms. This should not be a problem since you disabled only the providers (I think the socialauth base module is required even if you don't use it.) > I am still running on sqllite, as I am still testing things (one > task at a time). This should be no problem. > Using my "superuser" credentials, I can log to the admin section in > a fraction of a second. If you mean the django admin page https://localhost:800something/admin, that doesn't involve any part of Mailman at all. > However, if logout and attempt to login from the postorius website, > I get a « 502 bad gateway » error after roughly 30 seconds. The > logs in Systemctl for gunicorn register a "DIGEST-MD5 common mech > free" error message I would guess this is also just a connection drop because it doesn't receive the expected response within timeout. > and the nginx error logs just show a connection drop: > > 2021/08/12 18:11:09 [error] 26026#26026: *31 upstream prematurely closed connbection while reading response header from upstream, client: [ip redacted], server: > [domain redacted], request: "POST /accounts/login/ HTTP/2.0", upstream: "http://127.0.0.1:8006/accounts/login/", host: "[domain redacted]", referrer: "https://[domain redacted]/accounts/login/?next=/mailman3/lists/" a > > 1- If I attempt to login with improper credentials, the services > respond normally, and I get the expected red box with "invalid > credentials" message on the postorius page. It is only when proper > credentials are given that the connection fails. The only thing I can think of is that having sucessfully logged in, Postorius can't find Mailman core to populate your user page. That would explain why an invalid login (which is entirely within Postorius and Django) proceeds as expected, but a valid login would fail so spectacularly. > # Mailman API credentials > MAILMAN_REST_API_URL = 'http://localhost:8005' Is Mailman core listening on localhost:8005? Is there possibly a conflict with something else on that port? Steve

4 years, 10 months

Introducing my GSoC 2026 project: Domain Administration in Postorius

by Khushal A

Hi everyone, I'm Khushal, a final year Computer Science student from R V College of Engineering, India. I've been selected for Google Summer of Code 2026 with GNU Mailman project. I'll be working on Domain Administration in Postorius. Right now, Mailman has roles like site admins and list owners, but domain level management is still limited. The idea of this project is to make the domain owner role actually usable. A domain owner should be able to create lists in their domain, manage those lists with the same permissions as a list owner, and edit domain level settings for their domain. For example, if multiple domains are hosted on the same Mailman instance, each domain can be managed independently by its own owner without needing full admin access. Would love to hear how you currently manage domains and if there are any pain points. I’ll be sharing updates here: https://hashnode.com/@a-khushal Thanks, Khushal (a-khushal)

1 month, 3 weeks

Re: Language Support In Templates

by Mark Sapiro

On 1/25/21 12:18 PM, Brian Carpenter wrote: > Hello MM3 Users, > > I have a question regarding the use of templates in different languages. > I created a template for the unsubscribe notification in Postorius in > Greek. The template shows up fine in Greek via Postorius. However the > email that is sent out has a bunch of question marks where the Greek > should be: This is a bug in Postorius. I just reported it at <https://gitlab.com/mailman/postorius/-/issues/465>. There are a couple of workarounds. Assuming the list's preferred language is Greek (el), You can put the template in Mailman's var/templates/lists/<list-id>/el/ directory (creating it if necessary and ensuring it's readable by the Mailman user. You can set ``` [language.master] charset: utf-8 ``` in mailman.cfg to change the default character set from ascii to utf-8 -- 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: Messages not going to held queue

by Mail Person

I have it set so that members automatically go to the moderation queue from the Postorius settings. To make sure that wasn't the issue, I also added a test subscriber account to the list and set them manually to have their messages held for moderation. I then set them to "accept immediately" to make sure Postorius settings were taking effect. When "accept immediately" was set, the messages were sent through. When they were set to be held for moderation, the user did not get a moderation email, myself as the moderator did not get a notification, and Postorius did not show them in the held messages queue. As far as logs, in var/log/mailman3 I do not see any logs other than mailman.log, plugins.log and smtp.log. In the SMTP log I can see that the message is getting to mailman: Sep 07 20:10:08 2022 (2837) ('127.0.0.1', 45958) Data: b'MAIL FROM:<test email>' Sep 07 20:10:08 2022 (2837) ('127.0.0.1', 45958) sender: test email Sep 07 20:10:08 2022 (2837) ('127.0.0.1', 45958) Data: b'RCPT TO:<test@domain>' however no action is taken after that. In the cases where the message is sent I there are two actions showing the message going out: Sep 07 20:10:09 2022 (2839) <stuff(a)mail.gmail.com> smtp to test@domain for 2 recips, completed in 0.14289569854736328 seconds Sep 07 20:10:09 2022 (2839) <stuff(a)mail.gmail.com> post to test@domain from testemail, 2969 bytes This leads me to believe the message is being discarded or for some reason not getting to the moderation queue.

3 years, 9 months

New subscribed (by invitation) user: no password received in invitation/welcome e-mail. Postorius sign up / password reset broken

by ^m'e

Hi there, I migrated form MM2.1 to MM3.3.10 on Debian Trixie (mariadb backend) -- I know that's a bit unorthodox to ask here for help on a non venv-based installation, but hopefully I'll first gain a bit of insight of MM3 in order to formulate a more precise request to Debian maintainers. ## Issue #1. A newly invited (from Postorius mass subscription page) and confirmed user doesn't get any password in their invitation/welcome e-mail. I guess that's because MM3 allows a user to subscribe without having an account, right? Else, there's a problem. ## Issue #2 Anyway, if that new user asks for a password reset on Postorius they get "Server error An error occurred while processing your request." Log shows: ``` ERROR 2025-08-29 17:59:17,227 173488 django.request Internal Server Error: /accounts/password/reset/ Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 55, in inner response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 197, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 105, in view return self.dispatch(request, *args, **kwargs) ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/utils/decorators.py", line 46, in _wrapper return bound_method(*args, **kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 144, in dispatch return handler( form.save(self.request) ~~~~~~~~~^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/allauth/account/forms.py", line 633, in save adapter.send_password_reset_mail(user, email, context) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/allauth/account/adapter.py", line 577, in send_password_reset_mail return self.send_mail("account/email/password_reset_key", email, context) ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/allauth/account/adapter.py", line 201, in send_mail msg.send() ~~~~~~~~^^ File "/usr/lib/python3/dist-packages/django/core/mail/message.py", line 299, in send return self.get_connection(fail_silently).send_messages([self]) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^ File "/usr/lib/python3/dist-packages/django/core/mail/backends/smtp.py", line 134, in send_messages sent = self._send(message) File "/usr/lib/python3/dist-packages/django/core/mail/backends/smtp.py", line 152, in _send self.connection.sendmail( ~~~~~~~~~~~~~~~~~~~~~~~~^ from_email, recipients, message.as_bytes(linesep="\r\n") ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "/usr/lib/python3.13/smtplib.py", line 861, in sendmail self.ehlo_or_helo_if_needed() ~~~~~~~~~~~~~~~~~~~~~~~~~~~^^ File "/usr/lib/python3.13/smtplib.py", line 611, in ehlo_or_helo_if_needed if not (200 <= self.ehlo()[0] <= 299): ~~~~~~~~~^^ File "/usr/lib/python3.13/smtplib.py", line 451, in ehlo self.putcmd(self.ehlo_msg, name or self.local_hostname) ~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.13/smtplib.py", line 378, in putcmd self.send(f'{s}{CRLF}') ~~~~~~~~~^^^^^^^^^^^^^^ File "/usr/lib/python3.13/smtplib.py", line 365, in send raise SMTPServerDisconnected('please run connect() first') smtplib.SMTPServerDisconnected: please run connect() first ``` The same happens if the new users tries to sign up. Any idea? Cheers -- Marco

9 months, 3 weeks

Re: How to change the language in mailman3

by Mark Sapiro

On 7/22/20 10:17 AM, blackout69 wrote: > Hi everybody, > > with > $sudo updatedb > $sudo locate,I don't find these path Mailman core in mailman/messages/ > Hyperkitty in hyperkitty/local/ > django-mailman3 in django-mailman3/local/ > postorius in postorius/local/from here > https://www.pratico.work/file.tar.xz you can download the following > files: my file /usr/share/mailman3-web/settings_local.py $sudo locate > it/LC_MESSAGES > mypath.txt I can't (re)generate the .mo files because > there are no path above. Thank You for help Max I'm having trouble deciphering what you are saying, however, the actual paths you are looking for are: For Mailman core: mailman/messages/it/LC_MESSAGES/mailman.po For HyperKitty: hyperkitty/locale/it/LC_MESSAGES/django.po For djangomailman3: django_mailman3/locale/it/LC_MESSAGES/django.po For Postorius: postorius/locale/it/LC_MESSAGES/django.po Note 'locale', not 'local' -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

The email confirming the registration of an account on postorius is not correctly translated in Italian

by Massimo Zappalà

Hi everyone, thanks to the files.po on Weblate, I have translated all Mailman-Core, Postorius, Hyperkitty and Django_mailman3. I have also translated the confirmation message to subscribe to a list. Everything works, except for this: When I register a new account on postorius, he sends me a confirmation email totally in English, except the following final block which is sent in Italian: in my /usr/lib/python3/dist-packages/allauth/locale/it/LC_MESSAGES/django.po #: templates/account/email/email_confirmation_message.txt:7 #, python-format msgid "" "Thank you from %(site_name)s!\n" "%(site_domain)s" msgstr "" "Grazie da %(site_name)s!\n" "%(site_domain)s" By carefully analyzing the same file .po, I notice that the Italian translation of the whole text already exists. Why does the confirmation email arrive in English? #: templates/account/email/email_confirmation_message.txt:1 #, fuzzy, python-format #| msgid "" #| "User %(user_display)s at %(site_name)s has given this as an email " #| "address.\n" #| "\n" #| "To confirm this is correct, go to %(activate_url)s\n" msgid "" "Hello from %(site_name)s!\n" "\n" "You're receiving this e-mail because user %(user_display)s has given yours " "as an e-mail address to connect their account.\n" "\n" "To confirm this is correct, go to %(activate_url)s\n" msgstr "" "Ciao da %(site_name)s!\n" "\n" "L'Utente %(user_display)s di %(site_name)s ha registrato questo indirizzo e-" "mail.\n" "Per confermare, clicca qui %(activate_url)s\n" Thanks Max

5 years, 10 months

footer template priority

by Sam Darwin

It seems templates can be configured in the filesystem or via postorius. When I place a footer template in the filesystem it worked fine. Then without adjusting any configuration, without removing that, I tried to use the postorius control panel to add a footer template, which ends up in the database, both the core and web databases. But emails stop getting sent out. Emails were posted into Hyperkitty, but not mailed out via postfix. Whatever system logs I have access to, I have checked. There are no apparent errors anyplace. Perhaps I didn't look in the right places. The problematic email arrives, is posted to Hyperkitty, but isn't emailed out to subscribers. As if the template broke something. I remove the template from the postorius UI. Those queued emails are instantly sent! The template said "test content". No variables. I checked on the server for "queued emails" and did not find those either, in postfix or mailman. Mysterious. The phenomenon is repeatable on this server. Add a footer template, emails stop.

1 year

Mailman-users search results for query "Postorius"