Search results for "Postorius" - Mailman-users

SQL Schema request

by Stephen J. Turnbull

Ruth Ivimey-Cook writes: > Is there any way to get a copy of the mysql/mariadb table schema that I > can then pour the existing data into (i.e. I don't want to reinitialise > the db)? I suspect you alread know this, but the backend database schema is entirely implicit in the SQLAlchemy models. There is no function in Mailman to dump out the backend schema, although SQLAlchemy may have one. AAAAaaaannnnddd ... bingo! https://docs.sqlalchemy.org/en/14/faq/metadata_schema.html#how-can-i-get-th… Don't know if that does what you need, but it's the best I can come up with without reading tons of code. :-) There's probably a similar function that allows you to dump all the data in an SQLAlchemy-specific format that you can load back in to a different backend and SQLAlchemy will do the schema translation. Also, have you considered that Django keeps an independent set of tables for HyperKitty and/or Postorius? Same comments apply, except that Django has its own ORM. https://docs.djangoproject.com/en/3.2/ref/django-admin/#dumpdata Finally, don't the backend databases have some sort of "dump schema" command? That might be more useful. Note that I got lucky (yay, Google-fu!) with "DBM dump schema" on the first try so "dump" seems to be the right search term.

4 years, 5 months

Re: Trying to configure a list (hosted)

by paul＠arenson.org

I guess my message wasn't clear? Let me try again. I have not made any list settings or sent mails because I do not want my archive filled with a lot of test mails. I am simply trying to understand a) why there are supposed to be two ways to sign up--one where you just get the messages by email and one where you are able to interact with the archives and send from the web interface. Example, as seen here---> https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… 1) I was told that Subscription / Unsubscription lets you truly register and that just below that 2) "You can also subscribe without creating an account" lLets you just receive emails but not interact with the archives.post from the web. CONFUSION --> Aside from the confusing use of "subscribe/subscription for both, when I tried testing both options, BOTH sets of emails ended up in my members list. If there is a guide (I was told it is not ready), it would help, but anyway: 3) Can anyone help me understand the problem above? 4) Will it go away if I enter my settings? Will my users (this who truly register with a password) be able to get the archives and post from the interface? The next post is about the other issue:

6 years, 7 months

Re: Mailman3 via Docker and NGINX

by Hagen Bauer

is this the complete sitename.conf? I had a situation where I had a location / definition for caching before the mailman one. On 19.12.18 16:03, brian(a)emwd.com wrote: > I have Mailman3 installed on CentOS 7 using maxking's docker image. I believe the installation went fine and running "curl http://172.19.199.3:8000/postorius/lists/" produces the correct output. I also will be using exim and nginx with this installation. > > It seems I am stuck with the nginx setup. I created a sitename.com.conf file in the /etc/nginx/conf.d folder. I have the following inputted there: > > server { > listen 80; > server_name `sitename.com`; > > location /static/ { > alias /opt/mailman/web/static/; > } > > location / { > include uwsgi_params; > uwsgi_pass 172.19.199.3:8000; > uwsgi_read_timeout 300; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > } > > However when I go to http://sitename.com (obviously using an alias here for privacy reasons) I get the default nginx index page. Do I need to add anything to the main nginx.conf file to be able to see my mailman3 installation? > > Thank you for any assistance, > Brian Carpenter > _______________________________________________ > 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/ >

7 years, 3 months

Re: Welcome Message

by Abhilash Raj

On Tue, Apr 16, 2019, at 5:51 PM, brian(a)emwd.com wrote: > There is no using mailman start with Docker: > > # mailman start > -bash: mailman: command not found > > Same results with /usr/bin/python3 or python3. I am not very > knowledgeable of the use of Docker when it comes services such as > python3. When you are using Docker, services are running in a container. Any commands that are executed needs to run inside the container. To get a shell inside the container: $ docker exec -it mailman-core bash After that, you can run commands suggested above to make sure that you can actually get the URLs. I don't get why SSL verification fails for your application, I can see that SSL is setup correctly. Try this: Change POSTORIUS_TEMPLATE_BASE_URL to use HTTP and then remove and re-create the template in Postorius. This should delete the URL for template in Core, since just changing the config in settings.py doesn't affect Core, which already has the URL from when you created the template. We should have a way to re-sync the template' URLs in Core. I'll open an issue for it. > _______________________________________________ > 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: Django site - how to create programmatically - new install

by Clark Boylan

On Fri, Sep 30, 2022, at 10:12 AM, daniel.botting(a)codethink.co.uk wrote: > Hi all, > > I've mainly setup mailman3 to replace our mailman 2.1 install using > Ansible, a point I could do with some assistance on is setting the fqdn > used programmatically. I've been doing alot of reading before creating > this thread. > > To create a domain I currently navigate to: > https://serverfqdn.com/postorius/domains/ and click 'Add Domain'. > > I believe this is setting the name of the Django site, please accept my > apologies if I'm wrong and the SITE_ID=1 is then used, I am only > planning to use one domain only. I'm using Postgres and when I check > the contents of the Django_mailman3_maildomain table as below > afterwards: > > mailman3web=# TABLE django_mailman3_maildomain; > id | mail_domain | site_id > ----+--------------------------------------+--------- > 1 | mailman3-test2.guest.codethink.co.uk | 1 > > Many thanks You can create domains via the REST API: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… The documentation shows the use of helper functions, but you should be able to interact with the API using any HTTP client. We're doing this with Ansible and it looks like: https://paste.opendev.org/show/byAG1wqXVHgKVsJ28Eb9/ > > Daniel

3 years, 6 months

Re: Mailman 3 Installation Assistance

by brian＠emwd.com

Hi Simon, Thank you for your reply. I did not realize that docker created everything for you so I prefer that. So let me get back to my original problems. I ran into the following after doing the normal docker installation: 1. curl http://172.19.199.3:8000/postorius/lists/ curl: (7) Failed connect to 172.19.199.3:8000; Connection refused 2. I was told to run docker ps. Here is the output from that: ONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 073ecf209106 maxking/mailman-web:0.1 "docker-entrypoint..." 3 days ago Up 3 days 8000/tcp, 8080/tcp mailman-web aef8f44a7136 maxking/mailman-core:0.1 "docker-entrypoint..." 3 days ago Up 3 days 8001/tcp, 8024/tcp mailman-core 398e3fc05e2c postgres:9.6-alpine "docker-entrypoint..." 3 days ago Restarting (1) 36 hours ago dockermailman_database_1 3. I was asked to look at the logs which I don't have any: cd /opt/mailman/web/logs -bash: cd: /opt/mailman/web/logs: No such file or directory 4. I was asked to do docker logs mailman-web. It is filled with the following entries: psql: could not translate host name "database" to address: Try again Postgres is unavailable - sleeping It is after the above when I got confused. So now I understand that the Docker installation creates the database and runs it. That is important to know. So if you can help me get through the above 4 issues, it would be very appreciated. Thanks! Brian

8 years

API web hook for subscribe and remove user

by Stephen J. Turnbull

Tibor Molnar writes: > I'm also aware that mailman3 is already query API on localhost and > that's how it's generating the output for system information but if > I was going to configure it for remote where else other than > mailman.cfg do I need to configure this? You don't want to mess with mailman.cfg. Instead you should reverse proxy it, the same way that you do for Postorius. Note that you don't have to open up the whole REST API, you can restrict to very specific endpoints. For example for nginx, the basic scheme is location /REST-API/domains { proxy_pass http://127.0.0.1:8001/3.1/domains; } That particular configuration allows access to domains but not lists. Still,I recommend strong authentication on those locations. ... There are probably ways to get at pretty much everything once you have access to anything. For example, if you can get to a specific list, you can get its subscriber roster, and I think there's a way to pick a specific user, so then you can get their addresses and other subscriptions .... I haven't tried to do that, but I see no good reason to suppose pretty arbitrary path traversal is impossible. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for the REST API endpoints. Steve

1 year, 2 months

Problems with web interface after upgrade

by Victoriano Giralt

Hi, I just applied all the recipes that have been recently posted for upgrading (pip install --upgrade of all pieces, migrate, collectstatic) The compress part refuses to work "OFF_LINE", whatever that is. I tried with mailman running and stopped. I can access hte main Postorius page and the basic list information, but I cannot login nor access the archives. Operations end on two exceptions logged to the log file (and two mail messages to the owner = me). Very similar to what I get if I try to --force the "compress". I'm sure I'm missing somethning, but do not know what ... Thanks! Traceback: ERROR 2021-02-09 19:57:41,414 726 django.request Internal Server Error: /listas/accounts/login/ Traceback (most recent call last): File "/usr/local/lib/python3.6/site-packages/compressor/base.py", line 263, in precompile mod = import_module(mod_name) File "/usr/lib64/python3.6/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 994, in _gcd_import File "<frozen importlib._bootstrap>", line 971, in _find_and_load File "<frozen importlib._bootstrap>", line 953, in _find_and_load_unlocked ModuleNotFoundError: No module named 'sassc -t compressed {infile} {outfile}' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.6/site- packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/usr/local/lib/python3.6/site- packages/django/core/handlers/base.py", line 145, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/local/lib/python3.6/site- packages/django/core/handlers/base.py", line 143, in _get_response response = response.render() File "/usr/local/lib/python3.6/site- packages/django/template/response.py", line 106, in render self.content = self.rendered_content File "/usr/local/lib/python3.6/site- packages/django/template/response.py", line 83, in rendered_content content = template.render(context, self._request) File "/usr/local/lib/python3.6/site- packages/django/template/backends/django.py", line 61, in render return self.template.render(context) File "/usr/local/lib/python3.6/site- packages/django/template/base.py", line 171, in render return self._render(context) File "/usr/local/lib/python3.6/site- packages/django/template/base.py", line 163, in _render return self.nodelist.render(context) File "/usr/local/lib/python3.6/site- packages/django/template/base.py", line 937, in render bit = node.render_annotated(context) File "/usr/local/lib/python3.6/site- packages/django/template/base.py", line 904, in render_annotated return self.render(context) File "/usr/local/lib/python3.6/site- packages/django/template/loader_tags.py", line 150, in render return compiled_parent._render(context) File "/usr/local/lib/python3.6/site- packages/django/template/base.py", line 163, in _render return self.nodelist.render(context) File "/usr/local/lib/python3.6/site- packages/django/template/base.py", line 937, in render bit = node.render_annotated(context) File "/usr/local/lib/python3.6/site- packages/django/template/base.py", line 904, in render_annotated return self.render(context) File "/usr/local/lib/python3.6/site- packages/django/template/loader_tags.py", line 150, in render return compiled_parent._render(context) File "/usr/local/lib/python3.6/site- packages/django/template/base.py", line 163, in _render return self.nodelist.render(context) File "/usr/local/lib/python3.6/site- packages/django/template/base.py", line 937, in render bit = node.render_annotated(context) File "/usr/local/lib/python3.6/site- packages/django/template/base.py", line 904, in render_annotated return self.render(context) File "/usr/local/lib/python3.6/site- packages/compressor/templatetags/compress.py", line 131, in render return self.render_compressed(context, self.kind, self.mode, forced=forced) File "/usr/local/lib/python3.6/site- packages/compressor/templatetags/compress.py", line 107, in render_compressed rendered_output = compressor.output(mode, forced=forced) File "/usr/local/lib/python3.6/site-packages/compressor/css.py", line 49, in output ret.append(subnode.output(*args, **kwargs)) File "/usr/local/lib/python3.6/site-packages/compressor/css.py", line 51, in output return super(CssCompressor, self).output(*args, **kwargs) File "/usr/local/lib/python3.6/site-packages/compressor/base.py", line 295, in output output = '\n'.join(self.filter_input(forced)) File "/usr/local/lib/python3.6/site-packages/compressor/base.py", line 235, in filter_input for hunk in self.hunks(forced): File "/usr/local/lib/python3.6/site-packages/compressor/base.py", line 205, in hunks precompiled, value = self.precompile(value, **options) File "/usr/local/lib/python3.6/site-packages/compressor/base.py", line 268, in precompile return True, filter.input(**kwargs) File "/usr/local/lib/python3.6/site- packages/compressor/filters/base.py", line 229, in input return super(CachedCompilerFilter, self).input(**kwargs) File "/usr/local/lib/python3.6/site- packages/compressor/filters/base.py", line 196, in input raise FilterError(err) compressor.exceptions.FilterError: Error: It's not clear which file to import for '@import "../libs/bootstrap/stylesheets/bootstrap"'. Candidates: ../libs/bootstrap/stylesheets/_bootstrap.scss ../libs/bootstrap/stylesheets/bootstrap.scss Please delete or rename all but one of these files. on line 4 of static/hyperkitty/sass/hyperkitty.scss >> @import "../libs/bootstrap/stylesheets/bootstrap"; ^ -- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

5 years, 1 month

Re: Error when disabling signup

by Abhilash Raj

> On Aug 17, 2021, at 3:31 AM, Rainer Herbst <rainer.herbst(a)aip.de> wrote: > > Dear all, > > over the last couple of weeks, I have installed and configured mailman3 using the docker containers. > > It took me some time, but now it works quite well. At last, I wanted to disable the sign-up because only LDAP users should be able to login. > > As described in django_mailman3/views/user_adapter.py, I added the following line > to my settings_local.py: > ACCOUNT_ADAPTER = 'django_mailman3.views.user_adapter.DisableSignupAdapter' This isn’t going to work unless you are using the ‘rolling’ releases. The changes for disabling signups haven’t yet been released unfortunately. > > > After that, an error is thrown: > ModuleNotFoundError at /accounts/login/ > No module named 'django_mailman3.views.user_adapter' > > What could be the reason for that and how to solve it? > > Thanks in advance! > Rainer > > Here is the traceback: > Environment: > > Request Method: GET > Request URL: https://mailman.aip.de:1443/accounts/login/?next=%2Faccounts%2Flogin%2F > > Django Version: 2.2.19 > Python Version: 3.8.5 > Installed Applications: > ['hyperkitty', > 'postorius', > 'django_mailman3', > 'django.contrib.admin', > 'django.contrib.auth', > 'django.contrib.contenttypes', > 'django.contrib.sessions', > 'django.contrib.sites', > 'django.contrib.messages', > 'django.contrib.staticfiles', > 'rest_framework', > 'django_gravatar', > 'compressor', > 'haystack', > 'django_extensions', > 'django_q', > 'allauth', > 'allauth.account', > 'allauth.socialaccount'] > Installed Middleware: > ('django.contrib.sessions.middleware.SessionMiddleware', > 'django.middleware.common.CommonMiddleware', > 'django.middleware.csrf.CsrfViewMiddleware', > 'django.middleware.locale.LocaleMiddleware', > 'django.contrib.auth.middleware.AuthenticationMiddleware', > 'django.contrib.messages.middleware.MessageMiddleware', > 'django.middleware.clickjacking.XFrameOptionsMiddleware', > 'django.middleware.security.SecurityMiddleware', > 'django_mailman3.middleware.TimezoneMiddleware', > 'postorius.middleware.PostoriusMiddleware') > > > > Traceback: > > File "/usr/lib/python3.8/site-packages/django/core/handlers/exception.py" in inner > 34. response = get_response(request) > > File "/usr/lib/python3.8/site-packages/django/core/handlers/base.py" in _get_response > 115. response = self.process_exception_by_middleware(e, request) > > File "/usr/lib/python3.8/site-packages/django/core/handlers/base.py" in _get_response > 113. response = wrapped_callback(request, *callback_args, **callback_kwargs) > > File "/usr/lib/python3.8/site-packages/django/views/generic/base.py" in view > 71. return self.dispatch(request, *args, **kwargs) > > File "/usr/lib/python3.8/site-packages/django/utils/decorators.py" in _wrapper > 45. return bound_method(*args, **kwargs) > > File "/usr/lib/python3.8/site-packages/django/views/decorators/debug.py" in sensitive_post_parameters_wrapper > 76. return view(request, *args, **kwargs) > > File "/usr/lib/python3.8/site-packages/allauth/account/views.py" in dispatch > 146. return super(LoginView, self).dispatch(request, *args, **kwargs) > > File "/usr/lib/python3.8/site-packages/allauth/account/views.py" in dispatch > 74. response = super(RedirectAuthenticatedUserMixin, self).dispatch( > > File "/usr/lib/python3.8/site-packages/django/views/generic/base.py" in dispatch > 97. return handler(request, *args, **kwargs) > > File "/usr/lib/python3.8/site-packages/allauth/account/views.py" in get > 90. response = super(AjaxCapableProcessFormViewMixin, self).get( > > File "/usr/lib/python3.8/site-packages/django/views/generic/edit.py" in get > 133. return self.render_to_response(self.get_context_data()) > > File "/usr/lib/python3.8/site-packages/allauth/account/views.py" in get_context_data > 173. signup_url = passthrough_next_redirect_url( > > File "/usr/lib/python3.8/site-packages/allauth/account/utils.py" in passthrough_next_redirect_url > 444. next_url = get_next_redirect_url(request, redirect_field_name) > > File "/usr/lib/python3.8/site-packages/allauth/account/utils.py" in get_next_redirect_url > 45. if not get_adapter(request).is_safe_url(redirect_to): > > File "/usr/lib/python3.8/site-packages/allauth/account/adapter.py" in get_adapter > 535. return import_attribute(app_settings.ADAPTER)(request) > > File "/usr/lib/python3.8/site-packages/allauth/utils.py" in import_attribute > 155. ret = getattr(importlib.import_module(pkg), attr) > > File "/usr/lib/python3.8/importlib/__init__.py" in import_module > 127. return _bootstrap._gcd_import(name[level:], package, level) > > File "<frozen importlib._bootstrap>" in _gcd_import > 1014. <source code not available> > > File "<frozen importlib._bootstrap>" in _find_and_load > 991. <source code not available> > > File "<frozen importlib._bootstrap>" in _find_and_load_unlocked > 973. <source code not available> > > Exception Type: ModuleNotFoundError at /accounts/login/ > Exception Value: No module named 'django_mailman3.views.user_adapter' > > > > Viele Grüße, > > Rainer Herbst > Leiter IT-Service > Phone: +49 331 7499-257 > e-mail: rainer.herbst(a)aip.de > https://www.aip.de > > ----------------------------------------------------------------------------------------------- > Leibniz-Institut für Astrophysik Potsdam (AIP) > An der Sternwarte 16, 14482 Potsdam > > Vorstand: Prof. Dr. Matthias Steinmetz, Wolfram Rosenbach > Stiftung bürgerlichen Rechts > Stiftungsverzeichnis Brandenburg: 26 742-00/7026 > ----------------------------------------------------------------------------------------------- > > _______________________________________________ > 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)

4 years, 7 months

Re: Fwd: Re: Removing a mail addresses and users

by Stephen J. Turnbull

Mark Sapiro writes: > Then the people who developed the web based management UI (Postorius) > and archive UI (HyperKitty) chose to develop those within a Django > framework and Django has its own concept of User separate from Mailman > Core and that is where the disconnect occurs. > > It's not that Mailman Core lacks what you want. It's that Django doesn't > use it. I think that's mostly right, in terms of the features that users miss. However, as far as I know, Mailman core does lack facilities for identification, authentication, and authorization of connections to the REST API. And that means that the front ends have to handle this. I would guess that's why the web interfaces are built around Django user authentication. I think it would be possible to have somewhat tighter integration between the Django "web users" and the Mailman core User objects, but it's not necessarily going to be trivial. I see that Abhilash is pretty optimistic, but I fear this this is going to be a long-tail situation where we're going to be seeing core user vs. web-gui user integration issues in 2030 (maybe by then only 1 every 450 days ;-). I have some ideas, maybe in a couple weeks I can sketch them out. Steve

5 years, 9 months

Mailman-users search results for query "Postorius"