Search results for "Postorius" - Mailman-users

Re: Acceptable aliases defaults to []

by Barry Warsaw

On Aug 28, 2017, at 03:42, Henrik Rasmussen <her(a)adm.ku.dk> wrote: > > * Docker-mail 0.1.1 > * Mailman 3.1 > * Postorius 1.1.1 > * Hyperkitty 1.1.1 > > Minor issues: > > Settings -> Message Acceptance -> Acceptable aliases has a default of [] resulting in "An error occured: [u'[]']" when saving. This fiend should be empty by default or at least accept the default when saving. Hi. Could you explain where this error happens? Is it in Postorius or the core/REST API? > To me the description right under the Acceptable aliases field is not user friendly. It doesn't explain the purpose of the field, but is meant for the Mailman sysadmin, not the list admin who can't be expected to understand this. A much better description would be the ones used for MM2: > > * http://www.list.org/mailman-admin/node23.html > * https://wiki.list.org/DOC/What%20does%20%22message%20has%20implicit%20desti… > > On a second note: Where I can change the field and message descriptions in MM3, like the /usr/lib/mailman/messages/[sprog]/LC_MESSAGES/mailman.po in MM2? Currently, there are no translations for MM3. Cheers, -Barry

8 years, 11 months

Re: Question after upgrade to mm 3.2.3 and latest postorius

by Abhilash Raj

On Sun, Aug 11, 2019, at 12:43 PM, David Krantz wrote: > Hi all, > > I have just upgraded to mailman 3.2.3. My installation is from the git > sources and I use two different venv:s, one for the web part as I did > not want to compile the web server plugin to a newer python version > than 3.5, and one venv for the rest running python 3.7. Apart from > some missing dependencies and some changes that affected the django > config I just have two issues with postorius: I would recommend that you bump up to 3.7 for the web part too, mostly because 3.5 is now has been in security maintenance state for a while. We will drop support for 3.5 after this next release (so you do have some time :), but I fear there *could* potentially be other dependent libraries who might have dropped 3.5 support. Even though we do run CI and we'd (hopefully) know when there is a dependent library seriously breaking, but since we don't pin down versions, newer releases can cause problems. The web-server plugin I assume is mod_wsgi? If you use a separate wsgi server than the one embedded in web-server, you can bump versions a bit more easily. gunicorn or uwsgi are recommended options. Do note that the new version of Mailman Core also uses gunicorn now. > > 1. The index page with all lists is not sorted in any useful way > although it is based on something as the order seems to be stable. > Prior to the upgrade the lists were sorted in alphabetical order after > list name which is a lot more usable for me as admin. If I click the > link at the bottom with "click to view all lists" I get the old > behaviour. This change was made so that you will see only the lists you are a member of either as a subscriber, moderator or owner. This is default when you are logged-in, but when logged-out, you will see the old view with all lists alphabetically sorted. > 2. The template menu simply does not work, it seems as if some > database table is missing even after running migrations. Are you sure the migrations are there? I can see the following list on the latest git master of Postorius (all the ones after 0004_ are related to emailtemplate): ``` $ python manage.py showmigrations <snip> postorius [X] 0001_initial [X] 0002_auto_20160210_0721 [X] 0003_drop_addressconfirmationprofile [X] 0004_create_email_template [X] 0005_auto_20180707_1107 [X] 0006_auto_20180711_1359 [X] 0007_auto_20180712_0536 [X] 0008_auto_20190310_0717 [X] 0009_auto_20190508_1604 <snip> ``` > Django logs > the following: > > ERROR 2019-08-11 20:58:55,038 exception 11837 139756347221760 Internal > Server Error: /mailman3/lists/TESTLIST/templates Traceback > (most recent call last): File > "/...VENV3.5/lib/python3.5/site-packages/django/db/backends/utils.py", > line 85, in _execute return self.cursor.execute(sql, params) > psycopg2.errors.UndefinedTable: relation "postorius_emailtemplate" > does not exist LINE 1: ...ext", "postorius_emailtemplate"."identifier" > FROM "postorius.. > > The above exception was the direct cause of the following exception: > > Traceback (most recent call last): File > "/...VENV3.5/lib/python3.5/site-packages/django/core/handlers/exception.py", > line 35, in inner response = get_response(request) File > "/...VENV3.5/lib/python3.5/site-packages/django/core/handlers/base.py", > line 158, in _get_response response = > self.process_exception_by_middleware(e, request) File > "/...VENV3.5/lib/python3.5/site-packages/django/core/handlers/base.py", > line 156, in _get_response response = response.render() File > "/...VENV3.5/lib/python3.5/site-packages/django/template/response.py", > line 106, in render self.content = self.rendered_content File > "/...VENV3.5/lib/python3.5/site-packages/django/template/response.py", > line 83, in rendered_content content = template.render(context, > self._request) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/backends/django.py", > line 61, in render return self.template.render(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", > line 175, in render return self._render(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", > line 167, in _render return self.nodelist.render(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", > line 943, in render bit = node.render_annotated(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", > line 910, in render_annotated return self.render(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/loader_tags.py", > line 155, in render return compiled_parent._render(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", > line 167, in _render return self.nodelist.render(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", > line 943, in render bit = node.render_annotated(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", > line 910, in render_annotated return self.render(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/loader_tags.py", > line 67, in render result = block.nodelist.render(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", > line 943, in render bit = node.render_annotated(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", > line 910, in render_annotated return self.render(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/defaulttags.py", > line 313, in render if match: File > "/...VENV3.5/lib/python3.5/site-packages/django/db/models/query.py", > line 276, in __bool__ self._fetch_all() File > "/...VENV3.5/lib/python3.5/site-packages/django/db/models/query.py", > line 1179, in _fetch_all self._result_cache = > list(self._iterable_class(self)) File > "/...VENV3.5/lib/python3.5/site-packages/django/db/models/query.py", > line 54, in __iter__ results = > compiler.execute_sql(chunked_fetch=self.chunked_fetch, > chunk_size=self.chunk_size) File > "/...VENV3.5/lib/python3.5/site-packages/django/db/models/sql/compiler.py", > line 1063, in execute_sql cursor.execute(sql, params) File > "/...VENV3.5/lib/python3.5/site-packages/django/db/backends/utils.py", > line 68, in execute return self._execute_with_wrappers(sql, params, > many=False, executor=self._execute) File > "/...VENV3.5/lib/python3.5/site-packages/django/db/backends/utils.py", > line 77, in _execute_with_wrappers return executor(sql, params, > many, context) File > "/...VENV3.5/lib/python3.5/site-packages/django/db/backends/utils.py", > line 85, in _execute return self.cursor.execute(sql, params) File > "/...VENV3.5/lib/python3.5/site-packages/django/db/utils.py", line > 89, in __exit__ raise dj_exc_value.with_traceback(traceback) from > exc_value File > "/...VENV3.5/lib/python3.5/site-packages/django/db/backends/utils.py", > line 85, in _execute return self.cursor.execute(sql, params) > django.db.utils.ProgrammingError: relation "postorius_emailtemplate" > does not exist LINE 1: ...ext", > "postorius_emailtemplate"."identifier" FROM "postorius... > > Cheers > // David > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years, 11 months

Re: Welcome Message

by Abhilash Raj

On Tue, Apr 16, 2019, at 6:41 PM, brian(a)emwd.com wrote: > With all of this back and forth, I got it working. Using the mass > subscribe feature or the subscribe form on the info page WHILE LOGGED > IN AS ADMIN was causing the error. That shouldn't cause the error. Irrespective of how you subscribe, when you subscribe anyone to a list, Core will try to send the welcome message and try to reach Postorius for template. If the URL for template is wrong, or Postorius is down for whatever reason, the subscription will fail with the error that you saw before. > I logged out of Postorious and subscribed using the subscribe form on > the info page and the change to the welcome template showed up. So it > looks like being logged in as admin while trying to subscribe someone > was what was causing the problem. Is that a bug I discovered? I suspect stopping-restarting and re-creating the template (idk, if you really did that) might have something to do with it. I am not sure if this is a bug unless you can reliably reproduce this. -- thanks, Abhilash Raj (maxking)

7 years, 3 months

Re: sqlite3 Database "read only" error on mailman_sync job

by Ugnius S

I have installed using documentation. My linux distribution version has no full package available. I have installed step by step: $ sudo pip3 install mailman $ sudo pip3 install postorius $ sudo pip3 install hyperkitty $ sudo pip3 install mailman-hyperkitty And of course all mandatory components... Everything without errors, I can drop db files and I can download mailman-suite again and start from empty page again. But it will not guarantee that DB will not become READ ONLY again. Here should be logic. No developing support here? 2019-09-03, an, 19:36 Abhilash Raj <maxking(a)asynchronous.in> rašė: > > > On Sun, Sep 1, 2019, at 3:22 AM, ugniusviln(a)gmail.com wrote: > > Hi. All the project installation is under the same user / path and > > it works. Archiving working as well, (just one remark: no matter what > > to set in postorius, hyperkitty shows list as public) > > I have found work around - it is possible to change list as private in > > "admin" page. > > I started to get issues with runjobs after I have created couple of > > new lists with "no archive" option. > > How did you install all these components. It seems there the installation > is broken in weird ways. > > > > > If as owner user from project home I run: > > > > django-admin mailman_sync > > > > Traceback (most recent call last): > > File > > > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/utils.py", > > line 84, in _execute > > return self.cursor.execute(sql, params) > > File > > > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/sqlite3/base.py", > > line 383, in execute > > return Database.Cursor.execute(self, query, params) > > sqlite3.OperationalError: attempt to write a readonly database > > > > "django-admin runjob sync_mailman " - makes read only errors as well. > > "django-admin runjob new_lists_from_mailman" > > django.db.utils.OperationalError: attempt to write a readonly database > > END TRACEBACK > > > > I did not find information how to fix this. It was worked without errors > > before. > > I noticed, that if I stop mailman, "django-admin mailman_sync" starts > > to work. > > If I start "mailman start", then "django-admin mailman_sync" failing > > again. > > I did not check other jobs, but I think what is related to database, > > will get errors. > > Seems mailman locking the database. It is not a file permissions issue. > > Mailman db location is: /project_directory/var/data/mailman.db > > > > if to rename /project_directory/var/data/mailman.db to something, > > mailman creates database file size 0, django-admin runjobs start > > working, but of course postorius stops working. I did it for testing. > > I have returned this database file back, postorius started to work > > again, but django-admin runjobs does not work, error: "database read > > only". > > Please help me how to fix this issue. > > _______________________________________________ > > Mailman-users mailing list -- mailman-users(a)mailman3.org > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > > -- > thanks, > Abhilash Raj (maxking) >

6 years, 11 months

Missing bits of French translation

by iMark

Hi, I have a list set with "French" as its preferred language. The default emails such as the Confimation and Welcome get sent French. My browser (Chrome) has its default language set as French, and my PC's region and language are set as French. When I view the list's "Info" Postorius page I see some parts translated ... 1. Menu and button words are translated okay. eg: ENGLISH: Sign In FRENCH: S'identifier 2. Page heading words are translated okay. eg: ENGLISH: Subscription / Unsubscription FRENCH: Abonnement / désabonnement 3. Page text fails. eg. ENGLISH: You have to sign in to visit the archives of this list. FRENCH: Is in English. Looking at the .po file ... /opt/mailman/venv/lib/python3.11/site-packages/mailman/messages/fr/LC_MESSAGES/mailman.po "PO-Revision-Date: 2024-06-25 17:09+0000\n" None of the msgid strings for the 3 examples appear in the mailman.po file. So, as some strings are translated and others not (yet none appear in the mailman.po file), I'm thinking that either there is another translation file somewhere for Postorius that needs updating, or the missing msgid s were not included in the original .pot file. Am I on the right track?

2 months, 3 weeks

Re: Error -- postorius Un-handled exception

by Stephen J. Turnbull

Mark writes: > The user mailman has its plain text password written into the > mailman.cfg file. > If that is a potential weakness, It is. I may have some answers for that one in a few months (current project has a goal of storing all secrets in a secure vault, so that would mean enabling Mailman 3 to take advantage of such a vault). > would making mailman NOT the owner reduce vulnerability by a degree > (in that objects could not be created in the public schema by using > mailman's credentials)? Yes, but I don't really see what attacks that would enable. I guess you could store credit card numbers and malware there almost indetectably, but getting them out still requires host access. > Of course I would have a whole world of other problems if those > credentials were misused, so I guess it's a bit theoretical anyhow. Yes. I can think of many ways to abuse access to the existing data much more easily than how to abuse data that doesn't exist from the point of view of any application on the host. :-)

2 years, 6 months

Re: Understanding of members, accounts

by Mark Sapiro

On 5/11/20 5:15 PM, Peter Adebahr via Mailman-users wrote: > Is the solution to "sign up", using one's very e-mail address already in > the system? Yes. The address is in the Mailman Core part of the systen, but not in the web UI part. > I would like to understand why there is a difference between being > (only) a subscribed member and a member having an account - or, what > might be the advantage of being a member without an account? Being a mailing list member is a Mailman core concept. It usually says you receive posts from the list based on your delivery status and you can post based on your moderation status. Logging in to the web UI to access HyperKitty and Postorius is a Django concept and requires a Django account. If all you want is to post by email and receive messages from the list, you don't need a Django account, but to manage your user settings via Postorius and to visit private archives, you do. -- 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

Re: After server upgrade debian 11→12 and reinstalling everything in (venv), I got this error when accessing → mailman3/lists

by Mark Sapiro

On 9/5/25 03:37, Wikinaut wrote: > It's going about the variable $mailinglist_url in footers. Mark exlained, that in mm >= 3.3.10 this placeholder can be used in footers, given, that you have set up $base_url. > > This does not work for me. I need to know, WHERE to set $base_url to make $mailinglist_url become working and replaced in footers. The base url setting for this is an attribute of the domain. Setting it in the Domains view of Postorius or via REST will not be available until the next release, I.e. Mailman core 3.3.11, Postorius 1.3.14, Mailman Client 3.3.6. In the mean time with Mailman core 3.3.10, you can set this via `mailman shell` or by directly updating the `domain` table in the database. In mailman shell >>> d = getUtility(IDomainManager).get('mydomain') >>> d.base_url = 'https://mydomain/mailman3/lists' >>> commit() -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months

Re: Multiple domain problem

by Lars Bjørndal

Hi, Marik! I realized that I had two variables in settings.py where the domains is listed, and one of them had a preceding https. I've now followed the documentation for configuring Apache here: https://docs.mailman3.org/en/latest/install/virtualenv.html#apache-configur…. I want both domains to start mailman3 when contacting example1.com/mailman3 and example2.com/mailman3. I have the sam configuration in both virtualhost section in Apache. For example1.com/mailman3, it works perfectly. For example2.com/mailman3 however, the browser (elinks), reports Host not found: example2.commailman3 e.g. without a slash after the domain name. What could cause this to happen? Thanks Lars On Fri, Feb 10, 2023 at 11:59:02AM -0800, Mark Sapiro wrote: > On 2/10/23 01:43, Lars Bjørndal wrote: > > On Thu, Feb 09, 2023 at 02:05:09PM -0800, Mark Sapiro wrote: > > > On 2/9/23 13:21, Lars Bjørndal wrote: > > > > > > > > If I connect to example2.com, the title is example2.com, without the > > > > preceding List index. And the body says Page not found. > > > > > > > > > What's in the browser's address bar for that page? > > > > It's https://example2.com/mailman3/lists/ > > And when you get the Page not found, is it a browser 404 error or a > Postorius error page? > > > > > > > What's in Postorius domains view? > > > > I realized that I have to change SIT_ID to 1 to be able to connect to http://localhost:8000/. Then, when checking Domains, I have both domains with different SIT_ID value (1 and 2). > > > Why are you going to http://localhost:8000/? You should be able to see the > domain's view at https://example1.com/mailman3/domains/ or > https://example1.com/mailman3/domains/ or by just clicking Domains in > Postorius top nav bar. > > > > Going to http://localhost:8000/admin and choosing Sites, I have both domains listed. > > > Again you should be able to go to https://example1.com/admin or > https://example2.com/admin. If these don't work, you need to add directives > in your web server to proxy them to http://localhost:8000/admin > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to lars(a)lamasti.net

3 years, 5 months

Re: Postorius no connection to REST API

by Mark Sapiro

On 8/12/21 12:01 AM, Richard Rosner wrote: > Mark Sapiro wrote: >>> But whatever is listening on port 8001 is apparently not Mailman's rest >> server. What does >> ps -fww 14080 >> or whatever PID is currently listening on port 8001 show. > > UID PID PPID C STIME TTY STAT TIME CMD > list 15972 15963 0 Aug11 ? Sl 0:13 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1 I had asked "What does ps -fwwa|grep rest show?" and it didn't find this. That was my error. I meant 'ps -fwwA|grep rest' >>> OK. >> Perhaps instead you should have >> uid: list >> gid: list >> in your uwsgi configuration if you don't already. > > Tried that while also switching mailman3-web.service to list:list, exactly the same error. Also, I have /run/mailman3-web/uwsgi.sock owned by list:list now instead of www-data:www-data. All the mailman processes should run as `list` and all mailman related things should be readable and writable by `list`. >>> I'm not familiar enough with this form of ProxyPass using sockets to >> understand what the localhost:8001 does in this context, but uwsgi >> should not be doing anything with port 8001. In a configuration using >> TCP, it would listen on port 8000. Port 8001 is where Mailman's REST API >> server listens. uwsgi should receive connects in your case via the unix >> socket and then pass them to Django via the application in wsgi.py >> Also, you may want other paths proxied to uwsgi, namely at least some of >> hyperkitty, postorius, archives, accounts, admin and user-profile. > > Ok, I removed that port again, now it's exctly like in the automatically generated config file. > And you mean like > > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > ProxyPass /hyperkitty unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > ProxyPass /postorius unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > ProxyPass /admin unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > ProxyPass /archives unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > ProxyPass /accounts unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > ProxyPass /user-profile unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > </IfModule> Yes, I meant if you want those URLs to work, you have to pass them to uwsgi. You don't need all of them. `mailman2` and `postorius` are synonyms as are `archives` and `hyperkitty` However, you could try using TCP to communicate with uwsgi rather than a Unix socket. This means replacing uwsgi-socket = /run/mailman3-web/uwsgi.sock with uwsgi-socket = 0.0.0.0:8000 in your uwsgi.ini file and using directives like ProxyPass "/postorius" "http://127.0.0.1:8000/postorius" ProxyPass "/hyperkitty" "http://127.0.0.1:8000/hyperkitty" ProxyPass "/accounts" "http://127.0.0.1:8000/accounts" ProxyPass "/django" "http://127.0.0.1:8000/django" ProxyPass "/user-profile" "http://127.0.0.1:8000/user-profile" ProxyPass "/mailman3" "http://127.0.0.1:8000/mailman3" ProxyPass "/archives" "http://127.0.0.1:8000/archives" in apache. I am not familiar enough with apache/uwsgi configuration to be of more help. Have you seen https://wiki.list.org/x/12812344 and have you asked Debian for help with their package. They are the ones who should be supporting it <https://www.debian.org/support>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

Mailman-users search results for query "Postorius"