Search results for "Postorius" - Mailman-users

(venv) mailman-web migrate (as explained) fails with "django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE"

by Stephen J. Turnbull

Wikinaut writes: > I followed all single steps until this: > https://docs.list.org/en/latest/install/virtualenv.html#run-database-migrat… > (I will improve the documentation with the missing parts later > today), > > Now I got this and got stucked and need your help: > django.core.exceptions.ImproperlyConfigured: > allauth.account.middleware.AccountMiddleware must be added to > settings.MIDDLEWARE If you use the mailman-web setup, the allauth, allauth.account, and allauth.socialaccount applications are present in the initial INSTALLED_APPS tuple in the settings package. The example_projects in Postorius and HyperKitty each provide a very similar settings.py but with more extensive provision of socialauth providers. I strongly recommend you use the mailman-web settings package as a template for your own. Regarding the PostgreSQL bias, PostgreSQL is just more Mailman-friendly. We'll be happy to add more MySQL documentation, but I don't think any of the core devs use it where they have to make a choice. (For example I myself use MySQL only in my MediaWiki instance and I have done zero configuration of it.) There is at least one known gotcha for default installations of MySQL (it's terribly ungraceful when there are non-BMP UTF-8 characters), but any other warts or optimizations would be very welcome. Steve

3 years

Re: 3rd Party Account is not working

by Matthew Alberti

Same thing happens to me. If I comment out all the socialauth plugins, the web service doesnt work. Are you using the docker-mailman installation method? ⁣Get BlueMail for Android On Feb 16, 2021, 7:32 PM, at 7:32 PM, kwp.klein(a)gmail.com wrote: >Here is my /mailamn/config/mailman-web/settings_local.py. I get an >error message > >curl http://172.19.199.3:8000/postorius/lists/ >curl: (7) Failed connect to 172.19.199.3:8000; No route to host >Please comment out all the lines that are not necessary. > > >MAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' >EMAIL_HOST = '172.19.199.1' >EMAIL_PORT = 25 >USE_SSL = False > >INSTALLED_APPS = ( > 'hyperkitty', > 'postorius', > 'django_mailman3', > # Uncomment the next line to enable the admin: > 'django.contrib.admin', > # Uncomment the next line to enable admin documentation: > # 'django.contrib.admindocs', > 'django.contrib.auth', > 'django.contrib.contenttypes', > 'django.contrib.sessions', > 'django.contrib.sites', > 'django.contrib.messages', > 'django.contrib.staticfiles', > 'rest_framework', > 'django_gravatar', > 'paintstore', > 'compressor', > 'haystack', > 'django_extensions', > 'django_q', > 'allauth', > 'allauth.account', > 'allauth.socialaccount', > #'django_mailman3.lib.auth.fedora', > #'allauth.socialaccount.providers.openid', > #'allauth.socialaccount.providers.github', > #'allauth.socialaccount.providers.gitlab', > #'allauth.socialaccount.providers.google', >) >_______________________________________________ >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/

5 years, 8 months

Re: Bounce processing HTML

by Mark Sapiro

On 11/25/25 8:51 AM, pashdown(a)xmission.com wrote: > Where do I set forward_unrecognized_bounces_to ? I can't find documentation on this. If you have Postorius it's Settings -> Bounce Processing -> Forward unrecognized bounces. It is a list attribute with 3 possible values which are discard them, forward to list owners/moderators or forward to the site admin. The default value when lists are created is forward to list owners/moderators. However none of this is relevant to your situation because the bounces you are getting that result in the Bounce message for a non subscriber log messages you are seeing are not unrecognized. As I said at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… I think these are spam sent to the list-bounces address that one of the heuristic recognizers treats as a real DSN and parses those non-addresses. In order to see the actual messages, you will have to configure your MTA to deliver them to a human or you could apply this patch ``` --- a/src/mailman/runners/bounce.py +++ b/src/mailman/runners/bounce.py @@ -49,6 +49,7 @@ class BounceRunner(Runner): # List isn't doing bounce processing? if not mlist.process_bounces: return False + maybe_forward(mlist, msg) # Try VERP detection first, since it's quick and easy context = BounceContext.normal addresses = StandardVERP().get_verp(mlist, msg) ``` to copy all bounce messages to the forward_unrecognized_bounces_to destination. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 2 weeks

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

by Ugnius

Thank You. This is very valuable information. According documentation I understood that "runserver" should run on some internal port and uwsgi just works like proxy connects to the same as runserver port and serves content to apachi. Because when I was playing with the setup without "runserver" Web interface didn't work. Yes, I have stopped "runserver" and page still works fine. :) This didn't solve me database RO issue, but this information was important. Thank You. I am thinking what to do now... Maybe to recreate database (make initiation once again). It could take 2-3 hours. I did not noticed option to export/import lists setting. Or to try find solution how to make sqlite3 multiple writable. SQLite version 3.16.2 2017-01-06 16:32:41 Enter ".help" for usage hints. BR Ugnius > On 5 Sep 2019, at 23:31, Abhilash Raj <maxking(a)asynchronous.in> wrote: > >> On Thu, Sep 5, 2019, at 1:15 PM, Ugnius wrote: >> >> I do not know... In the setup example settings was something like process number = 2. But I understand at least 1 uwsgi and 1 run server should run? > > No, only uwsgi needs to run. It is fine if there are two of those, since it probably forks to have 2 worker process. There shouldn't be any "python manage.py runserver" processes running at all, it is meant only for testing purposes. > > The doc mentions that it is "development" server[1][2]. > > [1]: # Run the Django's "development" server at localhost:8000 > [2]: http://docs.mailman3.org/en/latest/prodsetup.html#setting-up-django-project > > Perhaps it should be more descriptive about what does it mean. > >> >>> On 5 Sep 2019, at 23:08, Abhilash Raj <maxking(a)asynchronous.in> wrote: >>> 6644 ? S 0:12 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>> 6645 ? S 0:00 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>> 6653 ? Sl 636:28 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>> 6656 ? Sl 0:27 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>> >>> This fishy, why do you have both uwsgi and "python manage.py runserver" running? >>> >>> You only need one of those, since they both do the exact same thing. Please remove >>> whatever is running the "python manage.py runserver" part and only use uwsgi. >>> >>>> On Thu, Sep 5, 2019, at 1:02 PM, Ugnius S wrote: >>>> Thank You, Abhilash, to helping. I have checked the processes, but also I have read, that sqlite3 can run in multi writing mode. >>>> May mailman processes are next: >>>> >>>> 6644 ? S 0:12 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>>> 6645 ? S 0:00 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>>> 6653 ? Sl 636:28 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>>> 6656 ? Sl 0:27 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>>> 6643 ? S 0:00 /usr/bin/python3 /usr/bin/master -C /opt/home/mailman.cfg >>>> 659 ? S 0:46 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=in:0:1 >>>> 6660 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=nntp:0:1 >>>> 6661 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=digest:0:1 >>>> 6662 ? S 0:48 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=pipeline:0:1 >>>> 6663 ? S 0:44 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=archive:0:1 >>>> 6664 ? S 0:41 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=command:0:1 >>>> 6665 ? S 0:01 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=retry:0:1 >>>> 6666 ? S 0:45 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=virgin:0:1 >>>> 6667 ? Sl 0:16 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=lmtp:0:1 >>>> 6668 ? Sl 1:30 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=rest:0:1 >>>> 6669 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=bounces:0:1 >>>> 6670 ? S 0:49 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=out:0:1 >>>> >>>> Looks like there are no double. Nothing more is running. >>>> >>>> 2019-09-05, kt, 03:16 Abhilash Raj <maxking(a)asynchronous.in> rašė: >>>> >>>>> On Wed, Sep 4, 2019, at 2:05 PM, Ugnius S wrote: >>>>> >>>>> I have installed using documentation. My linux distribution version has no full package available. I have installed step by step: >>>>> $ sudo pip3 install mailman >>>>> $ sudo pip3 install postorius >>>>> $ sudo pip3 install hyperkitty >>>>> $ sudo pip3 install mailman-hyperkitty >>>>> And of course all mandatory components... Everything without errors, I can drop db files and I can download mailman-suite again and start from empty page again. But it will not guarantee that DB will not become READ ONLY again. Here should be logic. No developing support here? >>>> >>>> Could you be running two separate processes such that the database is locked by one and so other finds it as READ Only? When you find a read only database, can you check if it is open in some other process? >>>> >>>>> >>>>> >>>>> >>>>> 2019-09-03, an, 19:36 Abhilash Raj <maxking(a)asynchronous.in> rašė: >>>>> >>>>> >>>>> On Sun, Sep 1, 2019, at 3:22 AM,ugniusviln(a)gmail.com wrote: >>>>> > Hi. All the project installation is under the same user / path and >>>>> > it works. Archiving working as well, (just one remark: no matter what >>>>> > to set in postorius, hyperkitty shows list as public) >>>>> > I have found work around - it is possible to change list as private in >>>>> > "admin" page. >>>>> > I started to get issues with runjobs after I have created couple of >>>>> > new lists with "no archive" option. >>>>> >>>>> How did you install all these components. It seems there the installation is broken in weird ways. >>>>> >>>>> > >>>>> > If as owner user from project home I run: >>>>> > >>>>> > django-admin mailman_sync >>>>> > >>>>> > Traceback (most recent call last): >>>>> > File >>>>> > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/utils.py", >>>>> > line 84, in _execute >>>>> > return self.cursor.execute(sql, params) >>>>> > File >>>>> > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/sqlite3/base.py", >>>>> > line 383, in execute >>>>> > return Database.Cursor.execute(self, query, params) >>>>> > sqlite3.OperationalError: attempt to write a readonly database >>>>> > >>>>> > "django-admin runjob sync_mailman " - makes read only errors as well. >>>>> > "django-admin runjob new_lists_from_mailman" >>>>> > django.db.utils.OperationalError: attempt to write a readonly database >>>>> > END TRACEBACK >>>>> > >>>>> > I did not find information how to fix this. It was worked without errors >>>>> > before. >>>>> > I noticed, that if I stop mailman, "django-admin mailman_sync" starts >>>>> > to work. >>>>> > If I start "mailman start", then "django-admin mailman_sync" failing >>>>> > again. >>>>> > I did not check other jobs, but I think what is related to database, >>>>> > will get errors. >>>>> > Seems mailman locking the database. It is not a file permissions issue. >>>>> > Mailman db location is: /project_directory/var/data/mailman.db >>>>> > >>>>> > if to rename /project_directory/var/data/mailman.db to something, >>>>> > mailman creates database file size 0, django-admin runjobs start >>>>> > working, but of course postorius stops working. I did it for testing. >>>>> > I have returned this database file back, postorius started to work >>>>> > again, but django-admin runjobs does not work, error: "database read >>>>> > only". >>>>> > Please help me how to fix this issue. >>>>> > _______________________________________________ >>>>> > Mailman-users mailing list -- mailman-users(a)mailman3.org >>>>> > To unsubscribe send an email to mailman-users-leave(a)mailman3.org >>>>> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >>>>> > >>>>> >>>>> -- >>>>> thanks, >>>>> Abhilash Raj (maxking) >>>> >>>> -- >>>> thanks, >>>> Abhilash Raj (maxking) >>>> >>>> >>> >>> -- >>> thanks, >>> Abhilash Raj (maxking) >>> >>> > > -- > thanks, > Abhilash Raj (maxking) > >

7 years, 2 months

Domain ownership issues

by peter＠chubb.wattle.id.au

Hi, I wanted to give another user the ability to create lists, so added that user as 'owner' of the domain. But he does not see the 'create list' button. I decided to try deleting him as owner, and the result is a python exception: KeyError: 'file' ERROR 2021-03-01 20:35:07,195 550 django.request Internal Server Error: /postori us/domains/sel4.systems/owners/b55d58c434c94f6dbd19ae338502dd2e/remove Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/decorators/http.py", line 40 , in inner return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django/contrib/auth/decorators.py", line 21, in _wrapped_view return view_func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/postorius/auth/decorators.py", line 75, i n wrapper return fn(*args, **kwargs) File "/usr/lib/python3/dist-packages/postorius/views/domain.py", line 182, in remove_owners remove_email = client.get_user(user_id).addresses[0].email File "/usr/lib/python3/dist-packages/mailmanclient/client.py", line 324, in get_user display_name=display_name)) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 111, in call raise HTTPError(url, response.status_code, urllib.error.HTTPError: HTTP Error 404: 404 Not Found Mailman Core Version GNU Mailman 3.2.2 (La Villa Strangiato) Mailman Core API Version 3.0 Mailman Core Python Version 3.9.0+ (default, Oct 19 2020, 09:51:18) [GCC 10.2.0] Peter C

5 years, 8 months

Re: changing the main template for subscriptions and more

by Andreas Barth

* Jens Günther (jens.guenther(a)posteo.de) [210621 17:05]: > Hey there, > > in Mailman2 there was a simple link in the moderation-emails, with > which I was able to open directly the "held-messages". I know how to > manually integrate such a link with the variables of mailman (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) > But: > > How can I change the template for all the lists (respectively > maildomains/webdomains) so that I don't have to do this manually for > all lists? I searched a bit for the corresponding template, but > didn't find it. At the end it only says the following: I'm using this patch (however, german-only) Andi diff --git a/src/mailman/templates/de/list:admin:action:post.txt b/src/mailman/templates/de/list:admin:action:post.txt index bc76a54c4..85cdd9376 100644 --- a/src/mailman/templates/de/list:admin:action:post.txt +++ b/src/mailman/templates/de/list:admin:action:post.txt @@ -9,5 +9,6 @@ Die Nachricht wurde aus folgenden Gründen zurückgehalten: $reasons -Besuchen Sie die Administrations-Seiten, um die Nachricht +Besuchen Sie die Administrations-Seiten, um die Nachricht anzunehmen oder abzulehnen. +https://$domain/mailman3/postorius/lists/$list_id/held_messages diff --git a/src/mailman/templates/de/list:admin:action:subscribe.txt b/src/mailman/templates/de/list:admin:action:subscribe.txt index 88427c8d0..ba77aa3ce 100644 --- a/src/mailman/templates/de/list:admin:action:subscribe.txt +++ b/src/mailman/templates/de/list:admin:action:subscribe.txt @@ -3,3 +3,7 @@ die Mailingliste nötig: Für: $member Liste: $listname + +Besuchen Sie die Administrations-Seiten, um die Anmeldung +anzunehmen oder abzulehnen. +https://$domain/mailman3/postorius/lists/$list_id/subscription_requests diff --git a/src/mailman/templates/de/list:admin:action:unsubscribe.txt b/src/mailman/templates/de/list:admin:action:unsubscribe.txt index c794355e8..0bace3950 100644 --- a/src/mailman/templates/de/list:admin:action:unsubscribe.txt +++ b/src/mailman/templates/de/list:admin:action:unsubscribe.txt @@ -3,3 +3,7 @@ der Mailingliste nötig: Für: $member Liste: $listname + +Besuchen Sie die Administrations-Seiten, um die Abmeldung +anzunehmen oder abzulehnen. +https://$domain/mailman3/postorius/lists/$list_id/subscription_requests diff --git a/src/mailman/templates/de/list:user:notice:welcome.txt b/src/mailman/templates/de/list:user:notice:welcome.txt index 3efc32bd1..974d8e465 100644 --- a/src/mailman/templates/de/list:user:notice:welcome.txt +++ b/src/mailman/templates/de/list:user:notice:welcome.txt @@ -1,16 +1,18 @@ Willkommen auf der Mailingliste "$display_name"! -Um an diese Liste zu schreiben, senden Sie eine E-Mail an: - +E-Mails an die Adresse $listname +werden an alle Teilnehmer verteilt. -Sie können Einstellungen vornehmen, indem Sie eine E-Mail an +Auf der Webseite https://$domain/ können Sie Ihre Einstellungen verwalten. +Wer dies möchte, kann sich dort registrieren - bitte mit der E-Mail-Adresse, +die auf der Mailingliste eingetragen ist. Nach dem Einloggen ist auch +möglich, die Empfangsadresse für die Mailinglisten zu ändern, oder +zusätzliche Sendeadressen einzurichten. +Sie können auch Einstellungen vornehmen, indem Sie eine E-Mail an $request_email - mit dem Wort 'help' (ohne Anführungszeichen) im Betreff oder im Inhalt -senden, Sie erhalten dann eine automatisierte Antwort mit weiteren -Instruktionen. Sie werden Ihr Passwort benötigen, um Änderungen an Ihren -Einstellungen vorzunehmen, aber aus Sicherheitsgründen wird dieses hier -nicht angegeben. Sollten Sie Ihr Passwort vergessen haben, nutzen Sie bitte -die 'Passwort vergessen'-Funktion auf der Login-Seite. +senden. Sie erhalten dann eine automatisierte Antwort mit weiteren +Instruktionen. Um Änderungen bei den Einstellungen vorzunehmen, wird das auf +https://$domain/ vereinbarte Passwort benötigt.

5 years, 4 months

Upgrading mailman 3 venv installation

by Morris Jones

Congratulations on the new release for Mailman 3 Core! I'm not a daily pip/python user, so I'm probably behind on the safe and proper way to update my installation (which is working pretty well). In my virtual environment, I ran `pip list -o` and got a significant list. I noticed that all of the mailman packages seemed to be "Type sdist" and the framework packages "Type wheel". (Dunno what "Type" means in this context.) So I tried `pip list -o | grep sdist` and got a smaller list: (venv) mailman@mail:~$ pip list -o | grep sdist atpublic 2.1.1 2.3 sdist django-allauth 0.43.0 0.45.0 sdist django-mailman3 1.3.4 1.3.7 sdist flufl.i18n 3.1.3 3.2 sdist flufl.lock 5.0.3 6.0 sdist HyperKitty 1.3.3 1.3.4 sdist lazr.config 2.2.2 2.2.3 sdist mailman 3.3.2 3.3.5 sdist mailmanclient 3.3.1 3.3.3 sdist mysqlclient 2.0.1 2.0.3 sdist postorius 1.3.3 1.3.6 sdist Is this a reasonable list of the packages that I should update? Are there framework updates I should be concerned with? I'm remembering that a specific non-current version of django was required for mailman. The one I have installed is 3.0.11, with 3.2.7 listed as Latest. My plan is to archive the virtualenv directory, upgrade the packages listed above. If something breaks, I should be able to restore the archived virtualenv. I'm running a single server, Ubuntu 18.04.6, with Zimbra running alongside. Best regards, Mojo -- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>

5 years, 1 month

Re: Error Logging - what changed with the New Year releases?

by Odhiambo Washington

On Sat, Jan 14, 2023 at 7:13 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/14/23 01:19, Odhiambo Washington wrote: > > Apart from all the defaults in settings.py (derived from gitlab), I also > > have this line: > > LOGGING['handlers']['file']['filename'] = > > '/opt/mailman/mm/var/logs/mailmanweb.log' > > > > Before the New Year releases of MM3, I used to get errors written to this > > file. > > Not anymore after I updated to the New Year releases. > > Another thing that I have realized is that prior to the New Year > releases, > > I would get an error logged to that file and also mailed to me. > > I don't think that I have changed anything in settings,py related to > > logging. > > > Nothing in those releases per se would affect this. This is Django and > django-allauth. Perhaps when you updated the Mailman packages, you also > updated these dependencies. > Which dependencies would those be? When I upgraded, the command I ran was: pip install --upgrade --force mailman mailmanclient postorius hyperkitty mailman-hyperkitty django-mailman3 And how do I find out what is suppressing the logging for the social accounts? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 9 months

Re: Importing config and archives only partially succeeded?

by Eric Broens

The settings - Archiving, are not different from the ones that do show the messages:"Private Archives" selected, and Active archivers "hyperkitty" also selected. I was trying to find out how the hyperkitty page gets the mails from the database, and if I can start from there.Or maybe something is not completely correct in the database tables. Best Regards,Eric On Sunday, December 13, 2020, 01:27:53 AM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 12/12/20 3:56 PM, Eric Broens via Mailman-users wrote: > After everything was imported, and I noticed that the mails were not shown in the archives for half of the mailinglists, I ran "manage.py update_index" to index the mails for all mailinglists.This command is still running for hours.Since it builds the search index, I don't expect that this would make the mails available on the webpage. I agree, that won't make the mails available on the webpage. If you're using the default Whoosh search engine, "hours" is not unexpected. Elasticsearch is much faster and Xapian faster still. What do you see in Postorius - Settings -> Archiving for the lists whose messages don't show? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years, 10 months

Re: About to Install MM3 -- Seeking clarification

by Mark Sapiro

On 1/2/23 03:54, Onyeibo Oku wrote: > > I pulled the plugs on uwsgi and installed Gunicorn. Gunicorn gave more > mileage but something is still not right. When I visit the mailmanweb > home with a browser, I see the following: > > "Server Error. An error occurred while processing your request." > > Mailmanweb and mailman3 services are running. I perused the log file > at /opt/mailman/web/logs/mailmanweb.log and found the following: > > > raise MailmanConnectionError( > mailmanclient.restbase.connection.MailmanConnectionError: ('Could not > connect to Mailman API: ', > 'ConnectionError(MaxRetryError("HTTPConnectionPool(host=\'localhost\', > port=8001): Max retries exceeded with url: > /3.1/lists?advertised=true&count=0&page=1 (Caused by > NewConnectionError(\'<urllib3.connection.HTTPConnection object at > 0x7f7f4b128c40>: Failed to establish a new connection: [Errno 111] > 0x7f7f4b128c40>Connection refused\'))"))') Postorius is unable to connect to Mailman core's REST API. Are your settings for accessing Mailman's REST API correct? E.g., does MAILMAN_REST_API_URL = 'http://localhost:8001' MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = 'restpass' match $ mailman info ... REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass Note the 3.1/ in REST root url is not included in MAILMAN_REST_API_URL. What do you get from, e.g. curl -urestadmin:restpass http://localhost:8001/3.1/lists It should return JSON with information about your lists. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

Mailman-users search results for query "Postorius"