Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: List Migration from MM2.1 -> MM3

by Odhiambo Washington

On Mon, Aug 15, 2022 at 4:59 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/15/22 06:53, Odhiambo Washington wrote: > > > > That is exactly what I have in my mailman.cfg > > > > Installing Postfix suppresses that message though. I installed Postfix > and > > then disabled it. > > > > > Your /opt/mailman/mm/venv/bin/mailman is talking to a different Mailman > core than the one reading that mailman.cfg and the one Postorius is > talking to. > How can I track the one it's talking to? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 9 months

[MM3-users] Re: How to best disable message decoration for all lists defined for a domain

by Ralph Seichter

* Mark Sapiro: > It's still a work in progress. Of course. I did not mean to criticise, just point out what settings I was surprised not to find in the UI. > To not add headers and or footers, you need empty templates for them. > These could be created via the list's Templates form except until [1] > is fixed, you can't make empty templates. I actually found a workaround in the meantime: update template set uri='file:///dev/null' where id=123; Not that I like to modify the underlying database manually, but it seems to do the trick for now. -Ralph

6 years, 2 months

[MM3-users] Execution of msgfmt failed when performing post upgrade steps

by Torge Riedel

Hi, I'm currently running a test setup of MM3 using Mark Sapiros approach with two venv. I also adopted his post-upgrade-script for the web part (django). Just some minutes ago I updated the packages of my test setup with pip3 where hyperkitty is now 1.3.0 When runnin the post-upgrade-script I get the following error message: Execution of msgfmt failed: /opt/mailman/web/venv/lib/python3.6/site-packages/hyperkitty/locale/nb_NO/LC_MESSAGES/django.po:630: duplicate message definition... /opt/mailman/web/venv/lib/python3.6/site-packages/hyperkitty/locale/nb_NO/LC_MESSAGES/django.po:273: ...this is the location of the first definition msgfmt: found 1 fatal error Not sure whether this is an error of MM3 or one of its dependency packages. Best regards Torge

5 years, 8 months

[MM3-users] Re: mailman3 vs postfix

by Ralf Wiegand

Mark - I have a hard time following this. /path/to/where/your/settings/are located what settings? what do I am looking for? cd /opt/mailman # all mailman applications are under /opt/mailman ls django-mailman3 hyperkitty mailman mailmanclient mailman-hyperkitty mailman-suite postorius venv-3.6 settings.py? /opt/mailman/mailman-suite/mailman-suite_project? I do not understand??? Ralf On 4/28/20 3:59 PM, Mark Sapiro wrote: > On 4/28/20 12:42 PM, Ralf Wiegand wrote: >> (venv-3.6) [root@empire mailman]# django-admin createsuperuser >> No Django settings specified. > > In that case, you need to specify additional options: > > --pythonpath /path/to/where/your/settings/are located > --settings name_of_your_settings_file_without_the_.py > > e.g. something like > > django-admin --pythonpath /usr/share/mailman3-web \ > --settings settings createsuperuser > >

5 years, 1 month

[MM3-users] Re: Subscribing users stuck in pending hell

by Quanah Gibson-Mount

--On Wednesday, May 24, 2023 6:11 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/24/23 16:07, Quanah Gibson-Mount wrote: >> >> Package: mailman3 >> Version: 3.2.1-1 > > For that version pendings don't have a token_owner. This script will > delete all pending subscriptions, even those waiting moderator approval, > so if there are any of those, they should be handled first. > ``` > >>> pendings = getUtility(IPendings) > >>> for token, data in pendings.find( > ... pend_type=subscription): > ... pendings.confirm(token, expunge=True) > ... > >>> commit() > ``` Thanks Mark! I had to change it to pend_type='subscription' but other than that it worked! :) Regards, Quanah

2 years

[MM3-users] Re: integrating mm3 with postfix / lmtp

by Fabian A. Santiago

On October 26, 2017 10:05:11 PM EDT, Mark Sapiro <mark(a)msapiro.net> wrote: >On 10/26/2017 06:49 PM, Fabian A. Santiago wrote: >... >> To: >test123-confirm+b7322edad83ae7ec99cfc5100161c7062d2c7685(a)gjb-online.com > > >There is an issue in Mailman 3.1 with regexp tables not working for >addresses of this form. As I posted at ><https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>, >see <https://gitlab.com/mailman/mailman/issues/401> and ><https://gitlab.com/mailman/mailman/merge_requests/323>. That was it. Perfect. I manually modified my regexp map and it works now. Excellent and Thank you. You're the man. Does mm3 ever refresh those maps or only as I add new domains / lists? -- Thanks, Fabian S. OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

7 years, 7 months

[MM3-users] Re: Issues with cross posted emails after upgrading to mailman 3.3.6

by Simon Coggins

On 4 Nov 2021, at 11:57 pm, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: On 11/4/21 1:02 AM, Simon Coggins wrote: > > 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. As you have seen, this is new in 3.3.5. I recognize this is a problem. Previously, attempts to accept the message on the second and subsequent lists would throw an uncaught exception - see https://gitlab.com/mailman/mailman/-/issues/914<https://gitlab.com/mailman/mailman/-/issues/914> and this was a fix for that. Yeah I’m seriously amazed we’ve not had complaints in the year we’ve been running mailman3 that people have lost emails to multiple lists. Only now that you fixed the exception have people seen missing emails :) Please file an issue for this at https://gitlab.com/mailman/mailman/-/issues<https://gitlab.com/mailman/mailman/-/issues> and I will try to find a better solution. Your approach of munging Message-IDs will create other issues. Consider a post to a list with direct CC to userx. userx replies-all to the message received directly. the In-Reply-To of this reply is the unmunged Message-ID which will affect threading in the archives and other recipient's MUAs. I realize this is preferable to losing the message, but I hope we can do better. Yeah it’s not a great solution but it’s the quickest I could come up with that works “for us”. 99% of our lists are announcement lists only with minimal replies so while this will break some. I’m hoping it will give us enough time to wait out a proper fix. I’ve created a new issue #955 with as much detail as I think you’ll need. Let me know if you need any more. -- Mark Sapiro <mark(a)msapiro.net<mailto:mark@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<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, 6 months

[MM3-users] Re: Transaction failed: Duplicate header 'DKIM-Signature'

by Mohsen Masoudfar

________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, April 13, 2023 1:11 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Transaction failed: Duplicate header 'DKIM-Signature' Thank you Mark, please see below the responses to your questions. On 4/13/23 07:25, Mohsen Masoudfar wrote: > I am observing the following error message in the logs for one specific list: > > = = = > relay=email-smtp.us-east-1.amazonaws.com[35.168.84.210]:587, delay=0.27, delays=0.05/0.04/0.12/0.06, dsn=5.0.0, status=bounced (host email-smtp.us-east-1.amazonaws.com[35.168.84.210] said: 554 Transaction failed: Duplicate header 'DKIM-Signature'. (in reply to end of DATA command)) > = = = This is non-compliant. Various parts of RFC6376, e.g. sections 5.6 and 6.1 clearly anticipate that a message can contain multiple DKIM-Signature: headers. > As I mentioned, this happens for one single list only and this list has not been able to send any email for a week now. After checking mailman-users, I came across the following setting, which seems kind of related to my issue: Is email-smtp.us-east-1.amazonaws.com the outgoing MTA for Mailman. I.e the value reported by `mailman conf -k smtp_host` or perhaps smtp_host is a local MTA which is configured to relay via email-smtp.us-east-1.amazonaws.com? > > # mailman conf -k smtp_host > > [mta] smtp_host: localhost In what log is that message? > > in /var/log/mail.log Presumably this error occurs on Mailman's attempt to deliver the mail to `smtp_host`. Otherwise, I don't see how it affects all mail from this list, but I also don't understand why this list's delivery would be different from other lists. Postfix is running on the local host and in /etc/postfix/main.cf, this is defined: relayhost = [email-smtp.us-east-1.amazonaws.com]:587 > = = = > To distribute messages with valid DKIM signatures, I set > remove_dkim_headers: yes > in /etc/mailman3/mailman.cf > = = = > > Here are my questions: > 1 - I have around 100 lists and this happens for this one list only, so, I am not sure, if the issue might be solved with this change. This setting will remove all DKIM headers from the message as Mailman receives it. Then, it depends on how and how many DKIM signatures are added to the outgoing mail. > > could this have any side effects? Is there a reason that this is NOT set per default? > 2 - Because this happens for this one list only, I would rather change it for this one list only, is there any option available changing it for one list only and not for the whole server? No, there is no such option. The fact that this happens for only one list is very strange. I would need more information to understand why. Do these messages get queued in Mailman's retry queue? If so, if you examine one such message with `mailman qfile`, what are the complete headers from that message. > > /var/lib/mailman3/queue/retry is empty Thanks again. M -- 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to mmasoudf(a)aaas.org

2 years, 1 month

[MM3-users] Re: migration

by Dave McGuire

On 7/30/21 4:25 PM, Mark Sapiro wrote: >> I am not at all fluent in django interactions (I'm still not entirely >> sure of what django actually *is*) so I have some reading to do. Any >> pointers on "django wrangling for n00bs" would be great. As I >> mentioned, I've not been hacking on mm3, just using it. I'm an >> accomplished programmer, but embedded C and assembler are a few >> galaxies away from python and web services! > > > Django is a Python based web framework. It is the framework used to > support HyperKitty and Postorius. To learn more, start at > https://www.djangoproject.com/ I'll get to reading. Thanks! -Dave -- Dave McGuire, AK4HZ New Kensington, PA

3 years, 9 months

[MM3-users] Re: Whitelist non subscriber

by Barry Warsaw

On Aug 10, 2017, at 13:05, Mark Sapiro <mark(a)msapiro.net> wrote: > > Mailman 3 defines the list attribute accept_these_nonmembers, but it is > not currently implemented to actually have any effect, nor is it exposed > in Postorius. Yes, that attribute is deprecated and (almost) completely removed. > At the present, I think you would have to create a user record with the > address and add that user to all lists with role nonmember and > moderation_action 'defer' to apply subsequent tests or 'accept' to > unconditionally accept posts from that address. That’s the way it should be done. Those actions may not be exposed yet in Postorius or the CLI, so you might have to do it with a `wishlist` script. -Barry

7 years, 9 months

Search results for query "sapiro"