Search results for "Postorius" - Mailman-users

Re: [Django] ERROR (EXTERNAL IP): Service Unavailable

by Mark Sapiro

On 2/25/21 9:38 AM, dancab(a)caltech.edu wrote: > Mark, > > Is it only this list that has an issue? > > Yes, this is the only list that is having the issue. > > Can you visit other pages for this list? > > Yes, I'm able to view the members list, list settings, templates, etc. > > I've restarted the service and tried to access the held messages for the list once again. Here's what is in the mailman log. > > > ERROR 2021-02-25 17:28:14,197 393 postorius Mailman REST API not available > Traceback (most recent call last): > File "/opt/mailmanve/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 706, in urlopen > chunked=chunked, > File "/opt/mailmanve/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 445, in _make_request > six.raise_from(e, None) > File "<string>", line 3, in raise_from > File "/opt/mailmanve/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 440, in _make_request > httplib_response = conn.getresponse() > File "/usr/lib64/python3.6/http/client.py", line 1346, in getresponse > response.begin() > File "/usr/lib64/python3.6/http/client.py", line 307, in begin > version, status, reason = self._read_status() > File "/usr/lib64/python3.6/http/client.py", line 276, in _read_status > raise RemoteDisconnected("Remote end closed connection without" > http.client.RemoteDisconnected: Remote end closed connection without response This is from Django's log. What's in Mailman core's mailman.log? Since everything else is accessing the REST API with no problem, I think core must be stuck on something and timing out. Is there a time delay between trying to get the held messages view and the "Mailman REST API not available. Please start Mailman core." response? Also is there a non-zero count in the badge on the Held messages tab? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

Re: Speed up importing mailman2 lists

by Stephen J. Turnbull

Mark Sapiro writes: > On 2/19/25 06:08, t.maintz(a)fz-juelich.de wrote: > > We are currently planning to migrate from mailman2 to mailman3 as > > a container, have around 1500 lists and would like to complete > > the migration ideally in a few hours. I've done two massive migrations in the last year. In the first (~20k lists), the lists were down for maybe two hours, but it took 22 hours for HyperKitty to populate, mostly in Xapian indexing we realized in post-mortem analysis. In the second (~1k lists), no perceptible downtime because they have their own bespoke archiver that has a list-manager-agnostic API. The trick to zero delivery downtime is that you can configure your MTA to route to Mailman 3 if the list exists there, if not route to Mailman 2 if the list exists there, and if not continue to any lower priority routes. It worked as designed (mops sweat off brow ;-). We did take Postorius and the Mailman 2 management CGIs and email command addresses offline for the duration (3 hours in the first case, 30 mminutes in the second). This is sraightforward if Mailman 2 and Mailman 3 are running on the same host. Life is more complex if you're spinning up Mailman 3 in a separate node but it should be possible. I think if you're migrating to HyperKitty you can speed up the migration by shutting off indexing, and doing that later at the cost of confusing people who expect the lists to be indexed. I'm not sure if it's possible to migrate the archives concurrently with accepting new posts, or maybe to migrate archives in advance and backfill any posts that arrive during the list migration. And there's no reason why you can't leave the legacy Mailman 2 archives up for browsing as a backup for as long as needed. Steve

1 year, 8 months

Re: Change base mailman URL path

by Mark Sapiro

On 4/6/23 20:07, chad.hays86(a)gmail.com wrote: > Hi, I recently completed the a Mailman3 install using these[1] instructions. I'm able to access the web interface, the Django admin app, etc off the root domain URL. For example: https://mydomain.org/mailman3, https://mydomain.org/admin, https://mydomain.org/archives > > What's the most straightforward way to put all of these URL paths behind a different context? For example: https://mydomain.org/lists/mailman3, https://mydomain.org/lists/admin, https://mydomain.org/lists/archives > > I'm running Apache2 as my web server and am using mod_proxy to proxy requests to uwsgi. There are two pieces to this: For the Django side, copy /opt/mailman/venv/lib/python3.x/site-packages/mailman_web/urls.py to /etc/mailman3/urls.py where python3.x is the python version in your venv and edit that file as in ``` 30,34c30,34 < path('mailman3/', include('postorius.urls')), < path('archives/', include('hyperkitty.urls')), < path('', include('django_mailman3.urls')), < path('accounts/', include('allauth.urls')), < path('admin/', admin.site.urls), --- > path('lists/mailman3/', include('postorius.urls')), > path('lists/archives/', include('hyperkitty.urls')), > path('lists/', include('django_mailman3.urls')), > path('lists/accounts/', include('allauth.urls')), > path('lists/admin/', admin.site.urls), ``` and add the following to /etc/mailman3/settings.py ROOT_URLCONF = 'urls' Then for the apache side, it depends what you have for your ProxyPass directives are. If you have several like ``` ProxyPass "/mailman3" "http://127.0.0.1:8000/mailman3" ProxyPass "/archives" "http://127.0.0.1:8000/archives" ... ``` change those to ``` ProxyPass "/lists/mailman3" "http://127.0.0.1:8000/lists/mailman3" ProxyPass "/lists/archives" "http://127.0.0.1:8000/lists/archives" ``` If you have just one like ``` ProxyPass "/" "http://127.0.0.1:8000/" ``` change it to ``` ProxyPass "/lists" "http://127.0.0.1:8000/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, 7 months

Re: Issue with Held Messages

by Mark Sapiro

On 08/19/2016 10:39 PM, Jean-Luc Wasmer wrote: > On 2016-08-19 17:58, Mark Sapiro wrote: >> On 08/17/2016 09:17 PM, Jean-Luc Wasmer wrote: >>> >>> No matter what action I set for member posts (Hold for moderator, >>> Reject) they are always delivered. >> >> >> I don't know why this would be. Perhaps the member's moderation is set >> to Accept immediately - you can see this on ther member's options page >> in Postorius when logged in as a list owner. > > Apart from "Mode of Delivery" that is set to "Regular" for the user, > none of the following attributes are set: > > Mail Delivery > Receive own posts to the list > Receive acknowledgement mails > Conceal address from the subscriber list > Avoid duplicate copies of messages If you look at the user's options when logged in as a list owner, you should see an additional "Administration options" section below those with a "Moderation" setting. What is that set to? ... > By the way, I didn't mention before but in Settings | Message > Acceptance, the "Acceptable aliases:" box contains "[]". When I try to > Save changes after modifying something, I gut "An error occured: []" in > the yellow banner (instead of "The settings have been updated."). What happens if you clear the Acceptable aliases box before saving? ... >> This is apparently <https://gitlab.com/mailman/mailmanclient/issues/10> >> fixed by <https://gitlab.com/mailman/mailmanclient/merge_requests/16> > > Any ETA when this will be pushed to "mailman-bundler"? I expect bundler will be updated when 3.1 is released and that should be soon. You may find <https://wiki.list.org/x/17891998> of interest. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 years, 2 months

Database deadlock when trying to delete a member.

by Simon Coggins

Hi, I’ve got a strange error. I migrated from mailman 2.1 to 3 using the migration guide on the website and things have been working fine. But I’m in the process of testing the new syncmembers command to replace some inhouse mailman API code we wrote. I’ve tracked my problem down to what appears to be a deadlock in the postgresql database. When trying to delete certain users the SQL query hangs and never returns. After doing some tracing and tracking it down to the database, I enabled DB logging of all queries and saw that the following query was never returning: DELETE FROM member WHERE member.id = 166814 If I try to run it manually I get the same issue, in psql it never returns. mailman=# explain analyze DELETE FROM member WHERE member.id = 166814; [… 60 seconds passes…] ^CCancel request sent ERROR: canceling statement due to user request CONTEXT: while deleting tuple (2998,72) in relation "member" I’m just wondering if there are any commands or scripts I can run to verify the database and it’s constraints to see if there is some error in the database data? Or where you’d recommend I go from here? It only impacts the user on this specific list. If I add this user to another list and remove them, everything works fine. This is on a test system so I can do various testing. I’m trying to find the root cause so that I can verify my production system isn’t impacted by the same thing. Setup Details: OS: Oracle Linux 7 (Redhat) Installed using pip via virtualenv talking to a local pgsql database on the same box. Data was migrated from a mailman 2.1 install into mailman3 using migration instructions on the website. PIP Modules versions: django-mailman3 1.3.5 mailman 3.3.3 mailman-hyperkitty 1.1.0 mailmanclient 3.3.2 postorius 1.3.4 psycopg2-binary 2.8.5 RPM packages: postgresql12-12.6-1PGDG.rhel7.x86_64 postgresql12-server-12.6-1PGDG.rhel7.x86_64 postgresql12-libs-12.6-1PGDG.rhel7.x86_64 postgresql12-devel-12.6-1PGDG.rhel7.x86_64 -Simon

5 years, 7 months

Re: Newbie question 2: Rewriting issue for bounced emails

by William Oliver

On Sun, 2021-12-26 at 16:47 -0800, Mark Sapiro wrote: > On 12/26/21 3:06 PM, William Oliver wrote: > > > > When running mailman3, do I need to set up a completely different > > virtual domain for it to run in? > > No. > > > > My "real" domain name is > > libertyfp.org, and I'm trying to make mailman work on that domain, > > e.g. > > "testlist(a)libertyfp.org." I'm starting to get the idea that I need > > to > > stick a completely different domain in there for the mailinglist. > > No. > > DNS or anywhere outside your server. > > Have you actually set an alias domain in Postorius for the > libertyfp.org > domain. It doesn't matter what name it is as long as it isn't > a real domain. A good choice is x.libertyfp.org. Have you set that > or > things like > > testlist(a)libertyfp.org testlist(a)x.libertyfp.org > testlist-bounces(a)libertyfp.org testlist-bounces(a)x.libertyfp.org > testlist-confirm(a)libertyfp.org testlist-confirm(a)x.libertyfp.org > ... [snip] Ah. I misunderstood you. I thought you meant that I had to tweak *postfix* to get this done. It's not that you weren't clear, it's that when I read the mailman3 instructions, I got the impression that *mailman* would set the alias domain automatically, so I was dead set on munging postfix. This makes more sense, and I can back out of some of the changes I made in postfix, which for the last couple of rounds was mostly flailing about randomly -- I've heard that's often not a good admin strategy. So.. if I need to do it myself, can you point me to what file I need to create/modify in the /opt/mailman/mm tree to set up the alias? Thanks! billo

4 years, 10 months

Re: spanish localization

by Victoriano Giralt

El sáb, 13-02-2021 a las 16:44 -0800, Mark Sapiro escribió: > On 2/13/21 4:08 PM, Victoriano Giralt wrote: > > Mark, please, how do you check when translations happened? Nov 7th is a > > very significant date for me (it is my wedding anniversary) and I'm 90% > > sure that I dedicated time to Weblate after that date... > > With respect to Mailman core, all I'm doing is downloading the .po for > Spanish and comparing it to mailman/messages/es/LC_MESSAGES/mailman.po > from the Mailman core 3.3.3 package on PyPI and they are identical. > > If there are translated strings on weblate that are different from that, > they don't show up in the downloaded > <https://hosted.weblate.org/download/gnu-mailman/mailman/es/>;. And you are very right and I have fallen as a newbee ... and first of all I apologise for the noise. I've been doing diffs with files downloaded from Weblate and those installed on the server by pip. As I should have done from the start. Mailman core and hyperkitty show no differences. Postorius shows a bunch and django_mailman3 just a couple. I leave for others a more detailed check of the strings between downloaded .po files and Weblate online strings, it's too late here. > > And I too want to help. It would be a help to me if you can give me > examples of specific strings whose weblate translation differs from > what's in the distributed .po files. And you have helped me, making me thing twice and stop moaning and going for the facts. Apologetic-thankful-big-mouth-shut-ly, Victoriano. -- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

5 years, 8 months

Re: Localization of auto-responses, question marks in welcome message

by Stephen J. Turnbull

Claus-Justus Heine via Mailman-users writes: > Kind thanks for the response. I have to apologize: my "test user" had > its preferred language set to en_US, so that was the reason for the > question marks. So this was indeed a user-error (i.e. my fault). But we'd like to have that user get the English version of the message. One of two things seems reasonable: 1. You have customized the German template, but not the English template. In that case, I think it makes sense for Mailman to assume the German template has important information that the English does not, and send the German template with its appropriate encoding (UTF-8, nowadays). The fact that en_US can be encoded in ASCII should not affect the encoding of the de template, ever.[1] 2. You have not customized the German template. In that case the user should get the default English template. How do those sound to you, as goals for Mailman behavoir? So ISTM this is a Mailman issue, if Mailman is sending out the German message with question marks substituted for non-ASCII characters, or if Mailman is sending out the German message with US-ASCII as the Content-Type charset parameter. The only way I can see this as a user (admin) issue is if you overwrote the English template with German (and even then, it's nuts for Mailman not to use UTF-8 for English what with directed quotes, emoji, and all the other enhancements to the character repertoire that US English speakers use). Can you tell me a little more about whether you configured any custom templates, and if so, how? That is, did you use the Postorius text field or overwrite files directly? Steve Footnotes: [1] Note to self: perhaps the admin UI can check the list of supported languages and warn if some but not all are customized.

4 years, 6 months

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

by Abhilash Raj

On Thu, Sep 5, 2019, at 1:49 PM, Ugnius wrote: > > 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. I think your problem about locked database might be solved. Like I mentioned, it is possible that those two running server could be stepping over each other toes. After removing the "runserver" process, I think you shouldn't fall into anymore of those locking issues. FWIW, it is also highly recommended to not use sqlite for any production use cases. Either postgres or mysql is preferred. > 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) >> >> -- thanks, Abhilash Raj (maxking)

7 years, 2 months

Race condition when mass subscribing same email addresses to two lists?

by Alan So

We are testing the latest Mailman core 3.3.5 and Postorius 1.3.6. My colleagues reported that some email addresses cannot subscribe to the lists when two of them are using mass subscribe feature to add email addresses to the list. Then I try whether I can repeat the same issue. I did this: 1) Create two lists with default setting 2) Prepare a list of 1000 fresh email addresses not added to the system before 3) Mass subscribe both lists of these 1000 email addresses around the same time with all three Pre (confirm, approved, verified) checked There are quite a lot of similar errors in mailman.log. Did not study the code yet. Which part is causing the issue? SQLAlchemy 1.3.24 psycopg2-binary 2.8.6 [2021-10-28 08:38:30 +0000] [20141] [ERROR] Error handling request /3.1/members Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.6/site-packages/gunicorn/workers/sync.py", line 136, in handle self.handle_request(listener, req, client, addr) File "/opt/mailman/venv/lib/python3.6/site-packages/gunicorn/workers/sync.py", line 179, in handle_request respiter = self.wsgi(environ, resp.start_response) File "/opt/mailman/venv/lib/python3.6/site-packages/mailman/database/transaction.py", line 51, in wrapper config.db.commit() File "/opt/mailman/venv/lib/python3.6/site-packages/mailman/database/base.py", line 52, in commit self.store.commit() File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/session.py", line 1046, in commit self.transaction.commit() File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/session.py", line 502, in commit self._assert_active(prepared_ok=True) File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/session.py", line 296, in _assert_active code="7s2a", sqlalchemy.exc.InvalidRequestError: This Session's transaction has been rolled back due to a previous exception during flush. To begin a new transaction with this Session, first issue Session.rollback(). Original exception was: (raised as a result of Query-invoked autoflush; consider using a session.no_autoflush block if this flush is occurring prematurely) (psycopg2.errors.UniqueViolation) duplicate key value violates unique constraint "ix_address_email" DETAIL: Key (email)=(testemail999(a)example.com) already exists.

5 years

Mailman-users search results for query "Postorius"