Search results for "Postorius" - Mailman-users

How to add new Domain?

by c.benner＠apd-it.eu

Hello, i'm really new to mailman3 and I've been using mm2.1 couple of years. It's really hardto understand documentation. But I'll do one in german language next time. I've got it installed ob Debian12 and it's working now. It takes a little more time to understand all settings and also the difference between postorius and django and what is when used for. But what I do not understand 'til now is how to add a new domain. My running config has one domain (e.g.) testdomain1.org and everything is working fine. The Domain has a virtualhost which listens on *:443 (with LE cert) Postfix works like a charm. The interface of the machine is bound to one IP Address public but for example here written as: 192.168.200.15 Id like to add a new Domain. My first step would be to add another IP Address to the interface: (e.g.) 192.168.200.16 Then I'll change the virtual host settings in apache conf from first domain which is actually listeing to *:443 to 192.168.200.15:443 And add a second site with 192.168.200.16:443 So the "physical" part is done Is that right 'til now? After that I'll go to the admin page xxxx/mailman3/admin which brings django admin page up. On that page I'll add "websites" and add testdomain2.net Last step is adding "mail domain" site: testdomain2.net mail domain: testdomain2.net After that I can add lists to that domain and mails to any list @testdomain2,net should be routed right? Maybe I'm to old (56yrs) but I've read a lot of documentation and everything was clear and understandable. It was never a question of linux or windows OS but on who'S writing the doc. I can't find any doc about the web part? What about Users having no acces to the shell but the Web-Frontend? Some pictures and a "How to" and "what if" would be great! But it's alos possible that I'm not finding it and it's somewhere out there. Thanks in advance.

11 months, 2 weeks

Re: Changing web access

by Ralf Wiegand

GNU Mailman 3.3.1 (Tom Sawyer) Python 3.6.8 (default, Sep 26 2019, 11:57:09) [GCC 4.8.5 20150623 (Red Hat 4.8.5-39)] config file: /opt/mailman/mailman/var/etc/mailman.cfg db url: sqlite:////opt/mailman/mailman/var/data/mailman.db devmode: DISABLED REST root url: https://empire:8001/3.1/ REST credentials: r****n:r*****s My REST API is running on "empire" (192.168.0.27), but isn't this messages referencing >>> snip python manage.py runserver 0.0.0.0:8000 Performing system checks... System check identified no issues (0 silenced). April 22, 2020 - 19:05:09 Django version 2.2.12, using settings 'settings' Starting development server at http://0.0.0.0:8000/ Quit the server with CONTROL-C. ERROR Mailman REST API not available Traceback (most recent call last): File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/urllib3-1.25.8-py3.6.egg/urllib3/connection.py", line 157, in _new_conn (self._dns_host, self.port), self.timeout, **extra_kw File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/urllib3-1.25.8-py3.6.egg/urllib3/util/connection.py", line 84, in create_connection raise err File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/urllib3-1.25.8-py3.6.egg/urllib3/util/connection.py", line 74, in create_connection sock.connect(sa) ConnectionRefusedError: [Errno 111] Connection refused During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/urllib3-1.25.8-py3.6.egg/urllib3/connectionpool.py", line 672, in urlopen chunked=chunked, File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/urllib3-1.25.8-py3.6.egg/urllib3/connectionpool.py", line 387, in _make_request conn.request(method, url, **httplib_request_kw) File "/usr/lib64/python3.6/http/client.py", line 1254, in request self._send_request(method, url, body, headers, encode_chunked) File "/usr/lib64/python3.6/http/client.py", line 1300, in _send_request self.endheaders(body, encode_chunked=encode_chunked) File "/usr/lib64/python3.6/http/client.py", line 1249, in endheaders self._send_output(message_body, encode_chunked=encode_chunked) File "/usr/lib64/python3.6/http/client.py", line 1036, in _send_output self.send(msg) File "/usr/lib64/python3.6/http/client.py", line 974, in send self.connect() File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/urllib3-1.25.8-py3.6.egg/urllib3/connection.py", line 184, in connect conn = self._new_conn() File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/urllib3-1.25.8-py3.6.egg/urllib3/connection.py", line 169, in _new_conn self, "Failed to establish a new connection: %s" % e urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x7f8dd8cdee80>: Failed to establish a new connection: [Errno 111] Connection refused During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/requests-2.23.0-py3.6.egg/requests/adapters.py", line 449, in send timeout=timeout File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/urllib3-1.25.8-py3.6.egg/urllib3/connectionpool.py", line 720, in urlopen method, url, error=e, _pool=self, _stacktrace=sys.exc_info()[2] File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/urllib3-1.25.8-py3.6.egg/urllib3/util/retry.py", line 436, in increment raise MaxRetryError(_pool, url, error or ResponseError(cause)) urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='localhost', port=8001): Max retries exceeded with url: /3.0/lists?advertised=true&count=0&page=1 (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f8dd8cdee80>: Failed to establish a new connection: [Errno 111] Connection refused',)) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailman/mailmanclient/src/mailmanclient/restbase/connection.py", line 96, in call headers=headers) File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/requests-2.23.0-py3.6.egg/requests/api.py", line 61, in request return session.request(method=method, url=url, **kwargs) File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/requests-2.23.0-py3.6.egg/requests/sessions.py", line 530, in request resp = self.send(prep, **send_kwargs) File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/requests-2.23.0-py3.6.egg/requests/sessions.py", line 643, in send r = adapter.send(request, **kwargs) File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/requests-2.23.0-py3.6.egg/requests/adapters.py", line 516, in send raise ConnectionError(e, request=request) requests.exceptions.ConnectionError: HTTPConnectionPool(host='localhost', port=8001): Max retries exceeded with url: /3.0/lists?advertised=true&count=0&page=1 (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f8dd8cdee80>: Failed to establish a new connection: [Errno 111] Connection refused',)) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/postorius/src/postorius/views/list.py", line 755, in list_index paginator_class=MailmanPaginator) File "/opt/mailman/django-mailman3/django_mailman3/lib/paginator.py", line 71, in paginate objects = paginator.page(page_num) File "/opt/mailman/django-mailman3/django_mailman3/lib/paginator.py", line 46, in page number = self.validate_number(number) File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/core/paginator.py", line 48, in validate_number if number > self.num_pages: File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/utils/functional.py", line 80, in __get__ res = instance.__dict__[self.name] = self.func(instance) File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/core/paginator.py", line 97, in num_pages if self.count == 0 and not self.allow_empty_first_page: File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/utils/functional.py", line 80, in __get__ res = instance.__dict__[self.name] = self.func(instance) File "/opt/mailman/django-mailman3/django_mailman3/lib/paginator.py", line 56, in count return self.function(count=0, page=1).total_size File "/opt/mailman/postorius/src/postorius/views/list.py", line 751, in _get_list_page advertised=advertised, mail_host=mail_host, count=count, page=page) File "/opt/mailman/mailmanclient/src/mailmanclient/client.py", line 181, in get_list_page return Page(self._connection, url, MailingList, count, page) File "/opt/mailman/mailmanclient/src/mailmanclient/restbase/page.py", line 37, in __init__ self._create_page() File "/opt/mailman/mailmanclient/src/mailmanclient/restbase/page.py", line 62, in _create_page response, content = self._connection.call(self._build_url()) File "/opt/mailman/mailmanclient/src/mailmanclient/restbase/connection.py", line 120, in call 'Could not connect to Mailman API: ', repr(e)) mailmanclient.restbase.connection.MailmanConnectionError: ('Could not connect to Mailman API: ', 'ConnectionError(MaxRetryError("HTTPConnectionPool(host=\'localhost\', port=8001): Max retries exceeded with url: /3.0/lists?advertised=true&count=0&page=1 (Caused by NewConnectionError(\'<urllib3.connection.HTTPConnection object at 0x7f8dd8cdee80>: Failed to establish a new connection: [Errno 111] Connection refused\',))",),)') <<<< snip not sure I understand??? On 4/22/20 2:50 PM, Mark Sapiro wrote: > On 4/22/20 11:35 AM, Ralf Wiegand wrote: >> but I am getting : >> >> mailmanclient.restbase.connection.MailmanConnectionError: ('Could not >> connect to Mailman API: ', >> 'ConnectionError(MaxRetryError("HTTPConnectionPool(host=\'localhost\', >> port=8001): Max retries exceeded with url: >> /3.0/lists?advertised=true&count=0&page=1 (Caused by >> NewConnectionError(\'<urllib3.connection.HTTPConnection object at >> 0x7f88fe4cb4e0>: Failed to establish a new connection: [Errno 111] >> Connection refused\',))",),)') > > What do you have for ALLOWED_HOSTS in your settings file(s)? You may > want something like > > ALLOWED_HOSTS = ['*'] > > or > > ALLOWED_HOSTS = ['192.168.*'] >

5 years, 8 months

Re: One-click unsubscribe?

by Jered Floyd

Reviving this thread I started in February because delivery rates continue to decline, and I get this threat from Google any time I check their Dashboard: "One-click Unsubscribe: Needs work — Ensure one-click unsubscribe is correctly implemented for your subscription messages One-click unsubscribe allows recipients to easily unsubscribe instead of marking your messages as spam" Having recently implemented "Feedback-ID" (Google's proprietary-but-required Feedback Loop mechanism) at my MTA, all this has done is confirm that 0.05-0.10% of subscribers report messages as spam and would probably rather be unsubscribed but cannot be bothered to figure this out. Having the headers that make Google/Yahoo/Apple/etc ask "Would you like to unsubscribe from this?" when they hit the "Junk" button will most likely resolve the problem. I'm pretty sure, as below, that we need to implement RFC 8058 headers in order to maintain deliverability to GMail. The only tracker issue I can find related to this is https://gitlab.com/mailman/mailman/-/issues/1099 -- is that the best place to discuss implementation? --Jered ----- On Feb 5, 2025, at 3:36 AM, Stephen J. Turnbull turnbull(a)sk.tsukuba.ac.jp wrote: [..] > If we're talking about a new feature, I think the most straightforward > approach is to use RFC 8058[1] "one click" URLs. I believe it is > already implemented by Gmail and Yahoo, I don't know about Outlook or > the open source MUAs. This would require a substantial (but > straightforward[2]) addition of code, and of course personalized > delivery (I don't know if anyone balks at that any more, though). [..] > Footnotes: > [1] https://datatracker.ietf.org/doc/html/rfc8058 > [2] That is, we'd need to add a new location in Postorius and code to > accept POST access to it, encrypt/decrypt functionality to handle an > opaque token (to prevent automated denial of service by folks without > access to the person's email) or a table of one-time tokens with > expiration (same purpose, and expiring so the database doesn't grow > infinitely). What we wouldn't need to do is to change any exsting > code.

1 month, 3 weeks

Re: moderation notices for list-owner being redirected to mailman address

by Mark Sapiro

On 2/7/22 16:11, Philippe B wrote: > I think that your last sentence helped us figure out what's going on. > > When Mailman generates a moderation message "To: LIST-owner" it actually delivers it to the address(es) of the LIST's moderator(s), which makes sense. No, it delivers the message to the union of the sets of owner addresses and moderator addresses. > In all the cases where we've seen that behavior, it turns out that the list involved didn't have any moderator, and we have site_owner set to "mailman"... You don't need to have moderators. The owners get the message too. > However, the lists had an owner, and we're not seeing those moderation messages being sent to their owner (instead). Is that something that needs to be configured explicitly somewhere? The only things that might affect this are if Settings -> Automatic Responses -> Autorespond to list owner is Respond and discard message or if the owners delivery_status is other than DeliveryStatus.enabled. Note that finding an owner's delivery status is tricky. The owner can find it in Postorius by going to https://www.example.com/mailman3/accounts/subscriptions/ and clicking on the entry for the list with role owner. This delivery status is not the same as the delivery status for the same address with a member role if there is one. For an admin you could do ``` $ bin/mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list >>> owner = m.owners.get_member('user(a)example.com') >>> owner.delivery_status <DeliveryStatus.enabled: 1> If you needed to set it here, you could do >>> owner.preferences.delivery_status = DeliveryStatus.enabled >>> commit() >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

Re: Mailman3 migration and/or archiving problem

by Odhiambo Washington

On Fri, Sep 6, 2024 at 11:43 AM <hnpilot(a)phnet.fi> wrote: > I have installed a mailman3 server following this documentation: > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… > > After a few hiccups I got mailman and postorius working and migrated one > list according to this documentation: > https://docs.mailman3.org/en/latest/migration.html > > It seemed to work and also hyperkitty_import was run without errors (or at > least none shown up). Running update_index command said that there were 0 > threads copied but I kjnow that the archive isn't empty. But now when I > tried to open the list info page from lists view it dies with 500 error. > > After diving into the different log files I found an error message that it > cannot find /etc/mailman3/mailman-hyperkitty.cfg. Great. Only that the cfg > file exists and seems to my (unexpert) eyes correct. > > After that problem I tried to create a new list. Creation seemed to go all > right but also with it, trying to open the list info page it shows 500 > error. > > When googling for a solution I landed on a message stating that there > might be double entries for the same list in listarchiver table but when I > checked ot turns out that the table is empty! > > I am a bit confused how to figure out the base cause of the problem and > would very much appreciate any pointers. > The documentation you followed is quite okay and reasonably detailed. Just wipe out your virtualenv and start over again. Practice it till you get it working. I suspect you missed a step - or did not understand well. You just need to seek clarification on that. Looking at the mailman-web logfile mentioned in that documentation might also help you. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 4 months

Hipperkitty failing to archive messages in a list

by Guillermo Hernandez (Oldno7)

First of all, best wishes and Happy New Year for everybody. Two days ago I had to reinstall all mailman3 related apps in a mailman 3 server (I tried to upgrade just hipperkitty, but it went bad). At first, all seemed running as before, but I just noted that the messages are not being archived. I did not change any config. Now the log is showing ERROR 2022-01-03 12:22:15,654 7165 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-03 12:22:15,674 7165 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-03 12:22:15,791 7165 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-03 12:22:16,208 7165 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-04 11:44:55,644 30518 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header ERROR 2022-01-04 11:44:55,664 30518 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header ERROR 2022-01-04 11:44:56,478 30518 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header ERROR 2022-01-04 11:44:56,620 30518 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header ERROR 2022-01-04 11:44:56,647 30518 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header (it's a very low traffic list: just two messages in two days) I do believe I did the upgrade/reinstall procedure as in previous upgrades (using pip: it's a system wide installation, not using dockers or venv), but seems that I did something wrong The messages are being delivered normally, but it fails archiving Before I make a bigger hole for myself, where to look for? Versions installed: HyperKitty 1.3.5 mailman 3.3.5 mailman-hyperkitty 1.2.0 mailmanclient 3.3.3 postorius 1.3.6 uWSGI 2.0.19.1 Mailman Core Version GNU Mailman 3.3.5 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.7.9 (default, Nov 30 2020, 10:49:53) [Clang 10.0.1 (git@github.com:llvm/llvm-project.git llvmorg-10.0.1-0-gef32c611a -- ___________________________________________ 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.

4 years

Re: Post installation issues (recipients refused) with Exim4 in a virtual host environment

by Odhiambo Washington

On Wed, Oct 11, 2023 at 11:15 AM Kyriakos Terzopoulos < kyriakos.terzopoulos(a)gmail.com> wrote: > Hi, > > I have set up (I believe successfully) and configured the following in a > Virtualhost environment (with HestiaCP): > > - A record for lists.mydomain.com > - Venv > - Mailman core > - Mailman web (run migrate, collectstatic, compress, compilemessages) > Postorius > - gunicorn, hyperkitty > - Nginx > - SMTP exim4 conf > > I can see Posrorius and I have logged in and created my first mailing list: > > [image: Screenshot 2023-10-11 at 10.57.31 AM.png] > > My issue is that even though I have subscribed to my list as you can see > above, I am not receiving the confirmation email. I get a "recipients > refused" error. The smtp log for mailman is as follows: > > Oct 11 10:41:20 2023 (1533666) > <169701007904.1534165.14569329382406660776@localhost> recipients refused: > {' > kyriakos.terzopoulos(a)gmail.com': (550, b'Verification failed for > <testlist-bounces+kyriakos.terzopoulos=gmail.com(a)myproject.eu > >\nUnrouteable > address\nSender verify failed')} > > Oct 11 10:41:20 2023 (1533666) > <169701007904.1534165.14569329382406660776@localhost> smtp to > testlist(a)myproject.eu for 1 recips, completed in 0.26796579360961914 > seconds > > Oct 11 10:41:20 2023 (1533666) > <169701007904.1534165.14569329382406660776@localhost> post to > testlist(a)myproject.eu from > testlist-confirm+c9b20c5290bec43147a7e96a6b8cd825daf913d7(a)myproject.eu, > 1667 bytes, 1 failures > > Oct 11 10:41:20 2023 (1533666) > <169701007904.1534165.14569329382406660776@localhost> delivery to > kyriakos.terzopoulos(a)gmail.com failed with code 550, b'Verification failed > for <testlist-bounces+kyriakos.terzopoulos=gmail.com(a)myproject.eu > >\nUnrouteable > address\nSender verify failed' > > I have used the configuration for exim that is here > < > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… > > > and > I have also tested with the alternative approach that is documented in > What do you have in the Exim's mainlog? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 3 months

Re: Getting original message headers

by Mark Sapiro

On 1/5/26 01:32, Peter Chubb via Mailman-users wrote: > > We've been seeing some particularly pernicious spammers > recently. They're using gmail accounts; I'd like to report them to > Google. > > To do that I need to find the original message headers. By the time > the message gets to the archive, or to the mailing list recipients, > all the Received: headers seem to have been deleted, leaving only the > ones from my list server outwards. Only minimal information from headers is in the hyperkitty archive, but the headers should be in the delivered email and in the message archived by the prototype archiver if enabled (Mailman's var/archives/prototype/<list_address>/new/) For example, in the list message I'm replying to I see these headers from your server > DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; > d=chubb.wattle.id.au; s=2; h=Subject:To:From:Date:References:Reply-To; > bh=g3joi1iLtQO6etRPAxWSgcpVPoLlVQz6JOFqB1oHHfY=; b=jJEI+qHRRXm7S4bGnmZU6zaeh9 > lcPLZkay/lfqg4j9/ucMazFOyEkO3dolXuwz+mnI3CdapcNoGI0/VdZKgNCjINkq6g+Lrzfj5yPZN > o8QPyn42K6pP9A724/LPtKf/ltxymwQxBGm9DbYVx3SWLc8Dxl0e2lMdT1PlQfjHZ3pk=; > Received: from [2401:d002:1202:a00::9] (helo=wombat.chubb.wattle.id.au) > by mx3.chubb.wattle.id.au with esmtpsa (TLS1.3) tls > TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 > (Exim 4.98.2) > (envelope-from <peter(a)chubb.wattle.id.au>) > id 1vcgxA-000000015I8-1oLW > for mailman-users(a)mailman3.org; > Mon, 05 Jan 2026 20:32:45 +1100 > Received: from [192.168.77.170] (helo=gram.chubb.wattle.id.au) > by wombat.chubb.wattle.id.au with esmtpsa (TLS1.2) tls > TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 > (Exim 4.98.2) > (envelope-from <peter(a)chubb.wattle.id.au>) > id 1vcgxJ-0000000AhKz-0d8s > for mailman-users(a)mailman3.org; > Mon, 05 Jan 2026 20:32:53 +1100 I don't know why you are not seeing similar headers in your list mail. Perhaps the spammers are posting via HyperKitty. > Is there a way to access the original incoming emai, before DMARC > mitigation etc., has changed the headers? If you can arrange via list settings or header filters for the message to be held for moderation, you can see the raw held message in Postorius or in Mailman's var/messages/ directory. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 weeks, 2 days

Re: Dump/restore users (with passwords) via API

by Abhilash Raj

On Tue, Sep 18, 2018, at 9:19 AM, Dmitry Makovey wrote: > On 09/17/2018 12:39 PM, Abhilash Raj wrote: > > On Mon, Sep 17, 2018, at 12:15 PM, Dmitry Makovey wrote: > >> We are trying to dump/restore users using API calls and it seems > >> that API allows us to dump password hashes (a good thing), but then > >> API does not allow to insert users back using saved password hashes > >> - only cleartext passwords. > > > > I'd say that is intentional. You don't want people to be setting up > > hashes as passwords. > > > >> Aside from create_user is there any other way to create > >> users/change their password? > > > > Not that I know of, not using the API atleast. You could potentially > > use the low level API that inserts records in the database or use SQL > > to dump and restore that data. > > > > What do you use the Core's user/password for? Currently, the user > > passwords are basically just a carry-over from Mailman2 and there > > shouldn't be any use for it. I have been considering removing that > > completely have Postorius do all the authentication/authorization. > > > > Email based authentication should rely on more reliable identities > > like email signatures, intead of having to send cleartext passwords > > over email. > > I think I am asking about the username/password auth for postorious and > how to dump/restore it. At present we have no tools for dump/restoring > users so that's what we're trying to build. Ah, why not take a database dump? There are a few specific tables that you can dump to get everything? We don't have a way to do that because we do not actually do not handle auth ourselves, but instead delegate it to allauth library. You may have to dig into internals of that to be able to fetch/restore users/passwords. -- thanks, Abhilash Raj (maxking)

7 years, 4 months

Re: Solved Re: after last upgrade I've got a CSRF failed verification

by Guillermo Hernandez (Oldno7)

El 27/10/22 a las 21:39, Mark Sapiro escribió: > On 10/27/22 03:04, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> >> Since I made all the mailman3 enviroment wide server open (not using >> venv) I already executed the migration doing a >> >> su -m mailman3 -c "python3 manage.py collectstatic" >> su -m mailman3 -c "python3 manage.py migrate" >> >> Being mailman3 the user who runs all of mailman3 related stuff >> >> I had problems doing the migrate part, showing an error of lacking >> perms. I solved it running the migration under root (I know it could >> be trouble after, but...) > > It would be much better to identify the problem files/directories and > adjust their ownership. It is possible that running stuff as root in > the past left things owned by root causing the issue. The problem was in the intent of execute one of the migrate parts and showed about python files. I'm pretty sure that I've been very carefull not running things as root before as I know it can mess all up. But this time it was an dead end and I needed to go through. In a few days I will upgrade another server. I will document the error if I find it again. > >> >> After that the compress part showed errors... but the postorius web >> maintenance was working well except for the CSRF error verification. >> I will trace the compress errors and will try to find the problem later. > > > Do you have `COMPRESS_ENABLED = True` in your settings? If that's not > the issue, it may be in the settings for COMPRESS_PRECOMPILERS > I will try to trace it and comment what I find. Thaks a lot for your support. -- ___________________________________________ 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.

3 years, 2 months

Mailman-users search results for query "Postorius"