Search results for "2021" - Mailman-users

Re: Documentation for transferiering a list between mm3 and mm3

by Johannes Winter

Am Fri, 26 Feb 2021 11:21:25 -0800 schrieb Mark Sapiro <mark(a)msapiro.net>: > On 2/26/21 11:03 AM, Morris Jones wrote: > > On 2/26/2021 10:55 AM, Mark Sapiro wrote: > > > Would it be unreasonable to do a database dump on the old instance > > and a restore on the new one? > > > The question is transferring a `list`. I took that to mean > transferring one of multiple lists to another installation which may > also have other lists. Yes, indeed, that was the question. Thank you for the answers!

4 years, 4 months

Re: Core, Hyperkitty and Postorius releases

by Mark Sapiro

On 5/14/21 5:02 AM, Odhiambo Washington wrote: > On Fri, May 14, 2021 at 2:52 PM Jeff Steele <jeff(a)steele.com> wrote: > >> >> >> On May 14, 2021, at 7:49 AM, Odhiambo Washington <odhiambo(a)gmail.com> >> wrote: >> >> /bin/sh: sass: Permission denied* >> >> >> >> Did you check the permissions on your sass binary? >> > > My mailman installed in /opt/mailman/mm > > find /opt/mailman/ -type f -name sass > > yielded nothing! Try `which sass` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

Re: can't get mail into mailman3 in docker

by matthew＠alberti.us

Bob, Can you run the command "sudo docker logs mailman-core" and see what the end of that says? Another good command to run is "sudo docker ps" and make sure the mailman-core container is actually running. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, August 11, 2021 1:25 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: can't get mail into mailman3 in docker On 8/10/21 11:29 AM, bob B wrote: > /opt/mailman/core/mailman-extra.cfg. now has > #lmtp_host: localhost > lmtp_host: 127.0.0.1 > lmtp_port: 8024 > > But but mail log shows > 2021-08-10T14:13:28.927266-04:00@####### postfix/qmgr[37253]: > DDF5D3083EC2: from=<user(a)user.com>, size=8181, nrcpt=1 (queue active) > 2021-08-10T14:13:28.973273-04:00@####### postfix/lmtp[39368]: > DDF5D3083EC2: to=<test@.....>, relay=127.0.0.1[127.0.0.1]:8024, > delay=0.07, delays=0.04/0.02/0.01/0, dsn=4.4.2, status=deferred (lost > connection with 127.0.0.1[127.0.0.1] while receiving the initial > server greeting) > > Also to clarify the images no longer have hard coded ips so I should NOT DO this correct? > ----------------------------- > lmtp_host: 172.19.199.2 > lmtp_port: 8024 > smtp_host: 172.19.199.1 > smtp_port: 25 > ----------------------------- I think that's correct, but I'm at a loss for helping further. Hopefully @maxking will be able to help. -- 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, 10 months

missing links in admin request mail Fwd: New subscription request to Mm3-test-mem from hstahl@uw.edu

by Stephen Willey Mats Mats

Mailman2 and other mailman3 installs I’ve seen included links in the moderation ‘requires approval’ or list subscription request approvals. But the messages from my mailman3 server does not have the links. What configuration am I missing? I’m running off the stable 0.3 docker images as updated this morning to the current releases (3.3.3, 1.3.4, 1.3.4) thanks, steve > From: list2-owner(a)mm3.xxx.s.uw.edu > Subject: list2(a)mm3.xxx.s.uw.edu post from xxx(a)jhmi.edu requires approval > Date: February 25, 2021 at 2:18:14 PM PST > To: list2-owner(a)mm3.xxx.s.uw.edu > > As list administrator, your authorization is requested for the > following mailing list posting: > > List: list2(a)mm3.xxx.s.uw.edu > From: xxx(a)jhmi.edu > Subject: this is a post that should be moderated > > The message is being held because: > > The message is not from a list member > > At your convenience, visit your dashboard to approve or deny the > request. > Begin forwarded message: > > From: mm3-test-mem-owner(a)mm3.xxx.s.uw.edu > Subject: New subscription request to Mm3-test-mem from xxx(a)uw.edu > Date: February 25, 2021 at 12:49:05 PM PST > To: mm3-test-mem-owner(a)mm3.xxx.s.uw.edu > > Your authorization is required for a mailing list subscription request > approval: > > For: xxx(a)uw.edu > List: mm3-test-mem(a)mm3.xxx.s.uw.edu

4 years, 4 months

Re: Core, Hyperkitty and Postorius releases

by Odhiambo Washington

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

4 years, 1 month

CVE-2021-40347: New security release for Postorius

by Abhilash Raj

Everyone, A security vulnerability was reported against Postorius recently which allows any logged-in user to unsubscribe any other member on any other list on same Mailman installation using a specially crafted POST request due to a missing ownership check. This has been assigned CVE-2021-40347. This affects all past versions of Postorius including 1.0.0. Thanks to Kunal Mehta for the security report and a quick patch to fix the vulnerability. I am also attaching a minimal patch that fixes it along with this email, without tests and NEWS so that it applies to older versions of Postorius easily (I have tested the included patch with 1.3.3, 1.3.2 git tags). Upgrading to 1.3.5 release is highly recommended and it mostly includes the fix for this vulnerability (and a small compatibility fix for django-mailman3 1.3.6) so it shouldn’t introduce any other bugs. You can upgrade to this release by running: $ pip install postorius==1.3.5 A full change log is available here[1] as usual and can be downloaded from PyPI[2]. [1]: https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-5 [2]: https://pypi.org/project/postorius/1.3.5/ Since there aren't many changes, this release requires 3.5+ like 1.3.4. Although, note that the next release will drop support for 3.5 and will support 3.6 only. For those of you who use container images, I am working on 0.3.12 of container images right now, so look out for that announcement. For those of you using the rolling releases, you can already upgrade to the latest version of the rolling release as it has the fix. -- thanks, Abhilash Raj (maxking)

3 years, 10 months

Re: FW: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/

by Christian Stalberg

Yes, I have django_mailman3/templatetags/d_gravatar.py in my installation. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, October 13, 2021 5:11 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: FW: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/ On 10/13/21 3:53 PM, Christian Stalberg via Mailman-users wrote: > Is this anything to be concerned about? It seems like an attempted break-in as I have no user named alekos.pantazis. First, this is a Django user, not a Mailman user. > -----Original Message----- > From: noreply(a)lists.ccalternatives.org > <noreply(a)lists.ccalternatives.org> > Sent: Tuesday, October 12, 2021 7:55 AM > To: csa(a)web-analysts.net > Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: > /user-profile/ > > Internal Server Error: /user-profile/ > > TemplateSyntaxError at /user-profile/ > 'd_gravatar' is not a registered tag library. Must be one of: The d_gravatar template tag was introduced by https://gitlab.com/mailman/django-mailman3/-/merge_requests/114 to support the `HYPERKITTY_ENABLE_GRAVATAR = False` setting for the user profile page. It should be OK. The error you see seems to say that django_mailman3/templates/django_mailman3/profile/profile.py contains {% load gravatar %} at line 3 but there is no django_mailman3/templatetags/d_gravatar.py file. Do you have the django_mailman3/templatetags/d_gravatar.py file in your installation? -- 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, 8 months

EMWD Mailing Lists Down

by Sherry Xie

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

3 years, 5 months

Re: Postorius no connection to REST API

by Richard Rosner

postorius, admin, hyperkitty and user-profile work now, accounts doesn't WARNING 2021-08-21 10:52:41,931 3975 django.request Not Found: /accounts WARNING 2021-08-21 10:52:41,931 3975 django.request Not Found: /accounts [pid: 3975|app: 0|req: 26/26] 127.0.0.1 () {56 vars in 1208 bytes} [Sat Aug 21 10:52:41 2021] GET /accounts => generated 5651 bytes in 433 msecs (H\ TTP/1.1 404) 5 headers in 170 bytes (1 switches on core 0) pid 3975 is /usr/bin/uwsgi --plugin python3 --ini /etc/mailman3/uwsgi.ini PS: now I seem to have done something stupid. I wanted to switch everything from example.com to the real domain. So I added it in admin and got rid of example.com. Seems there was some configuration missing, now nothing is working. How do I get everything back and have it use the right domain?

3 years, 10 months

Re: ModuleNotFoundError: No module named 'settings'

by Jeff

I found a work around for the problem with the missing settings module. I modified: /etc/systemd/system/mailmanweb.service to add the PYTHONPATH environmental variable: [Service] Environment="PYTHONPATH=/etc/mailman3/" User=mailman Group=mailman ExecStart=/usr/local/mailman3/bin/uwsgi --ini /etc/mailman3/uwsgi.ini Now it starts up fine: *** Starting uWSGI 2.0.19.1 (64bit) on [Tue May 11 09:38:47 2021] *** compiled with version: 8.3.1 20191121 (Red Hat 8.3.1-5) on 09 May 2021 00:39:19 os: Linux-4.18.0-240.22.1.el8_3.x86_64 #1 SMP Thu Apr 8 19:01:30 UTC 2021 nodename: xxxxxx machine: x86_64 clock source: unix detected number of CPU cores: 12 current working directory: / detected binary path: /usr/local/mailman3/bin/uwsgi !!! no internal routing support, rebuild with pcre support !!! your processes number limit is 126645 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 10 Python version: 3.8.3 (default, Aug 31 2020, 16:03:14) [GCC 8.3.1 20191121 (Red Hat 8.3.1-5)] PEP 405 virtualenv detected: /usr/local/mailman3 Set PythonHome to /usr/local/mailman3 Python main interpreter initialized at 0x7e65a0 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 250032 bytes (244 KB) for 4 cores *** Operational MODE: preforking+threaded *** added /etc/mailman3/ to pythonpath. WSGI app 0 (mountpoint='') ready in 0 seconds on interpreter 0x7e65a0 pid: 207058 (default app) *** uWSGI is running in multiple interpreter mode *** spawned uWSGI master process (pid: 207058) spawned uWSGI worker 1 (pid: 207060, cores: 2) spawned uWSGI worker 2 (pid: 207062, cores: 2) [uwsgi-daemons] spawning "/usr/local/mailman3/bin/mailman-web qcluster" (uid: 1001 gid: 1001) 09:38:48 [Q] INFO Q Cluster oklahoma-thirteen-johnny-alpha starting. 09:38:48 [Q] INFO Process-1:1 ready for work at 207067 09:38:48 [Q] INFO Process-1:2 ready for work at 207068 09:38:48 [Q] INFO Process-1:3 ready for work at 207069 09:38:48 [Q] INFO Process-1:4 ready for work at 207070 09:38:48 [Q] INFO Process-1:5 ready for work at 207071 09:38:48 [Q] INFO Process-1:6 ready for work at 207072 09:38:48 [Q] INFO Process-1:7 ready for work at 207073 09:38:48 [Q] INFO Process-1:8 ready for work at 207074 09:38:48 [Q] INFO Process-1:9 ready for work at 207075 09:38:48 [Q] INFO Process-1:10 ready for work at 207076 09:38:48 [Q] INFO Process-1:11 ready for work at 207077 09:38:48 [Q] INFO Process-1:12 ready for work at 207078 09:38:48 [Q] INFO Process-1:13 monitoring at 207079 09:38:48 [Q] INFO Process-1 guarding cluster oklahoma-thirteen-johnny-alpha 09:38:48 [Q] INFO Process-1:14 pushing tasks at 207080 09:38:48 [Q] INFO Q Cluster oklahoma-thirteen-johnny-alpha running.

4 years, 1 month

Mailman-users search results for query "2021"