Search results for "Postorius" - Mailman-users

Question after upgrade to mm 3.2.3 and latest postorius

by David Krantz

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: 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. 2. The template menu simply does not work, it seems as if some database table is missing even after running migrations. 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

7 years, 1 month

Re: Emergency Moderation

by Brian Carpenter

On 5/21/20 6:30 PM, Mark Sapiro wrote: > On 5/21/20 3:23 PM, Brian Carpenter wrote: >> Is there an Emergency Moderation function (similar to the one that Mailman 2 had) with Mailman 3 core/Postorius? > > It's in core and it's just recently been exposed in REST > https://gitlab.com/mailman/mailman/-/merge_requests/643 but it's not in > Postorius yet. > Can I add this through a mailman core update via pip? Thank you for the information. It is very helpful. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

6 years, 3 months

Re: Help with installing Postorius and Hyperkitty on Ubuntu 19

by Mark Sapiro

On 6/8/19 4:33 PM, Andrew Bernard wrote: > Hi Mark, > > Thanks for your great help. But despite decades of UNIX experience, my area > is not Django (yet). The nub of my question is that I thought you have to > have a manage.py file for Django to be able to set up the various affairs, > such as making the database migrations and so on. It is that that is > eluding me. Apologies for this hopelessly newbie question. The equivalent of manage.py in what I suggested is /opt/mailman/bin/django-admin. > I was impressed with your method of installation in the page referenced, > and I have foolwed that closely. But I am puzzled about the build script. > If I run as user mailman, not root, it wanted to install under /usr. which > of course results in permission denied. I had to modify the script to say > this: > > python setup.py install --prefix /opt/mailman/mm/venv If you want to install in the virtualenv, you should just activate the virtualenv and it should work. Perhaps the issue is that the build script at <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…> assumes the virtualenv is at /opt/mailman/mm/venv. You need to insure that the '. ../mm/venv/bin/activate' line is actually pointing to your 'venv/bin/activate' -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 3 months

Re: django fake users

by Stephen J. Turnbull

Andrew Hodgson writes: > >Require moderator approval for subscribing. > > 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). Ah, so "fake" == "account in Django but no user in Mailman"? I don't have time to look at it, so take this with a grain of salt, but I don't think they are passing the email confirmation. If they were, they would show up in Mailman. > 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. I think this would be simple enough to deal with (not trivial, so I'm not making any promises except to try adding it to the GSoC ideas page -- that should be enough to clarify whether there are any "annoyance to 'real' users" issues, and we move forward from there if there aren't). Basically, Postorius should notify Mailman that there is a *pending* user in Django, and if there's no confirmation by a deadline, remove that user. This requires a bunch of infrastructure like a table of "pending" users, callbacks for the deletion, etc, but I don't see why it would be conceptually difficult. (This combination is why I think it would be a good GSoC task) Steve

5 years, 8 months

Re: Disabling the version disclosure.

by ninad＠iitb.ac.in

Steve from another mailman list suggested the below solutions. 1st method suggested worked. This is just for this group's information. Thank Steve for the solution. --------------------------------------- Suggested solution ------------------------------------------------------- It helps to explain why you don't want to change the HTML code, because there are several ways to do this, with different implications both for the page's appearance and for future maintenance. The visually cleanest way to do this is to copy the files site-packages/postorius/templates/postorius/base.html site-packages/hyperkitty/templates/hyperkitty/base.html to /etc/mailman3/templates/postorius/base.html /etc/mailman3/templates/hyperkitty/base.html search for '_VERSION' and delete or edit the version stanzas near the end of those files, add TEMPLATES[0]['DIRS'].append('/etc/mailman3/templates') somewhere in /etc/mailman3/settings.py, and restart mailman-web (typically as root, using 'systemctl restart mailmanweb'). Alternatively and less visually appealing you can clear the version variable itself with a file 'site-packages/version_hack.py' containing the lines def suppress_version(request): return {"HYPERKITTY_VERSION": "Wouldn't you like to know?", "POSTORIUS_VERSION": "Wouldn't you like to know?"} ... you probably want to change the strings to empty strings ... and add the lines TEMPLATES[0]['OPTIONS']['context_processors'].append( 'version_hack.suppress_version' ) somewhere in /etc/mailman3/settings.py, and restart mailman-web. The former method of overriding the templates is a supported API, and very unlikely to be obsoleted any time soon. The latter method of patching the variables is something of a hack, and also leaves the tags like "Postorius version" visible in the page. Steve ----------------------------------------------------------------------------------------

1 year, 5 months

Re: Postorius no connection to REST API

by Mark Sapiro

On 8/9/21 8:56 AM, Richard Rosner wrote: > Mark Sapiro wrote: > >>> The REST API is apparently not listening on the host/port this is trying >> to connest to. > > Apparently. The question is why. You are in a better position to answer that than am I. What does `sudo netstat -lntp` show? What does `ps -fwwa|grep rest` show? >>> What is executing the manage.py command to start Django. Is it user list? > > Probably. It depends on who is calling it. I understand too little of the new architecture. But mailman3.service is run as list, mailman3-web.service as root. mailman3-web.service must also run as list. >>> 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 > > I too have no experience in the combination ow apache and uwsgi. The only other uwsgi app I'm running is on another server and running under nginx. So, what do you have in your apache config for proxying to uwsgi and what's your uwsgi configuration. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

Re: Core, Hyperkitty and Postorius releases

by Odhiambo Washington

On Sat, May 15, 2021 at 1:08 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/14/21 3:00 PM, Odhiambo Washington wrote: > > On Sat, May 15, 2021 at 12:47 AM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> Those are headers for compiling some sass. Possibly you actually have a > >> `sassc` installed in which case you may need > >> > >> COMPRESS_PRECOMPILERS = ( > >> ('text/x-scss', 'sassc -t compressed {infile} {outfile}'), > >> ('text/x-sass', 'sassc -t compressed {infile} {outfile}'), > >> ) > >> > >> > > This change makes the error I was getting to go away. However, I cannot > > login to manage lists, even after restarting mailman. > > > > The error details are here: https://pastebin.ubuntu.com/p/vM2c5WYyJ4/ > > > The relevant part of which is > > OfflineGenerationError at /accounts/login/ > You have offline compression enabled but key > "fa788b08b65fd318d68cfc5afebc18acd3e93cebffadb54d863572ad1754f368" is > missing from offline manifest. You may need to run "python manage.py > compress". Here is the original content: > > I.e., something went wrong with your compress command. Try it again. > I have successfully run the following commands: /opt/mailman/mm/bin/django-admin collectstatic --clear --noinput --verbosity 0 /opt/mailman/mm/bin/django-admin compress /opt/mailman/mm/bin/django-admin compilemessages /opt/mailman/mm/bin/django-admin migrate But the error at https://pastebin.ubuntu.com/p/vM2c5WYyJ4/ persists. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

5 years, 4 months

Re: Can login at /admin, but cannot login at the account/login page.

by Stephen J. Turnbull

Gonzalo Cardenas writes: > Actually it doesn't let me in to the login page / sign up page (the > HTTP requests hangs until it times out). The URL I'm trying to > access is http://localhost/accounts/login/?next=/mailman3/lists/ or > http://localhost:8002/accounts/signup/?next=/mailman3/lists/ > eventually Nginx returns a "502 Gateway timeout error" The second URL appears to presume Postorius is actually running on port 8002, but this > location / { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; tells nginx to proxy to port 8000. I don't use nginx or uwsgi myself (I use Apache and mod_wsgi) so I am not very confident. But you need to make sure that all of the configuration files use the same port. I don't remember if any of the webservers suffered from this, but some programs don't map 127.0.0.1 to localhost. If any of the configs specify localhost for the Postorius URI, you could try using 127.0.0.1 instead. If making all these port configurations consistent doesn't do the trick, please post your mailman-web settings.py, uswgi config, and nginx config. You can substitute fake domain names and IP addresses if you're worried about privacy of your configs, but make sure that (1) if the configs specify several IPs or several domain names, you distinguish them in your fake versions, and (2) always substitute the same fake IP/name for a given real IP/name. Steve

4 years, 4 months

Re: Changing subscription address

by Stephen J. Turnbull

Andreas Barth writes: > To make it more complex (perhaps?), I'd like to switch django to use > the single sign on-system, which means: mail adresses and user > accounts are managed elsewhere, and djano / mailman / whatever > component consumes accounts (and verified mail adresse) from the > central account store. Django *is* our single-sign-on system, and Mailman core *is* our central account store. That's why it's possible to mix and match Mailman core with other UI applications. This has been proved in practice by at least one commercial service. That is, we don't do *any* authentication in Mailman core. And because authenticating general Internet connections is *hard*, we want to keep it that way![1] ;-) The single exception is the mail address verification dance, which is an extremely simple protocol with a well-known threat model that nobody can do anything about (somebody who can read your mail).[2] So we delegate authentication and credentials management to Django, which already knows how to do passwords, OAuth and friends, and probably multifactor, too. That's *all* that the Django account functionality does for Postorius.[3] All the other user and admin information that Postorius exposes are ultimately backed by queries to Mailman core's REST API, not by Django's internal database. This subthread is 100% about how to initialize the Mailman core user record in a way more consistent with user expectations. The other, closely related subthread is about presenting tables of subscriber data for multiple subscriptions, instead of requiring people to visit per-subscription pages. There's no need to change the division of labor between core and Postorius to implement either. Steve Footnotes: [1] We probably can't, in the long run. People definitely want Mailman systems distributed across multiple hosts, and there are limits to how well that can work with all the hosts behind a firewall. That implies authenticating connections to the REST API endpoints. [2] Technically, in theory we could encrypt the verification email in case there's a miscreant-in-the-middle who can read plain text, but then we've got a key distribution problem and a user education problem. Encryption is like regexps but worse: whenever you have a problem and you adopt encryption as the answer, now you have *three* problems! :-P [3] I'm not sure about HyperKitty. Mailman core doesn't know or care about web preferences, so I suppose HyperKitty has to store them somewhere.

5 years, 5 months

Re: postfix virtual domain and mailman 3

by Mark Sapiro

On 12/25/19 1:53 PM, work(a)andrefincato.info wrote: > > question: i tried to add the `alias_domain` to mailman using Mailman Core REST APIs because I read about https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#unusual-… ; entering the mailman console and doing `dump_json('http://localhost:9001/3.0/domains/example.com/lists')` was giving me error that `dump_json` is not an available module. > > is that the way to go? should I add a an `alias_domain` to Mailman in order for it to output a `postfix_vmap` when doing `mailman aliases`? and then add it to postfix `main.cf` like so > > ``` > virtual_alias_maps = hash:/etc/postfix/valias, regexp:/opt/mailman/var/data//postfix_vmap > ``` I think the above should work for you. As far as `dump_json` is not an available module goes, the docs reference a lot of helper functions that are described at <https://mailman.readthedocs.io/en/latest/build/lib/mailman/docs/documentati…>. These need to be imported. I.e., for dump_json ``` from mailman.testing.documentation import dump_json ``` But, if you are just trying to set an alias_domain for the domain and you have Postorius, you can do that via Postorius. If not Postorius you can use `mailman shell`, For example ``` $ mailman shell Welcome to the GNU Mailman shell >>> dm = getUtility(IDomainManager) >>> d = dm.get('example.com') >>> d.alias_domain = 'x.example.com' >>> ``` Then you need to do `mailman aliases` to create/update the maps. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 8 months

Mailman-users search results for query "Postorius"