Search results for "Postorius" - Mailman-users

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

7 years, 2 months

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

4 months, 2 weeks

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

4 years, 11 months

Re: Error while running mailman-web compilemessages

by Stephen J. Turnbull

Philip Colmer writes: > Looking at the packaging for mailman-web and mailman-hyperkitty, the former > (https://gitlab.com/mailman/mailman-web) specifies "django >=2.2, !=3.0, > <4" This is the relevant requirement, mailman-web is what actually configures django for use by HyperKitty and Postorius. > and the latter (https://gitlab.com/mailman/mailman-hyperkitty/) doesn't > seem to specify a django version requirement. IIRC, mailman-hyperkitty is the small Python module that enables core to send posts to a hyperkitty. That module has nothing to do with Django. > There is a separate Hyperkitty project > (https://gitlab.com/mailman/hyperkitty) which has added support for > Django 4 but that doesn't seem to be what is installed by following > the instructions at > https://docs.mailman3.org/en/latest/install/virtualenv.html This is all very confused (lots of duplication across several project and multiple documented configurations requiring slightly different lists of projects for installation), and we need to clean it up. We're aware of it, but cleaning up is hard because it means that sources for people's existing installations are going to disappear. Also, mailman/hyperkitty is the actual implementation of HyperKitty, and I don't think Django 4 support is considered anything like stable yet, which is why mailman-web doesn't allow it. Volunteers to identify duplication and help with deduplication welcome! ;-)

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

4 years, 3 months

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)

3 years, 9 months

Re: Mailman 3 Social Auth Configuration

by Mark Sapiro

On 10/12/2016 08:09 PM, emonical(a)misfitlabs.org wrote: > > I am a new Mailman 3 user and have just gotten an environment configured using the Mailman bundler. The setup is almost complete, but, there's still Persona authorization. Mailman bundler installs the latest releases from PyPI, but those are behind the latest development branches. > I was reading the your setup here from (https://wiki.list.org/DOC/Mailman%203%20installation%20experience) and was wondering if someone might have some insight as to how to remove the Persona log in to keep it locked down entirely to localized user registration. With the latest gitlab branches, you will have Django Allauth. This includes login by verified email and password, and if you choose to not use any of the supported Oauth2 providers, that will be the only method. To do this without waiting for the Mailman 3.1 release and an updated bundler, you will need to install the latest master branches from <https://gitlab.com/groups/mailman> for Mailman, Postorius, HyperKitty, MailmanClient, django-mailman3 and HyperKitty - Mailman plugin. The wiki article <https://gitlab.com/groups/mailman> will give some insight into the process, but it isn't fully current. I will be updating it. Meanwhile, ask your specific questions here and we will try to help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 7 months

Problems after update to mailman 3.3.7

by Guillermo Hernandez (Oldno7)

I've getting the most strange behaviour after update to last releases. In one of my mailman3 servers, the messages doesnt reach for some lists (the five last ones) the update have not showed any error but in the var/data for the lmtp and vmap postfix files mailman does not create aliases for that last 5 lists. Any message addressed to them is returned with a "no such user" error. If I create a new list the system or restart mailman runners it shows this error: Generating MTA alias maps /usr/local/lib/python3.9/site-packages/pymysql/connections.py:799: UserWarning: Previous unbuffered result was left incomplete warnings.warn("Previous unbuffered result was left incomplete") I did a CHECK TABLE on mailinglists table but all seems ok. I tried reinstalling PyMySQL, but has no effect. (well, I tried reinstalling all) It seems to me that something is preventing creation of that aliases, an then the that last five lists are unreachable. I have no clue of what to do now and I'm driving crazy. Some direction to look for will be much apreciated. Thanks in advance. P.S.: I can access via postorius/hyperkitty to the archives of the lists that are unreacheable. -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

2 years, 6 months

Re: lists.mailman3.org web site.

by Mark Sapiro

On 08/27/2016 09:15 PM, Mark Sapiro wrote: > I have just upgraded the lists.mailman3.org Mailman 3 installation to > the heads of the GitLab mailman* branches. A major change is the switch > from Persona to Django Allauth. This requires some configuration which > isn't yet complete. Hopefully it will all be working very soon. > > In the mean time if you want to log in to Hyperkitty/Postorius you > should be able to log in with your email address. The first time you do > this, Mailman probably won't even know your password so you'll have to > request a reset. Once you have reset your password, you should be able > to log in. > > I hope to have several social auth choices working very soon. Update: Django Allauth is now properly configured and working on lists.mailman3.org. You can log in by email/password as noted above or via OAuth2 with a GitHub, GitLab, Google or Facebook identity. If you are an existing user, in order to use one of the OAuth2 providers, you must first log in with email and password and go to the Account Connections tab in your account settings and add the 3rd party account(s) you wish. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 9 months

Re: Mailman3 don't work if aliases are enabled

by Mark Sapiro

On 10/9/20 3:37 PM, Massimo Zappalà wrote: > > If I try to uncomment the last two rows in main.cf > virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_emails.cf, mysql:/etc/postfix/mysql_virtual_alias_maps.cf > virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailbox_maps.cf > The aliases and email messeges works fine but the mailman3's mailinglist don't work. > > How can I solve this? I'm not certain about this. The Postfix log entries for the failed delivery to Mailman may help, but I think you deed to configure an alias domain or domains for your list domain(s). The alias domain is not a real domain and is not in DNS. it is any unused domain name and will be known only to Postfix. I typically use x.example.com where example.com is the real list domain. You can set the alias domain for the real domain in the domains view in Postorius. Then you need to add `hash:/var/lib/mailman3/data/postfix_vmap` to your main.cf virtual_alias_maps setting and run Mailman's `mailman aliases` command to generate the proper /var/lib/mailman3/data/postfix_* files. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…>. You may also need to set relay_domains = hash:/var/lib/mailman3/data/postfix_domains -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

Mailman-users search results for query "Postorius"