Search results for "Postorius" - Mailman-users

Re: Can't Start Mailman3 Core on Fresh Install

by Jonathan Green

I've triple checked the password in mailman.cfg and used the same username/password directly in MySQL and was able to get to the mailman3 database. I did run a test script in python3 using the PyMySQL connector and got the same error. Is there some permissions issue I need to look for? I ran the install as user root - perhaps the user running the python script doesn't have access somehow? On Thu, Jul 21, 2022 at 7:48 AM Stephen J. Turnbull < stephenjturnbull(a)gmail.com> wrote: > Mail Person writes: > > > Hi Everyone. I'm installing Mailman3 on a Ubunu 18.03 server using > > MySQL as the backend. After installing using the mailman3-full > > package and configuring it, I'm getting the following error when > > trying to start the mailman3 service: > > > Jul 21 04:28:44 eps mailman3[81963]: > > sqlalchemy.exc.OperationalError: (pymysql.err.OperationalError) > > (1045, "Access denied for user 'mailman3'@'127.0.0.1' (using > > password: YES)") > > I would guess that the password doesn't match. This can happen > because some configuration is done with Python modules (.py files, the > configuration is Python code) where strings are *delimited* by quote > marks (which are not part of the value) and some (.cfg files) are > .ini-style, where all values are read as strings, and so quote marks > become part of the value. > > The web database (mostly user information) and the mailing list > database are separate (because not all Mailman installations use > Postorius and HyperKitty). Are you sure you have the right user and > password for the mailing list database configured in mailman.cfg? > > Other reasons would be in this reference: > > > Jul 21 04:28:44 eps mailman3[81963]: (Background on this error at: > > http://sqlalche.me/e/e3q8) > > > I'm not sure why the access issue is happening. Mailman3-web is > > running fine and I can see the site at mailman3/postorius/lists > > (but it says Page Not Found). > > "Page not found" is probably a consequence of the same access error. > You can probably see it in the database logs. > >

3 years, 9 months

Re: How to change the language in mailman3

by Massimo Zappalà

Hi everyone, Debian buster run on my server. I installed the apt install mailman3-full package and configured it. Everything works fine. I'm trying to change the language (mailman3, postorius and hyperkitty) from English to Italian, but it's not clear what I'm missing. These are the files that I modified to try to set the Italian language: /etc/mailman3/mailman.cfg default_language: it --------------------------------------------------------------- /etc/mailman3/mailman-web.py LANGUAGE_CODE = 'it-IT' TIME_ZONE = 'Europe/Rome' USE_I18N = True USE_L10N = True USE_TZ = True --------------------------------------------------------------- /usr/lib/python3/dist-packages/django/conf/global_settings.py TIME_ZONE = 'Europe/Rome' USE_TZ = True LANGUAGE_CODE = 'it-IT' --------------------------------------------------------------- With this command, I set the Italian language to the list. It takes the setting, but it doesn't work sudo mailman shell -l test(a)pratico.work >>>m.preferred_language='it' >>>commit() >>>CTRL-D Can anyone tell me what I'm missing? Thank you in advance Max

5 years, 9 months

Re: django fake users

by Andrew Hodgson

Brian Carpenter wrote: >On 1/17/21 6:24 AM, Andrew Hodgson wrote: >> I don't think this would help the issue. What I am seeing here is users signing up through Postorius using the sign up option which then creates an account in Django (but not Mailman). Yesterday alone I had over 700 of these accounts created. I don't know whether they pass email confirmation or not (I don't see this in Django admin), however they don't get added as users in Mailman and they don't attempt to subscribe to any list. >You can select "Email Addresses" in Django. On the "Email Addresses" >page, select No under the By verified heading in the FILTER box. There you should see a list of unverified email/users. Thanks for that, was looking in the wrong place. The fake accounts currently in my system aren't actually being verified as I kind of expected. Andrew.

5 years, 3 months

Re: Reject with notification not working

by MegaBrutal

Mark Sapiro <mark(a)msapiro.net> ezt írta (időpont: 2026. márc. 25., Sze, 1:16): > On 3/25/26 4:00 AM, MegaBrutal via Mailman-users wrote: > > Mark Sapiro <mark(a)msapiro.net> ezt írta (időpont: 2026. márc. 24., K, > 8:26): > > > >> What is the moderation action for the address you posted from? > >> > > > > I posted if from a member address, and members are set to "Reject (with > > notification)". The message didn't get to the list (as expected), but no > > notification was sent either – basically the action was like if I set > > "Discard (no notification)". > > As the list owner go to Users->Members in Postorius and click the > address you posted from. Scroll to the bottom of the page. What is the > setting for Moderation? > List Default. Do you see why it would not work?

1 month, 1 week

Re: Postorius no connection to REST API

by Mark Sapiro

On 8/8/21 6:44 AM, rrosner5(a)gmail.com wrote: > > I just installed Mailman3-full from debian stable repository (Mailman 3.2.1 to be precise). Mailman itself is working, also are all mailing lists imported from Mailman 2.1. But I just can not get the web interface of Postorius to work. Please see <https://wiki.list.org/x/12812344>. > I did manage to get it running through apache2 after I figured out what I had to remove from the old site config and replace it with the stuff in the automatically created config. Upon loading the site, I was able to log in and verify the mail address, but it kept showing that it wasn't able to connect to the REST API. > > I double and triple checked, that mailman-web.py and mailman-hyperkitty.cfg contain the same API key (api_key in hyperkitty and SECRET_KEY and MAILMAN_ARCHIVER_KEY in mailman web), but that didn't help. Because those aren't the settings that matter for this. What if anything are your settings in the mailman.cfg [webservice] section for hostname: port: admin_user: admin_pass: use_https: (defaults in our distribution are localhost, 8001, restadmin, restpass and no respectively - I don't know if Debian changes these). These need to match the Django settings MAILMAN_REST_API_URL = 'http://localhost:8001' MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = 'restpass' I also saw a recommendation, that it can cause problems, when the API key uses symbols like / so I switched it to _ in all three places, but that didn't help. The configuration for mailman, mailman-web and hyperkitty all are set to using https, switching them to http doesn't solve any of the problems. > Meanwhile, the site only shows "Internal Server Error" even though I did not change anything. But probably not that relevant while it can't be used either way. What I can provide on logs: > > /usr/share/mailman3-web/manage.py mmclient > Python 3.7.3 (default, Jan 22 2021, 20:04:44) > [GCC 8.3.0] on linux > Type "help", "copyright", "credits" or "license" for more information. > (InteractiveConsole) >>>> client.system > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 95, in call > response, content = Http().request(url, method, data_str, headers) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1513, in request > (response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1263, in _request > (response, content) = self._conn_request(conn, request_uri, method, body, headers) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1186, in _conn_request > conn.connect() > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1049, in connect > raise socket_err > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1010, in connect > sock.connect((self.host, self.port)) > ConnectionRefusedError: [Errno 111] Connection refused The REST API is apparently not listening on the host/port this is trying to connest to. > An excerpt from /var/log/mailman3/web/mailman-web.log: > Traceback (most recent call last): > File "manage.py", line 10, in <module> > execute_from_command_line(sys.argv) > File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 364, in execute_from_\ > command_line > utility.execute() > File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 308, in execute > settings.INSTALLED_APPS > File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 56, in __getattr__ > self._setup(name) > File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 41, in _setup > self._wrapped = Settings(settings_module) > File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 110, in __init__ > mod = importlib.import_module(self.SETTINGS_MODULE) > File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module > return _bootstrap._gcd_import(name[level:], package, level) > File "<frozen importlib._bootstrap>", line 1006, in _gcd_import > File "<frozen importlib._bootstrap>", line 983, in _find_and_load > File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked > File "<frozen importlib._bootstrap>", line 677, in _load_unlocked > File "<frozen importlib._bootstrap_external>", line 728, in exec_module > File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed > File "/usr/share/mailman3-web/settings.py", line 486, in <module> > from settings_local import * > File "<frozen importlib._bootstrap>", line 983, in _find_and_load > File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked > File "<frozen importlib._bootstrap>", line 677, in _load_unlocked > File "<frozen importlib._bootstrap_external>", line 724, in exec_module > File "<frozen importlib._bootstrap_external>", line 859, in get_code > File "<frozen importlib._bootstrap_external>", line 916, in get_data > PermissionError: [Errno 13] Permission denied: '/usr/share/mailman3-web/settings_local.py' > [uwsgi-daemons] throttling "python3 manage.py qcluster" for 25 seconds > > not sure where the Permission denied comes from/what permissions should be. /usr/share/mailman3-web/settings_local.py is a symlink owned by root to /etc/mailman3/mailman-web.py owned by list:list with 640 permission. What is executing the manage.py command to start Django. Is it user list? > The apache2 error log contains nothing from the last restart of mailman3 and mailman3-web and trying to load the web page, the only interesting lines to the end of the log are > [Sun Aug 08 14:40:33.642119 2021] [proxy:error] [pid 2248:tid 140583379425024] (111)Connection refused: AH02454: uwsgi: attempt to connect to Unix domain socket /run/mailman3-web/uwsgi.sock (localhost) failed > [Sun Aug 08 14:40:33.644627 2021] [:error] [pid 2248:tid 140583379425024] [client 134.61.97.39:11893] AH10101: failed to make connection to backend: httpd-UDS:0 > [Sun Aug 08 14:54:22.555229 2021] [proxy:error] [pid 2248:tid 140583379425024] (111)Connection refused: AH02454: uwsgi: attempt to connect to Unix domain socket /run/mailman3-web/uwsgi.sock (localhost) failed > [Sun Aug 08 14:54:22.555293 2021] [:error] [pid 2248:tid 140583379425024] [client 134.61.97.39:11913] AH10101: failed to make connection to backend: httpd-UDS:0 > [Sun Aug 08 14:58:24.376278 2021] [mpm_event:notice] [pid 2247:tid 140583610946688] AH00492: caught SIGWINCH, shutting down gracefully > [Sun Aug 08 14:58:34.534966 2021] [mpm_event:notice] [pid 3696:tid 140070763447424] AH00489: Apache/2.4.48 (Debian) OpenSSL/1.1.1d mod_wsgi/4.6.5 Python/3.7 configured -- resuming normal operations > [Sun Aug 08 14:58:34.535159 2021] [core:notice] [pid 3696:tid 140070763447424] AH00094: Command line: '/usr/sbin/apache2' I don't use uwsgi and know little about it so I don't know what the Unix domain socket /run/mailman3-web/uwsgi.sock connection is for, but this appears to be some miscunfiguration between apache and uwsgi. Normally, in an apache/uwsgi configuration, apache proxies to uwsgi via tcp port 8000 and uwsgi is configured with [uwsgi] uwsgi-socket = 0.0.0.0:8000 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

Mailman 3 installation from latest Debian packages

by Matthew Blissett

Hi, I've installed mailman3-full 3.3.3-1 from Debian bullseye (Debian testing). The dropdown controls on the UI for Postorius (e.g. "Subscription requests", "Mass operations" and the username button to log out) and the similar controls on Hyperkitty (e.g. "Threads by month") do not work. You can see the latter at http://newlistszm.gbif.org/mailman3/hyperkitty/list/test@newlistszm.gbif.or… I found https://lists.gem5.org/archives/list/gem5-announce@gem5.org/ which is running the same version, but presumably not using these Debian packages as the Javascript is slightly different. Could this be a problem with the Debian packaging, or perhaps my configuration -- which is very close to the defaults (i.e. Mailman and Apache configuration generated by dpkg). Has anyone set up a working installation using these packages? Thanks, Matt Blissett PS, I wrote a similar message earlier in the week to a Debian list: https://alioth-lists.debian.net/pipermail/pkg-mailman-hackers/2021-February…

5 years, 2 months

attachment.html

by Sam Darwin

Hi, Using a typical modern email client such as Gmail, the messages are usually html formatted. Then, Hyperkitty displays attachment.html on every message. Can that be removed? I was searching for the topic "attachment.html" in the archives and there wasn't much information. What finally cracked the code was Mark's comment: If in Postorius on the list's Settings -> Alter Messages page, Filter Content and Convert html to plaintext are both Yes, the HTML should be converted to plain text and that should appear in HyperKitty. It turns out "Filter content" affects many settings. It's easy to skip over that. I wonder if the UI might call attention somehow, with a graphic element, or with text: "Settings on this page will not take effect. Because 'Filter content' has not been enabled". It is right that "Filter content" must be set in order to remove attachment.html ? And now, a search will have more results. :-)

2 years, 10 months

Re: Handling of SPAM mails in mailman3 - Check for X-Spam Header

by Mark Sapiro

On 1/16/20 10:51 AM, Torge Riedel wrote: > > Such SPAM mails are currently hold for moderation with reason "not from > a list member". Is there no check for the "X-Spam: Yes" header or is > this check done later? If you set a Header Filter (in Postorius the Header filters tab) those checks are done before non-member moderation. This won't work for posts from members because the header checks are done between member moderation checks and non-member moderation checks, but if you create a Header Filter for header 'x-spam' and pattern 'yes' with action hold, a message from a non-member which has an X-Spam: Yes header should be held for that reason. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

[Mailman-Users] mailman 3 and freeipa

by Stephen J. Turnbull

Crossposting and redirecting replies to mailman-users(a)mailman3.org. Steven Jones writes: > I cant find anything on this so far but can Mailman3's webui use > freeipa as the authentication mechanism? Hi Steve, I don't have a complete answer offhand (and right now I'm just reducing my inbox so a single google search is as much as I can do), but searching for "freeipa django" indicates that there are "connectors" for Django and FreeIPA. The nicest option would be a plugin for Django's socialauth application. If that doesn't seem to exist, perhaps you can just add a FreeIPA application to the Django configuration. You would need to add it to both Postorius and HyperKitty configurations. Steve -- Associate Professor Division of Policy and Planning Science http://turnbull.sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull(a)sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN

7 years, 1 month

Re: Deleting messages from HyperKitty archive

by Mark

On 2024-03-26 08:45, Mark Sapiro wrote: > On 3/25/24 13:00, Mark wrote: >> >> Regarding updating, the Hyperkitty docs say to (a) update the code >> base; and (b) update the database schemas. >> >> Although updating the database is mentioned, there isn't anything >> about updating the code base. > > Updating the code base just means installing an updated version. E.g. > upgrading from 1.3.8 to 1.3.9. > Thanks Mark. Was another case of "If all else fails, read the instructions..." $ sudo systemctl stop mailman3 $ sudo systemctl stop mailmanweb (venv) $ pip install -U mailman postorius django-mailman3 hyperkitty mailman-web (venv) $ mailman-web migrate (venv) $ mailman-web compress (venv) $ mailman-web collectstatic (venv) $ mailman-web compilemessages $ sudo systemctl start mailman3 $ sudo systemctl start mailmanweb https://www.mailman3.org/en/latest/upgrade-guide.html Successfully upgraded to Hyperkitty 1.3.9 and the delete message link now shows for the list owners. Best, Mark

2 years, 1 month

Mailman-users search results for query "Postorius"