Search results for "2021" - Mailman-users

Re: [EXTERNAL] Re: Database deadlock when trying to delete a member.

by Simon Coggins

Ok after bit tracking I’ve worked out that the bouncer is dangling transactions when it’s sending warning messages. When https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py… is called and it get to update last_warn_sent it does the following in the DB: 2021-03-23 14:42:50.622 AEST [11693] LOG: statement: UPDATE member SET last_warning_sent='2021-03-23T04:42:50.622015'::timestamp, total_warnings_sent=1 WHERE member.id = 169331 But it never COMMITs this transaction. So all write operations are now hung waiting for the transction to be closed as the member record has been modified. As a test I added config.db.commit() after https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py… and restarted. And my mailman syncmembers worked perfectly and I didn’t have any hangs it correctly removed everyone it should have. In the database logs I can see the COMMIT. I’m pretty sure this is not the right spot for a config.db.commit() but hopefully this helps point to what might be going wrong. -Simon --- [signature_201226327]<https://www.cqu.edu.au/> Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.13, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M 0408 115 861 | E s.coggins(a)cqu.edu.au<mailto:.coggins@cqu.edu.au> [cquconnect]<https://www.cqu.edu.au/social-media> I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 From: Simon Coggins <s.coggins(a)cqu.edu.au> Date: Tuesday, 23 March 2021 at 11:01 am To: Abhilash Raj <maxking(a)asynchronous.in> Cc: "mailman-users(a)mailman3.org" <mailman-users(a)mailman3.org> Subject: Re: [EXTERNAL] Re: [MM3-users] Database deadlock when trying to delete a member. You are correct it’s the bounce runner locking the tables. If I kill -15 the bounce runner, the session lock releases and my sync continues correctly. ├─python3,60157 /opt/mailman/venv/bin/runner -C /etc/mailman.cfg --runner=bounces:0:1 So something in the bounce runner is not closing transactions correctly from the looks of it. -Simon --- [signature_201226327]<https://www.cqu.edu.au/> Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.13, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M 0408 115 861 | E s.coggins(a)cqu.edu.au<mailto:.coggins@cqu.edu.au> [cquconnect]<https://www.cqu.edu.au/social-media> I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 From: Abhilash Raj <maxking(a)asynchronous.in> Date: Friday, 19 March 2021 at 4:58 pm To: Simon Coggins <s.coggins(a)cqu.edu.au> Cc: "mailman-users(a)mailman3.org" <mailman-users(a)mailman3.org> Subject: [EXTERNAL] Re: [MM3-users] Database deadlock when trying to delete a member. This is an external email from: maxking(a)asynchronous.in This is helpful. The two pending queries looks like the job of bounce runner. Since it runs every 2m to check if any Member’s bounce score is above the threshold and if any warning needs to be sent or delivery needs to be disabled. It looks to me that the database query has been running for 1min 58sec, which is longer than I’d expect. Are you seeing that query *always* there when you dump the list of queries? I am not sure what the empty COMMIT queries are really. Abhilash

4 years, 3 months

Re: How To Install Mailman 3 on Debian 10 (Complete Guide)

by Mark Dadgar

On Mar 2, 2021, at 9:31 AM, Quanah Gibson-Mount <quanah(a)symas.com> wrote: > --On Tuesday, March 2, 2021 9:09 AM +0100 Lars Schimmer <l.schimmer(a)cgv.tugraz.at> wrote: > >> On 01/03/2021 13:15, Brian Carpenter wrote: >>> On 3/1/21 3:10 AM, Lars Schimmer wrote: >>>> If it should be a gold standard, it should mention the default setup >>>> of a standard debian system (which is exim4, btw) and not assuming a >>>> special setup debian system. >>> >>> So why don't you write up your own how-to for your so-call ''standard >>> debian system". Remember this is a forum for Mailman 3, not a forum for >>> the users of a "standard debian system". So far your comments are not >>> helpful at all. >> >> Install debian >> >> apt-get install mailman3-full > > As someone who is stuck using the ancient version of mailman3 in debian, I have to disagree. 99.9999% of the time I hit an issue, it turns out it was fixed years ago, but because I use the debian maintained version, I don't have those fixes. It's horrible. +100 I originally installed mailman3 via the ubuntu packages and I eventually replaced that setup (read: paid Brian to re-install mailman3 “correctly") for 2 key reasons: 1) The ubuntu (and presumably debian) packages are 1+ years out of date - Quanah is correct in that most of the bugs you hit have been fixed already but haven’t made it through the package maintainer process yet. 2) The package installs are non-standard with respect to the way the mailman3 community tends to install them, which makes getting support here on this list much, much harder. You can see evidence of that periodically when someone asks a question and Mark’s response starts with “I’m not entirely sure how the <distro> package sets things up, but …”, which is no slight on Mark because he has his hands full with mm3 already and tracking every distro install layout is just not going to happen. It also means that the official mm3 docs don’t match what came out of your package. It’s just not good all the way around. > Distribution packages tend to be useful for really basic things like libraries. For constantly evolving projects where you need to be current, they're more of a detriment. So much this. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 4 months

Re: ModuleNotFoundError: No module named 'settings'

by Abhilash Raj

> On May 10, 2021, at 8:11 PM, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > Michela via Mailman-users writes: > >> The log file, /opt/mailman/web/logs/uwsgi-error.log, contains the >> following stack trace, however. Note the bit toward the bottom: >> "ModuleNotFoundError: No module named 'settings'" > > Given that you can run the applications from the command line as > systemd services, this almost certainly localizes the problem to uwsgi > itself. Note that uwsgi has been problematic lately. I don't recall > the details. I think there's a preference for gunicorn as the SGI > provider among the Mailman 3 developers (and it's what core uses > internally to provide the REST interface) so uwsgi may not get "beta" > testing in production from us. > > Specifically, is this line > > pythonpath = /etc/mailman3/ > > present, correct, and not commented out in uswgi.ini? > >> My configuration files outside of the Mailman virtual environment >> are in /etc/mailman/: > > Is it possible you have /etc/mailman/ instead of /etc/mailman3/ in > uwsgi.ini as in the above quote? (I am pretty sure that's a typo in > the post, but gotta check everything.) On the other hand, maybe we > did a typo, and there should be no trailing slash on /etc/mailman3 in > this statement. (Usually trailing slashes aren't a problem, > applications mostly ignore them, but there is no trailing slash on any > directory in my sys.path, so it's worth a try.) Yeah, it would be good to share the full contents of /etc/mailman3/uwsgi.ini, for some reason what is listed in the docs[1] is working on one of my test servers. Although, given that there are more than one reports of the same error, it is possible something is wrong or missing in the docs. The trailing slashes in this case isn’t really a problem I think. If you can share some initial parts of your uwsgi-error.log part where uwsgi initializes that would be useful too. I am looking something that looks like this: ``` *** Starting uWSGI 2.0.19.1 (64bit) on [Thu Jan 21 08:49:16 2021] *** compiled with version: 9.3.0 on 21 January 2021 08:40:15 os: Linux-5.4.0-1036-azure #38-Ubuntu SMP Wed Jan 6 18:26:25 UTC 2021 nodename: mailman machine: x86_64 clock source: unix detected number of CPU cores: 2 current working directory: /opt/mailman3 detected binary path: /opt/mailman3/venv/bin/uwsgi !!! no internal routing support, rebuild with pcre support !!! your processes number limit is 15571 your memory page size is 4096 bytes detected max file descriptor number: 1024 lock engine: pthread robust mutexes thunder lock: disabled (you can enable it with --thunder-lock) uwsgi socket 0 bound to TCP address 127.0.0.1:8000 fd 8 Python version: 3.8.5 (default, Jul 28 2020, 12:59:40) [GCC 9.3.0] PEP 405 virtualenv detected: /opt/mailman3/venv/ Set PythonHome to /opt/mailman3/venv/ Python main interpreter initialized at 0x56002ba3aed0 python threads support enabled your server socket listen backlog is limited to 100 connections your mercy for graceful operations on workers is 60 seconds mapped 166688 bytes (162 KB) for 2 cores *** Operational MODE: threaded *** added /etc/mailman3/ to pythonpath. WSGI app 0 (mountpoint='') ready in 1 seconds on interpreter 0x56002ba3aed0 pid: 715893 (default app) *** uWSGI is running in multiple interpreter mode *** spawned uWSGI master process (pid: 715893) spawned uWSGI worker 1 (pid: 715897, cores: 2) [uwsgi-daemons] spawning "mailman-web qcluster" (uid: 1001 gid: 1001) 08:49:18 [Q] INFO Q Cluster december-nebraska-helium-montana starting. 08:49:18 [Q] INFO Process-1:1 ready for work at 715904 08:49:18 [Q] INFO Process-1:2 ready for work at 715905 ``` Please ignore that the paths in my logs are `/opt/mailman3/*`, I have multiple installations on my test server, the docs say it should be `/opt/mailman/*`. It doesn’t really matter as long as they are consistent in all places. Also, what happens if you run the command "/opt/mailman/venv/bin/mailman-web qcluster” as a “mailman” user on your machine? Do you see the traceback like above or does it start a process like this? ``` mailman@mailman:~$ /opt/mailman3/venv/bin/mailman-web qcluster 05:05:29 [Q] INFO Q Cluster april-east-hot-potato starting. 05:05:29 [Q] INFO Process-1:1 ready for work at 3364005 05:05:29 [Q] INFO Process-1:2 ready for work at 3364006 05:05:29 [Q] INFO Process-1 guarding cluster april-east-hot-potato 05:05:29 [Q] INFO Process-1:3 monitoring at 3364007 05:05:29 [Q] INFO Q Cluster april-east-hot-potato running. 05:05:29 [Q] INFO Process-1:4 pushing tasks at 3364008 ``` [1]: https://docs.mailman3.org/en/latest/install/virtualenv.html#setting-up-a-ws… > > If it's none of the above, I'm out of ideas. Maybe Mark or Abhilash > has more experience. > > Steve > > _______________________________________________ > 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)

4 years, 1 month

Re: Core, Hyperkitty and Postorius releases

by Abhilash Raj

On Fri, May 14, 2021, at 2:16 PM, Odhiambo Washington wrote: > On Sat, May 15, 2021 at 12:01 AM Mark Sapiro <mark(a)msapiro.net> wrote: > > > On 5/14/21 1:54 PM, Odhiambo Washington wrote: > > > > > > /usr/local/include/sass > > > > > > That is the only thing found that is in the base system. > > > > And that's the one you want. What is it's mode? > > > > root@gw:/usr/home/wash # ls -al /usr/local/include/sass > total 104 > drwxr-xr-x 2 root wheel 512 Apr 16 16:49 . > drwxr-xr-x 176 root wheel 10240 Apr 19 18:05 .. > -rw-r--r-- 1 root wheel 2369 Apr 8 11:08 base.h > -rw-r--r-- 1 root wheel 10742 Apr 8 11:08 context.h > -rw-r--r-- 1 root wheel 6632 Apr 8 11:08 functions.h > -rw-r--r-- 1 root wheel 6489 Apr 8 11:08 values.h > -rw-r--r-- 1 root wheel 198 Apr 8 11:08 version.h > > I imagined I needed an executable. This sounds like a result of you running `pip3 install sass`, probably with sudo which failed mid-way due to the exception you posted above. Which OS are you using? On debian/ubuntu, you can install: sudo apt install sassc I am not exactly sure how it got removed during your upgrade to the new version of Mailman since it shouldn't affect your system packages. Did you install Mailman initially using system packages or instructions provided at [1]? [1]: https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… -- thanks, Abhilash Raj (maxking)

4 years, 1 month

Re: problem with postorius initial setup

by Abhilash Raj

-- thanks, Abhilash Raj (maxking) > On Mar 16, 2021, at 11:35 AM, John Covici <covici(a)ccs.covici.com> wrote: > > On Tue, 16 Mar 2021 12:14:36 -0400, > Stephen J. Turnbull wrote: >> >> John Covici writes: >> >>> Hi. I am trying to setup postorius, but I have run into a problem. I >>> am using the example project, except I am using postgresql instead of >>> sqlite3. I ran python manage.py migrate which was successful. >>> >>> On running the development server I get: >>> Exception in thread django-main-thread: >>> Traceback (most recent call last): >>> File >>> "/usr/lib/python3.8/site-packages/django/utils/module_loading.py", >>> line 20, in import_string >>> return getattr(module, class_name) >>> AttributeError: module 'postorius.middleware' has no attribute >>> 'APICountingMiddleware' >> >> This appears to be another version mismatch. The >> APICountingMiddleware appears to be a debugging or development >> instrumentation tool. It was added on 2021-02-28, so it's very >> recent. Somehow your Postorius settings.py is newer than your >> Postorius middleware.py. I would guess you have checked out or pip'ed >> a very recent version of Postorius but the example_project is picking >> up an older version, possibly from the Gentoo package. Why that could >> happen depends on whether you've set up a venv for the up-to-date >> Postorius, whether it's active, and so on. > > I think I know what is happening, but not how to fix. The > example_project which the docs told me to get is from the postorius > git which is, of course, recent, whereas the postorius I have from the > gentoo package is 1.3.3, which is not that old, but maybe not up to > the git version. Should I be using the git version? You want to follow this guide[1] for installing from pip. It covers both Postorius and Hyperkitty. [1]: https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… I am assuming you saw it in this doc [2] to use the example_project. That is very specific to development installations. I will update the document to make it clearer and point to [1] for any production setup. [2]: https://docs.mailman3.org/projects/postorius/en/latest/setup.html#setup-you… > > -- > Your life is like a penny. You're going to lose it. The question is: > How do > you spend it? > > John Covici wb2una > covici(a)ccs.covici.com > _______________________________________________ > 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/

4 years, 3 months

Re: Edit archived email? Is it possible?

by Prasanth Nair

Hi Mark, Many thanks for your help. I have managed to modify some of the messages after following your instructions. Kind regards, Prasanth On Wed, 29 Sept 2021 at 08:08, Prasanth Nair <prasanth.nair(a)linaro.org> wrote: > Hi Mark, > > Thank you for your help. Let me try this. > > Kind regards, > Prasanth > > On Tue, 28 Sept 2021 at 18:03, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 9/28/21 6:02 AM, Prasanth Nair wrote: >> > Hello, >> > >> > Does anyone know how to edit an archived email in Mailman3? It is >> possible >> > in Mailman2 ( >> > >> https://wiki.list.org/DOC/How%20do%20I%20edit%20the%20archives%20of%20a%20M… >> ). >> > Is there any option similar to this in Mailman3? >> >> >> In some sense the process is the same but possibly even simpler in >> Mailman 3. You need to modify the underlying data which requires >> appropriate access to the server. >> >> In Mailman 3, the data are in the hyperkitty_email table in Mailman's >> database. You can get the Message-ID hash from the URL to the archived >> message, e.g. for the message to which I'm replying, the URL is >> >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >> and the hash is 7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA. Then if you have >> access, you can do database queries like >> ``` >> SELECT subject, content FROM hyperkitty_email WHERE message_id_hash = >> '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; >> ``` >> and >> ``` >> UPDATE hyperkitty_email SET content = '<new content>' WHERE >> message_id_hash = '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; >> UPDATE hyperkitty_email SET subject = '<new subject>' WHERE >> message_id_hash = '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; >> ``` >> If the message has attachments, they are in the hyperkitty_attachment >> table and can be referenced by `email_id` which is the corresponding >> `id` from the hyperkitty_email entry. >> >> You can also do similar things via `django-admin shell`. E.g. >> ``` >> $ django-admin shell >> Python ... >> (InteractiveConsole) >> >>> from hyperkitty.models.email import Email >> >>> x = >> Email.objects.filter(message_id_hash='7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA') >> >>> print(x[0].content) >> ``` >> but this requires some knowledge of HyperKitty's models and Django's ORM. >> >> -- >> 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/ >> >

3 years, 9 months

Re: EMWD Mailing Lists Down

by Allan Hansen

All, I recently entered a ticket for some work and received this response: ***** Allan, Thank you for your business with EMWD however we are experiencing a severe shortage in labor(just like any other small business at the moment) and we cannot currently support your request. We hope to be at full staff in a few months but as you know this is a niche product and it is difficult to find or train mm3 experts. Thank you for your understanding. Sincerely, Marshall ***** I sincerely hope that they manage to get the company up and running again. I had great help from Brian and enjoyed working with him. Yours, Allan On 1/15/22, 18:18 , "Sherry Xie" <sherrytxie(a)gmail.com> wrote: Hi all, I am an EMWD Mailman 3 customer, and I recently realized my mailing lists are no longer working (the last email that went through was sent on December 25, 2021). Emails I send to the lists do not show up in archives or reach subscribers. It seems like others have had this issue before since ownership of the company was transferred following Brian Carpenter's passing – has anyone been able to get in touch with support or get their issues resolved? I've submitted a support ticket but have no idea if this is being monitored. I also have no way to contact the current management team, as only their names were announced in the November 5, 2021 email from Barbara Carpenter. Any help would be greatly appreciated – thanks in advance! Sherry _______________________________________________ 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/

3 years, 5 months

Re: How To Install Mailman 3 on Debian 10 (Complete Guide)

by Lars Schimmer

On 02/03/2021 18:31, Quanah Gibson-Mount wrote: > > > --On Tuesday, March 2, 2021 9:09 AM +0100 Lars Schimmer > <l.schimmer(a)cgv.tugraz.at> wrote: > >> On 01/03/2021 13:15, Brian Carpenter wrote: >>> On 3/1/21 3:10 AM, Lars Schimmer wrote: >>>> If it should be a gold standard, it should mention the default setup >>>> of a standard debian system (which is exim4, btw) and not assuming a >>>> special setup debian system. >>> >>> So why don't you write up your own how-to for your so-call ''standard >>> debian system". Remember this is a forum for Mailman 3, not a forum for >>> the users of a "standard debian system". So far your comments are not >>> helpful at all. >> >> Install debian >> >> apt-get install mailman3-full > > As someone who is stuck using the ancient version of mailman3 in debian, > I have to disagree. 99.9999% of the time I hit an issue, it turns out > it was fixed years ago, but because I use the debian maintained version, > I don't have those fixes. It's horrible. Intereting view for a software poackage taking a few years to get a way to migrate from mailman2 to mailman3. Or in other words: if a stable version is not useable/to old, the software is not production ready. Sure, bugs do happen, developement does happen. But for a production server you do not want to update every month just for the latest feature. If a software reaches stable, it gets a package which is able to run the lifetime of debian stable. Bugs will be iron out with debian security packages. All new features will not be production critical, mostly add new features. > Distribution packages tend to be useful for really basic things like > libraries. For constantly evolving projects where you need to be > current, they're more of a detriment. Nope. Vote against this view. You need a stable system to rely on and setup without hassle in a nonce. Not to check every package you installed for latest update and run updates every week with latest bugs, issues while upgrading a package. Debian stable has a reason to exist for admins with less time and a wish to run production ready software. Not latest bleeding edge testing software. > --Quanah > > -- > > Quanah Gibson-Mount > Product Architect > Symas Corporation > Packaged, certified, and supported LDAP solutions powered by OpenLDAP: > <http://www.symas.com> MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

4 years, 4 months

Re: Hyperkitty download mbox

by Mark Sapiro

On 4/25/21 2:20 PM, Andrew Hodgson wrote: > Hi, > > Hyperkitty 1.3.4. > > I am trying to download a complete list mbox by going to all threads view and using the download option. I have tried a couple of tools (Gunzip and Winrar) and both are giving me an unexpected end of file when trying to decompress the gz file. > > Here is the list URL I am using: https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil… Depending in the web server configuration, timeouts can occur when downloading large archive mboxes. instead of downloading the entire mbox with <https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil…>, do it in pieces by adjusting start and end. e.g. <https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil…> <https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil…> <https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil…> Although, I don't think timing out is the issue, and I'm not sure what is, but I think it has something to do with messages in the archive. If I try to get the 3 pieces as above, the first piece with start=2008-02-19&end=2012-12-31 works but the others don't and even the smaller <https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil…> fails the same way. If I try to get 2013 month by month, all work except December which gives me an internal server error. What's the traceback from that error. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

List creation error

by Odhiambo Washington

I am running this on a test environment - a Debian10 VM. Postorius comes up and I create a domain. All is fine. Then I create a list and see that the list is created, but there is an error below the message: Something went wrong HTTP Error 500: <html> <head> <title>Internal Server Error</title> </head> <body> <h1><p>Internal Server Error</p></h1> </body> </html> mailmansuite.log has the following entry: INFO 2021-01-06 10:31:48,062 4177 hyperkitty.lib.mailman Imported the new list testlist(a)mm3.washington.home from Mailman ERROR 2021-01-06 10:31:48,511 4177 postorius Un-handled exception: HTTP Error 500: <html> <head> <title>Internal Server Error</title> </head> <body> <h1><p>Internal Server Error</p></h1> </body> </html> Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/postorius/views/generic.py", line 74, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/views/generic/base.py", line 97, in dispatch return handler(request, *args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/postorius/views/list.py", line 264, in get 'hyperkitty' in self.mailing_list.archivers and # noqa: W504 File "/usr/lib/python3.7/_collections_abc.py", line 666, in __contains__ self[key] File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 146, in __getitem__ return self._get(key) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 88, in _get return self.rest_data[key] File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 74, in rest_data response, content = self._connection.call(self._url) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/restbase/connection.py", line 112, in call error_msg, response, None) urllib.error.HTTPError: HTTP Error 500: <html> <head> <title>Internal Server Error</title> </head> <body> <h1><p>Internal Server Error</p></h1> </body> </html> ERROR 2021-01-06 10:31:48,529 4177 django.request Internal Server Error: /mm3/mailman3/lists/testlist.mm3.washington.home/ ERROR 2021-01-06 10:31:48,529 4177 django.request Internal Server Error: /mm3/mailman3/lists/testlist.mm3.washington.home/ PS: I could probably have caused the error with some weird operation I did: Initially when postorius comes up, it has the domain - *example.com <http://example.com>*. I am not sure where it gets this. Using MySQL, I dumped the DB and s/ example.com/lists.washington.home/g then re-imported the DB, restarted mailman and apache2. Might that be the issue??? I am relying on https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 as the guide and where it gets the *example.com <http://example.com> *from still remains a mystery for me. I have blown away everything - except the config files and the scripts mentioned in this guide - twice and re-installed and still get the example.com domain as the default. There must be something obvious I am missing. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

4 years, 6 months

Mailman-users search results for query "2021"