Search results for "2021" - Mailman-users

Re: Issues with cross posted emails after upgrading to mailman 3.3.6

by Simon Coggins

Ok so after pulling it all apart this appears to have been a major problem in mailman3 from conception maybe? So here’s what happening as I understand it. If an email comes in and it is address to 2+ lists and 2 or more of those lists hold the email for moderation. The email is stored in the database using the message-id-hash (or something based on the message-id). Then if one list moderator approve/discards the email then that action deletes the message from the database. But there are still 1+ other lists that the message was addressed to that have pending actions, but that email is now gone. Before 3.3.5 these approves were silently dropped and no email was sent to the list, but in 3.3.5 new code was added to send a dummy email that contains "The content of this message was lost. It was probably cross-posted to multiple lists and previously handled on another list.” We have multiple campuses in the same city and it’s not uncommon for people to send the same email to the multiple lists in the same city. This is where we’ve started to see the content was lost emails. I’m amazed we haven’t had people report missing emails before this. My very ugly hack that I’m sure is not even close to the right way of fixing this was to set exim to use max_rcpt = 1 when talking to the mailman LMTP server. Then I made the following changes to runners/lmtp.py *** lmtp.py.orig 2021-11-04 17:46:03.428874115 +1000 --- /opt/mailman/venv/lib/python3.6/site-packages/mailman/runners/lmtp.py 2021-11-04 17:37:59.911514738 +1000 *************** *** 37,42 **** --- 37,43 ---- import email import asyncio import logging + import hashlib from aiosmtpd.controller import Controller from aiosmtpd.lmtp import LMTP *************** *** 155,160 **** --- 156,171 ---- if msg.defects: return ERR_501 msg.original_size = len(envelope.content) + + # Modify the messageID so tha it's unique for each list. This requies + # the MTA to be configured to only send one RCPT per connection + # In exim this is max_rcpt = 1 + # SIMON HACK + del msg['Message-ID'] + msg['Message-ID'] = "{}{}".format(hashlib.sha512(envelope.rcpt_tos[0].encode('utf8')).hexdigest()[:24], message_id.strip("<>")) + message_id = msg['Message-ID'] + # END SIMON HACK + add_message_hash(msg) msg['X-MailFrom'] = envelope.mail_from # RFC 2033 requires us to return a status code for every recipient. All I’m doing is literally appending a subset of a hash of the mailing list rcpt address to the front of the message-id, so that if it gets moderated, each instance of the email has a different message-id and each moderation action has it’s own copy of the email to operate on. This seems to have gotten us out of the immediate issues. But I’m eager to find a better solution that might be more permanent. -Simon --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [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 On 4 Nov 2021, at 1:11 pm, Simon Coggins <s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au>> wrote: Sorry that should be we went from 3.3.4 -> 3.3.5. I’m just reading the code now but my quick reading of it seems to say that if someone sees to 2 lists and they are both moderated, if one list moderator releases it, the email is deleted from the store and then when the second person releases it it’s now a dummy message that has no contents? That doesn’t sounds right. -Simon --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [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 On 4 Nov 2021, at 12:50 pm, Simon Coggins <s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au>> wrote: Since upgrading from 3.3.4 to 3.3.6 we are seeing a high instance of emails that are sent to 2 lists (EG 2 campuses). One campus will get the email and the other campus will get an email that just contains "The content of this message was lost. It was probably cross-posted to multiple lists and previously handled on another list.” Is this something new in 3.3.6? I’m trying to work out what’s going on and why it would be lost. Both lists need the email as the membership list is different so the people on the second list get a useless email. -Simon --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [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

3 years, 8 months

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

by Simon Coggins

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 > On Mar 18, 2021, at 5:31 PM, s.coggins(a)cqu.edu.au wrote: > > Just to add to this. Looking at the active queries in PostgreSQL there appear to be a bunch of commits that haven't finished. I don't know how it all fits together but it looks like the commits aren't finishing and transactions are staying open, so when I hit an open transaction all write operations for the DB hang until the transaction has finished. > > postgres=# SELECT pid, age(clock_timestamp(), query_start), usename, query > FROM pg_stat_activity > WHERE query != '<IDLE>' AND query NOT ILIKE '%pg_stat_activity%' > ORDER BY query_start desc; > pid | age | usename | > query > > --------+-----------------+-------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > ------------------------------------------------------------------------------------------------------- > 15767 | 00:01:58.30353 | mailman | SELECT member.id AS member_id, member._member_id AS member__member_id, member.role AS member_role, member.list_id AS member_list_id, member.moderation_action AS member_moderation_action, mem > ber.address_id AS member_address_id, member.preferences_id AS member_preferences_id, member.user_id AS member_user_id, member.bounce_score AS member_bounce_score, member.last_bounce_received AS member_last_bounce_received, member.la > st_warning_sent AS member_last_warning_sent, member.total_warnings_sent AS member_total_warnings_sent + > | | | FROM member JOIN mailinglist ON member.list_id = mailinglist.list_id JOIN preferences ON preferences.id = member.preferences_id > > + > | | | WHERE mailinglist.process_bounces = true AND member.total_warnings_sent >= mailinglist.bounce_you_are_disabled_warnings AND preferences.delivery_status = 3 > 18033 | 00:05:28.255636 | mailman | DELETE FROM member WHERE member.id = 169331 > 15762 | 00:11:42.842237 | mailman | COMMIT > 15740 | 00:11:59.12324 | mailman | COMMIT > 15760 | 00:12:01.212976 | mailman | COMMIT > 15757 | 00:12:01.542144 | mailman | COMMIT > 15755 | 00:12:01.708328 | mailman | COMMIT > 15754 | 00:12:01.804737 | mailman | COMMIT > 15751 | 00:12:01.921644 | mailman | COMMIT > 15745 | 00:12:02.72934 | mailman | COMMIT > 15743 | 00:12:02.795885 | mailman | COMMIT > 15742 | 00:12:02.948795 | mailman | COMMIT > 15738 | 00:12:03.3471 | mailman | COMMIT > 15664 | 00:12:08.480084 | mailman | COMMIT > (21 rows) > > > I've checked my production system and I can see the same COMMIT queries running. Some for 2 days (since the last restart). > _______________________________________________ > 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/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org> -- thanks, Abhilash Raj (maxking)

4 years, 3 months

Re: uncaught bounce messages

by Mark Sapiro

On 10/23/21 10:51 AM, David Bremner wrote: > > I'm getting (many) uncaught bounce messages for one user. Other than > forcibly unsubscribing them, is there anything I can do? I hesitate to > post this message publically, but here is what I can see, somewhat > anonymized If you send me the complete bounce message off list, I can see if it should be added to the recognition at https://gitlab.com/warsaw/flufl.bounce/. BTW, is flufl.bounce in your installation version 4.0? If not you can update via pip install -U flufl.bounce which may help. Actually, depending on how these where installed, it might be necessart=y to do pip install -U flufl.bounce flufl.lock flufl.i18n To avoid import errors due to packaging issues. > The MIME structure looks like > > └┬╴multipart/mixed 7030 bytes > ├─╴text/plain 442 bytes > ├─╴message/delivery-status 176 bytes > └─╴text/rfc822-headers 5301 bytes This is not a RFC 3464 compliant DSN which looks like the above except the top level is multipart/report, not multipart/mixed. However, our recognizer shouldn't care as it only looks at the message/delivery-status part. > In /var/log/mailman3/bounce.log I see lines like > > Oct 23 08:20:00 2021 (5320) Bounce message w/no discernable addresses: <hex-digits(a)foo.bar> <hex-digits(a)foo.bar> is the Message-ID: > In the delivery-status part I see A compliant DSN will also have a Reporting-MTA: section preceding the Final-Recipient: section. > Final-Recipient: rfc822; fub(a)foo.bar > Action: delayed > Status: 4.0.0 This is not a bounce. It is a 'delivery delayed' message. If delivery is not accomplished within an MTA configured time (days), it will turn into a 5.x.x failure which is a bounce, but since fub(a)foo.bar was not recognized, the DSN is non-compliant in some way. In any case, please send me a copy of the bounce so I can see about recognizing it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

Re: docker mailman-core mailman3 image not responding on port 8024

by Abhilash Raj

Sorry for stepping in this very late. The problems here are possibly due to the recent changes in the docker-mailman related to removal of static IPs in the container images. The changes have been reported working by some folks, but i know that they aren’t really using the docker-compose.yaml provided in the repo or have highly customized versions of those so the combination of both might be broken. It is also a problem that the documentation isn’t versioned properly to signify the difference that has been made in the repo since the last released version of the container image :( Either way, can you share the contents of /etc/mailman.cfg from inside the mailman-core container? That is most definitive source of truth for what actually configuration is being passed to Mailman Core to infer which actual host:port is the LMTP runner listening to and if the configuration being passed to it are what we expect. Abhilash > On Aug 17, 2021, at 7:17 AM, bob B <bader(a)cchmc.org> wrote: > > Ok, I took a step back and started fresh... So the issue appears to be that mailman-core docker image is not replying on port 8024. > > I did a packet capture and it shows (172.23.01 is the gateway for the docker network on the host, 172.23.03 is the IP of mailman-core when I did the capture) > *************************************** > 1 2021-08-16 14:15:14.865053 172.23.0.1 172.23.0.3 TCP 74 34066 → 8024 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=985607751 TSecr=0 WS=128 > 2 2021-08-16 14:15:14.865084 172.23.0.3 172.23.0.1 TCP 54 8024 → 34066 [RST, ACK] Seq=1 Ack=1 Win=0 Len=0 > *************************************** > > The above show the docker host sending/relaying mail to mailman-core, but mailman-core does not acknowledge on port 8024. > > The images are up i.e > *************************************** > 58923db6fb9f maxking/mailman-core:0.3 "docker-entrypoint.s…" 26 minutes ago Up 25 minutes 127.0.0.1:8001->8001/tcp, 127.0.0.1:8024->8024/tcp mailman-core > *************************************** > > > > Docker yamel has the port setup (8024) > *************************************** > services: > mailman-core: > image: maxking/mailman-core:0.3 > container_name: mailman-core > hostname: mailman-core > . > . > ports: > - "127.0.0.1:8001:8001" # API > - "127.0.0.1:8024:8024" # LMTP - incoming emails > networks: > mailman: > *************************************** > > I can nc to the ports for docker web & 8001 on core and they are listening > > But 8024 is not responding > *************************************** > #>docker-mailman-host]# nc -v 172.23.0.4 8000 > Ncat: Version 7.50 ( https://nmap.org/ncat ) > Ncat: Connected to 172.23.0.4:8000. > ^C > #>docker-mailman-host]# nc -v 172.23.0.4 8080 > Ncat: Version 7.50 ( https://nmap.org/ncat ) > Ncat: Connected to 172.23.0.4:8080. > ^C > #>docker-mailman-host]# nc -v 172.23.0.3 8001 > Ncat: Version 7.50 ( https://nmap.org/ncat ) > Ncat: Connected to 172.23.0.3:8001. > ^C > > #>docker-mailman-host]# nc -v 172.23.0.3 8024 > Ncat: Version 7.50 ( https://nmap.org/ncat ) > Ncat: Connection refused > *************************************** > > Docker logs show postfix is up on mailman-core > *************************************** > sudo docker logs mailman-core > List of databases > Name | Owner | Encoding | Collate | Ctype | Access privileges > -----------+---------+----------+------------+------------+--------------------- > mailmandb | mailman | UTF8 | en_US.utf8 | en_US.utf8 | > postgres | mailman | UTF8 | en_US.utf8 | en_US.utf8 | > template0 | mailman | UTF8 | en_US.utf8 | en_US.utf8 | =c/mailman + > | | | | | mailman=CTc/mailman > template1 | mailman | UTF8 | en_US.utf8 | en_US.utf8 | =c/mailman + > | | | | | mailman=CTc/mailman > (4 rows) > > Postgres is up - continuing > Using Postfix configuration > Found configuration file at /opt/mailman/mailman-extra.cfg > HYPERKITTY_URL not set, using the default value of http://mailman-web:8000/hyperkitty > > *************************************** > > > > Any ideas is there anything else I can do to troubleshoot? Is the issue with the mailman-core image? > _______________________________________________ > 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)

3 years, 10 months

Re: mass subscribers disablement!?

by Christian Stalberg

Yes I upgraded to a version >=3.3.1 and had 70 subscribers disabled. Is there a way to see via the web GUI which subscribers were disabled? Correspondingly, can I re-enable delivery for them via the web GUI? Thank you in advance. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, October 22, 2021 5:51 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: mass subscribers disablement!? On 10/22/21 2:07 PM, Christian Stalberg via Mailman-users wrote: > I added the additional hosts to ALLOWED HOSTS in settings_local.py and > mailman is distributing mail to subscribers again. However, I then > received many emails of valid users subscriptions being disabled. What > would cause that? Did you just upgrade Mailman core from a version <=3.3.0 to one >=3.3.1? If so, see https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/U 5ZW6X5QLQRXUOMD2DN77CYCOLKVMUXJ/ > Can subscriber management be done via command line? See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/do cs/commands.html for description of the available mailman subcommands. If you are interested in re-enabling delivery for members whose delivery is disabled by bounce, you can do this fairly easily in an interactive `mailman shell` session. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/do cs/shell.html Something like the following session: $ bin/mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> lm = getUtility(IListManager) >>> for mlist in lm.mailing_lists: ... for member in mlist.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... member.preferences.delivery_status = DeliveryStatus.enabled ... print('Re-enabled delivery for bouncing member {} on list {}' ... .format(member.address.email, mlist.list_name)) ... <print output here> >>> commit() >>> exit() -- 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

Re: Anyone using Rspamd with Mailman 3?

by Philip Colmer

On Thu, 23 Sept 2021 at 06:19, Torge Riedel <torgeriedel(a)gmx.de> wrote: > Am 22.09.21 um 11:20 schrieb Philip Colmer: > > why don't you let Mailman3 do the DMARC mitigation? > > I do have DMARC mitigation activated in mailman3, so that all mails sent > are coming from a unique mail for each list. Some list members have strict > SPF setups forcing me to do that. > Just to confirm, the DMARC mitigation action is "Replace From: with list address" and DMARC mitigate unconditionally set to Yes? > Following the config, I use rspamd from http://rspamd.com/apt-stable/ I was using the ASAN build but I've switched back to the normal build just for consistency. Version is 3.0-2~focal > rspamadm configdump arc > *** Section arc *** > sign_networks [ > "127.2.4.7", > ] > use_domain = "recipient"; > allow_envfrom_empty = true; > allow_hdrfrom_multiple = false; > allow_username_mismatch = true; > sign_inbound = true; > sign_local = false; > symbol_sign = "ARC_SIGNED"; > path = "/var/lib/rspamd/dkim/$selector.key"; > try_fallback = true; > use_redis = false; > key_prefix = "ARC_KEYS"; > allow_hdrfrom_mismatch = true; > sign_authenticated = false; > use_esld = true; > selector = "2019"; > > *** End of section arc *** > > rspamadm configdump dkim_signing > *** Section dkim_signing *** > sign_authenticated = true; > use_esld = true; > selector = "2019"; > try_fallback = true; > use_domain = "header"; > allow_hdrfrom_mismatch = false; > symbol = "DKIM_SIGNED"; > allow_username_mismatch = true; > allow_envfrom_empty = true; > allow_hdrfrom_multiple = false; > key_prefix = "DKIM_KEYS"; > use_redis = false; > sign_local = true; > sign_networks [ > "127.2.4.7", > ] > path = "/var/lib/rspamd/dkim/$selector.key"; > > *** End of section dkim_signing *** > Thanks for sharing that. There wasn't anything of substance that was different. I'm still hitting a problem though where the final receiving MTA says that the ARC header provided by Rspamd is invalid (BodyHash is different from the expected one). I have now submitted an issue on GitHub against Rspamd because I am concerned it is trying to apply ARC before it applies DKIM, which is incorrect. Regards Philip

3 years, 9 months

Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by Mark Sapiro

On 3/2/21 12:33 PM, David Partain via Mailman-users wrote: > On Tue, 2021-03-02 at 20:07 +0000, David Partain via Mailman-users > wrote: >> On Tue, 2021-03-02 at 19:56 +0000, David Partain via Mailman-users >> wrote: >> >> I assume this is because /usr/share/mailman3-web/manage.py, which >> has: >> >> '#!/usr/bin/env python' >> >> resolves to Python 2.7.17. >> >> Should I could try changing that to '#!/usr/bin/env python3' and see >> what happens? :) I could also uninstall python2 but that becomes >> more of a nail-biter... NO! Do not do that. >> I can report that the above doesn't help. Neither does just making >> /usr/bin/python link to /usr/bin/python3.6 >> >> I still get errors in mailman-web.log pointing to 2.7 as shown in my >> previous mail. > > If I force the issue by linking /usr/bin/python to /usr/bin/python3.6, > I start seeing: > > ModuleNotFoundError: No module named 'hyperkitty > > in mailman-web.log. > > I know next to nothing about python. Is > > pip install hyperkitty > > the right answer? No. > I have the following installed now: > > # dpkg -l | grep hyperkitty > python-django-hyperkitty 1.1.4-4 > python3-mailman-hyperkitty 1.1.0-4 > > but this version of Ubuntu has no python3-django-hyperkitty or I'd just > try installing that... This is all because you are using the Ubuntu 18.04 package which is about 4 years out of date and is from the era where HyperKitty, Postorius and django_mailman3 still ran under Python 2.1.7. Unless you want to remove the Ubuntu package and install everything with pip, you need to just stick with what you have that at least partly works and we'll try to determine how to fix the utf8mb4 issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

Re: Issues with cross posted emails after upgrading to mailman 3.3.6

by Simon Coggins

On 8 Nov 2021, at 11:11 am, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: Simon Coggins wrote: > On 7 Nov 2021, at 10:54 am, Mark Sapiro <mark(a)msapiro.netmailto<mailto:mark@msapiro.netmailto>:mark@msapiro.net<mailto:mark@msapiro.net>> wrote: > I wound up taking a different approach. I check for other references to > the message in the message store and only delete the message if there > are none. The fix is at > https://gitlab.com/mailman/mailman/-/merge_requests/932/diffshttps://gitlab…<https://gitlab.com/mailman/mailman/-/merge_requests/932/diffshttps://gitlab…> > Oh nice. That seems like a sensible solution. Thanks for tackling so quickly. I’ll do some testing today and roll it out once testing is complete. I made a small change to defend against 'impossible' situations. See https://gitlab.com/mailman/mailman/-/merge_requests/933/diffs<https://gitlab.com/mailman/mailman/-/merge_requests/933/diffs> Thanks for the heads up. I did a bunch of testing with the original patch and was happy with it so we’re running that in prod now. How far off is 3.3.6? Just working out if I apply this slight change or wait for the full release. _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org> --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [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 ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: attachment.png Content-Type: image/png Name: attachment.png Replaced multipart/alternative part with first alternative.

3 years, 7 months

Re: under which uid should uwsgi/manage.py run?

by Guillermo Hernandez (Oldno7)

On 14/1/22 18:16, Axel Rau wrote: > Hi Guillermo, > > thanks for your reply. > >> Am 14.01.2022 um 12:51 schrieb Guillermo Hernandez (Oldno7) via Mailman-users <mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org>>: >> > . . . >> drwxr-xr-x 21 mailman mailman 1024 Jul 8 2021 lists > How are new lists created by the web frontend with uid www? That's because is not "www" who is doing that work (I suspect). In my apache24 httpd.conf file I have these lines ##### LoadModule wsgi_module "/usr/local/lib/python3.7/site-packages/mod_wsgi/server/mod_wsgi-py37.so" WSGIPythonHome "/usr/local" WSGIDaemonProcess hyperkitty threads=25 python-path=/usr/local/mailman3 user=mailman3 group=mailman WSGIProcessGroup hyperkitty #### In the httpd-vhosts.conf I have all the Alias directives and, related to this, this lines: WSGIScriptAlias /mailman3 /usr/local/mailman3/wsgi.py process-group=hyperkitty WSGIScriptAlias /hyperkitty /usr/local/mailman3/wsgi.py process-group=hyperkitty WSGIScriptAlias /postorius /usr/local/mailman3/wsgi.py process-group=hyperkitty WSGIScriptAlias /archives /usr/local/mailman3/wsgi.py process-group=hyperkitty <Directory "/usr/local/mailman3"> <Files wsgi.py> Require all granted </Files> WSGIProcessGroup hyperkitty </Directory> ##### I believe that you can be suffering of a mixup of configuration files (al least the ownership that has to be mailman). > I like your approach, but must resolve my pgsql cert access issue. > >> I've read your mail about your installation and I did it different. I followed the steps that I detailed in https://forums.freebsd.org/threads/mailman-3.61050/#post-488128 <https://forums.freebsd.org/threads/mailman-3.61050/#post-488128> > I followed the same, but had trouble with the recent cryptography python package. > I’m now at Python3.9 > >> Thus I don't know if it can help, but I know for sure that I don't like that your ../var/etc dir is owned by root. > I have changed that to mailman. > > Axel > --- > PGP-Key: CDE74120 ☀ computing @ chaos claudius > > _______________________________________________ > 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: mailman3 on new Debian 12 installation, got ssl apache working on all URLs except /mailman3

by Philip Bondi

LE and certbot created those paths for me, somehow. Both on CentOS and Debian. Don't know why. Checked my putty logs. Cannot find the first emergence of strange path. You guys are superheroes. Debian 12: <PRE> pjbondi@shackleton12:~$ sudo -i root@shackleton12:~# cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" root@shackleton12:~# ls -alF /etc/letsencrypt/live/ total 32 drwx------ 7 root root 4096 Nov 29 07:57 ./ drwxr-xr-x 9 root root 4096 Mar 27 15:02 ../ -rw-r--r-- 1 root root 740 Nov 27 10:27 README drwxr-xr-x 2 root root 4096 Mar 6 09:03 systemdatabase.ca/ drwxr-xr-x 2 root root 4096 Mar 6 09:03 systemdatabase.ca-0001/ drwxr-xr-x 2 root root 4096 Mar 6 09:04 systemdatabase.com/ drwxr-xr-x 2 root root 4096 Mar 6 09:04 systemdatabase.com-0001/ drwxr-xr-x 2 root root 4096 Mar 6 09:04 systemdatabase.homelinux.com/ root@shackleton12:~# </PRE> CentOS 7: <PRE> [1004] $ cat /etc/os-release NAME="CentOS Linux" VERSION="7 (Core)" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="7" PRETTY_NAME="CentOS Linux 7 (Core)" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:centos:centos:7" HOME_URL="https://www.centos.org/" BUG_REPORT_URL="https://bugs.centos.org/" CENTOS_MANTISBT_PROJECT="CentOS-7" CENTOS_MANTISBT_PROJECT_VERSION="7" REDHAT_SUPPORT_PRODUCT="centos" REDHAT_SUPPORT_PRODUCT_VERSION="7" [1005] $ ls -alF /etc/letsencrypt/live/ total 4 drwx------. 7 root root 168 Aug 15 2023 ./ drwxr-xr-x. 9 root root 108 Jan 19 03:22 ../ -rw-r--r--. 1 root root 740 Jul 2 2020 README drwxr-xr-x. 2 root root 93 Jan 19 2023 systemdatabase.ca/ drwxr-xr-x. 2 root root 112 Jan 19 03:22 systemdatabase.ca-0001/ drwxr-xr-x. 2 root root 112 Feb 5 2021 systemdatabase.com/ drwxr-xr-x. 2 root root 112 Jan 19 03:21 systemdatabase.com-0001/ drwxr-xr-x. 2 root root 112 Jan 19 03:20 systemdatabase.homelinux.com/ </PRE> Again. We're almost there with ssl apache configs. - works for LE challenge and Subversion https://systemdatabase.ca/ - 6 paths work for MM3 https://systemdatabase.ca/postorius/, etc - But https://systemdatabase.ca/mailman3 fails

3 months, 1 week

Mailman-users search results for query "2021"