Search results for "Postorius" - Mailman-users

Mailman3-web/Postorius behind Lighttpd

by Élodie BOSSIER

Hi, I'm using Mailman 3.3.3 (Tom Sawyer) on Debian Bullseye 11.2 from packages : #dpkg -l | grep mailman ii mailman3 3.3.3-1 all Mailing list management system ii mailman3-full 3.3.3-1 all Full Mailman3 mailing list management suite (metapackage) ii mailman3-web 0+20200530-2 all Django project integrating Mailman3 Postorius and HyperKitty ii python3-django-mailman3 1.3.5-2 all Django library to help interaction with Mailman3 (Python 3 version) ii python3-mailman-hyperkitty 1.1.0-10 all Mailman3 plugin to archive emails with HyperKitty ii python3-mailmanclient 3.3.2-1 all Python bindings for Mailman3 REST API (Python 3 version) I can access from localhost to http://127.0.0.1:8000/ which move me correctly to http://127.0.0.1:8000/postorius/lists/ and all seem to be correct. But 127.0.0.1:8000 listen only in localhost : #netstat -tanpu | grep 8000 tcp 0 0 127.0.0.1:8000 0.0.0.0:* LISTEN 626175/python3 So I try to use my lighttpd as proxy as recommanded with this config : > scgi.protocol = "uwsgi" > scgi.server = ( > "/" => (( "host" => "127.0.0.1", "port" => 8000, "check-local" => > "disable" )), > ) but it's return me a "502 Bad Gateway". I see nothing on there logs : - /var/log/lighttpd/error.log - /var/log/mailman3/web/error.log - /var/log/mailman3/web/access.log But on the file : /var/log/mailman3/web/mailman-web.log I can see that : > QUERY_STRING > REQUEST_URI/postorius/lists/REDIRECT_STATUS200 > SCRIPT_NAME" 400 - I don't know what I'm doing wrong ... There is a way to solve it with lighttpd or bind the port 8000 to 0.0.0.0 instead 127.0.0.1 (which is not recommanded) ? Thank you in advance. Best regards, Elodie

3 years, 5 months

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

3 years, 5 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

3 years, 11 months

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

4 years, 6 months

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

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.

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

4 years, 11 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 month, 1 week

Re: Time Zone Issue in Postorius

by Mark Sapiro

On 2/7/22 21:18, David Newman wrote: > On 2/4/22 10:29 AM, Mark Sapiro wrote: >> >> The appropriate setting for Django is always `TIME_ZONE = >> 'UTC'`because the time passed from Mailman core is a naive >> datetime.datetime object and is actually UTC. > > Could use clarification on this. Are you referring to the settings.py > file, or something else? Settings.py > Asking because my settings.py currently has: > > # Django time zones > USE_TZ = True > TIME_ZONE = 'America/Los_Angeles' It should be TIME_ZONE = 'UTC' Times passed from Mailman core are naive times, I.e. they don't have time zone info, but they are in UTC. Thus for Django to get the correct time with time zone you need USE_TZ = True (without that, Django will throw an exception about naive times) and the TIME_ZONE to apply is UTC. With those settings, Django has the correct time zone aware times. > and list timestamps appear to work OK both in Hyperkitty and as received > by members' mail clients. Mail sent to list members is not at all affected by this. That involves Mailman core only. Also, time stamps on posts in HyperKitty come from Date: headers or Django internal times. Where you see this manifested is for example when looking at a held message in Postorius and seeing the hold time. which is a time stamp generated by Mailman core. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

Re: Where is postorius.wsgi?

by Simon Hanna

On 01/26/2018 11:18 AM, Peter Münster wrote: > On Fri, Jan 26 2018, Peter Münster wrote: > >> ImportError: No module named settings > Ok, I've found the solution: > > In wsgi.py: > > import sys > sys.path.append('/srv/www/htdocs/ckc3r/postorius/example_project') > > > But now, I get another error: > > File "/usr/lib/python2.7/site-packages/postorius-1.1.2-py2.7.egg/postorius/views/rest.py", line 33, in <module> > from django_mailman3.lib.scrub import Scrubber > File "/usr/lib/python2.7/site-packages/django_mailman3-1.2.0a1-py2.7.egg/django_mailman3/lib/scrub.py", line 26, in <module> > from email.message import EmailMessage > ImportError: cannot import name EmailMessage > > What should I do please? You appear to be using a prerelease version of django-mailman3 which is not compatible with the other parts. Install an earlier version and it should work. You also appeared to have used Python3 for the frontend in earlier posts. Currently Python3 is not yet supported. The next stable releases will most likely support Python3 and drop support for Python2

7 years, 6 months

Mailman-users search results for query "Postorius"