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

[MM3-users] Re: Mailing lists sometimes do not honor moderation_action of non-members

by Mark Sapiro

On 11/3/19 6:58 PM, Alan So wrote: > Are there any pointer of documentation that I can clear all _these_nonmembers settings by updating the databases directly or using mailman shell? I am not so familiar with mailman shell though. We expect list owners use moderation_action only for members and non-members. $ bin/mailman shell -l test.example.com Welcome to the GNU Mailman shell The variable 'm' is the test.example.com mailing list >>> m.accept_these_nonmembers = [] >>> m.hold_these_nonmembers = [] >>> m.reject_these_nonmembers = [] >>> m.discard_these_nonmembers = [] That will just blindly clear them all. If you want to see what you're clearing, you could do things like >>> if m.accept_these_nonmembers: ... m.accept_these_nonmembers ... m.accept_these_nonmembers = [] ... which if the list's accept_these_nonmembers is non-empty will display it and then set it empty. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

[MM3-users] Re: Docker-Setup: example.com in test mails

by Mark Sapiro

On 2/24/22 13:30, Bjoern Franke via Mailman-users wrote: > Hi, > >> >> >> Exactly what messages are you referring to? I don't understand `test >> mails testing for bounces`. >> > > I mean the messages created by > > [mta] > verp_probes: yes I thought that might be what you meant, but you said > To our confusion, test mails testing for bounces are sent from example.com > > From: Mailman mailman(a)example.com > To: Mailman Bounces mailman-bounces(a)example.com > Verp probes are always addressed to the bouncing user, never to mailman-bounces(a)example.com unless mailman-bounces(a)example.com is a list member with bouncing deliveries. They are also from listname-bounces+<token>@example.com, not mailman(a)example.com. I don't know what messages you are looking at, but they don't seem to be verp probes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: DKIM signatures with message footers or subject prefixes

by Mark Sapiro

On 3/12/22 12:20, Stanisław Findeisen via Mailman-users wrote: > On Fri, Mar 11, 2022 at 10:41:00AM -0800, Mark Sapiro wrote: >> Also, your outgoing MTA should DKIM sign the mail on the way out. With that and the above setting, the outgoing message will have only your >> valid DKIM signature and no prior Authentication-Results:. > > Ok, you mean after replacing the From address with the list address, right? > I can see no way (or sense) to DKIM sign arbitrary From: addresses. Your DKIM signature only says you sent the mail and if the signature validates, the mail hasn't been modified since you signed it. I.e. validation of the signature is a statement to the recipient that the mail received is what you sent. That's all. If the domain of the From: address doesn't align with your domain, the signature won't help with DMARC, but that's a separate issue and why we have DMARC mitigations suck as replacing the From: with the list address. > This actually works quite good: the recipient just gets 2 DKIM signatures. The original one is broken, the MTA-generated one (after writing my list address into From) is OK. This is good enough even for ProtonMail (no red warning). And your rewriting the From: is only necessary for DMARC. If the ProtonMail red flag is only because there was no valid DKIM signature, you shouldn't need to rewrite From:. If it is because of DMARC, you do. > What about this list (mailman-users). It looks this one also has From address replacement + conditional DMARC mitigation. And remove_dkim_headers: no. Correct? This list has DMARC mitigation action = Replace From: and DMARC Mitigate unconditionally = No and remove_dkim_headers: no. We DKIM sign all outgoing mail from lists.mailman3.org. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: Restore/export existing Mailman lists + hyperkitty archives on a new server

by Mark Sapiro

On 9/15/22 01:22, Kimmo L wrote: > Hi Mark! > > I forwarded the same shunted file to you as well, which i sent to Steve. Thanks. I got it and will look further. > About that no "Message-ID" error - Basically it still occurs in mailman.log file even if some other list has been used. And our other lists does not use this "anonymous list" option. Those errors should result in the affected messages being saved as *.pck files in Mailman's var/archives/hyperkitty/spool/ directory. Possibly there is only one such 'bad message' which is retried each time there is a new post resulting in the same error. How many such files are there? If only one, please send me that one too. Also, these can be examined with `mailman qfile`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: Using the API to create nonmembers with a different moderation action than the list default

by Mark Sapiro

On 6/6/24 11:36 PM, Perry Kollmorgen wrote: > Hi, > > My next challenge is to script the setup of a bunch of nonmembers who have a moderation action of accept (or maybe defer) whilst the list itself has a nonmember action of hold. > > This is due to a relatively heavy use of nested lists, and have a fair number of people who might possibly send to all lists, and are important enough they wouldn't want to be manually allowed each time even if it only once. Note that beginning with Mailman 3.3.10 (not yet released) you can put things like @list2@example.com in accept_these_nonmembers of list1(a)example.com to accept posts from non_members who are members of list2(a)example.com. See https://gitlab.com/mailman/mailman/-/merge_requests/1154 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: Log Owner/Moderator actions ban address matching.

by Mark Sapiro

On 5/1/25 04:02, Stephen J. Turnbull wrote: > Odhiambo Washington via Mailman-users writes: > > > So this issue can be addressed by making Postorius to log user logins, > > right? > > However, I don't have the patch :) > > I would guess it's probably possible to get Django to do this, quite > possibly using standard configuration to do so. I just don't know > where to look offhand. Postorius can't log logins because it's not Postorius (or HyperKitty) that does the logging in. It is django-allauth. You can see the `Last Login` info for a user in the Django admin web UI under Authentication and Authorization -> Users django-mailman3 does have some involvement with logging in and it might be possible to add logging there, but I don't offhand know where. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

[MM3-users] Re: Language confusion in held mail notifications

by Mark Sapiro

On 9/22/21 2:16 AM, Henrik Rasmussen wrote: > I just upgraded from Mailman 3.2.0 (La Villa Strangiato) to Mailman 3.3.4 (Tom Sawyer) - Docker Mailman v0.3.12. As the language is not possible to set, and the default language is English, I set my user profile to Spanish and the list config to German, to figure out where the changes would take affect. > > After sending a mail to the list as the moderated list user, the resulting notification returned to the users email address is mostly in German, but the reason indicated is in Spanish "El mensaje proviene de un miembro moderado". I am unable to duplicate this in Mailman 3.3.5rc1. I set the list's language to German and a moderated user's language to Spanish. The held message notice to the user was entirely in Spanish and the notice to the admin was entirely in German. User Notice --------------------------------------------------- Date: Thu, 23 Sep 2021 17:12:50 -0700 From: test-bounces(a)msapiro.net To: mark(a)msapiro.net Subject: Su mensaje a test(a)msapiro.net espera la aprobación del moderador Su mensaje a la lista 'test(a)msapiro.net' con el asunto A test message Ha sido retenido hasta que el moderador de la lista pueda revisarlo y aprobarlo. El mensaje está siendo retenido por: El mensaje proviene de un miembro moderado O bien el mensaje será enviado a la lista, o bien recibirá una notificación con la decisión del moderador. --------------------------------------------------------------- Owner Notice -------------------------------------------------- Date: Thu, 23 Sep 2021 17:12:50 -0700 From: test-owner(a)msapiro.net To: test-owner(a)msapiro.net Subject: Der Beitrag test(a)msapiro.net von mark(a)msapiro.net muss genehmigt werden [-- Attachment #1 --] [-- Type: text/plain, Encoding: base64, Size: 0.5K --] Ihre Einwilligung als Administrator*in ist für folgende Nachricht an die Mailingliste nötig: Liste: test(a)msapiro.net Absender: mark(a)msapiro.net Betreff: A test message Die Nachricht wurde aus folgenden Gründen zurückgehalten: Die Nachricht kommt von einem moderierten Mitglied Besuchen Sie die Administrations-Seiten, um die Nachricht anzunehmen oder abzulehnen. [-- Attachment #2 --] [-- Type: message/rfc822, Encoding: 7bit, Size: 0.8K --] Date: Thu, 23 Sep 2021 17:12:48 -0700 From: Mark Sapiro <mark(a)msapiro.net> To: test(a)msapiro.net Subject: A test message User-Agent: Mutt/1.9.4 (2018-02-28) Give this a try. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan [-- Attachment #3 --] [-- Type: message/rfc822, Encoding: 7bit, Size: 0.9K --] Date: Thu, 23 Sep 2021 17:12:50 -0700 From: test-request(a)msapiro.net Subject: confirm b903b34955e0268e33b011ff9c9ccb7667dce4f2 Wenn Sie auf diese Nachricht antworten und den Subject: Header unverändert lassen wird Mailman die zurückgehaltene Nachricht verwerfen. Tun Sie dies, wenn es sich bei der Nachricht um Spam handelt. Wenn Sie auf die Nachricht antworten und einen Approved: Header mit dem Listenkennwort einfügen, wird Nachricht für die Veröffentlichung auf die Liste genehmigt. Der Approved: Header kann auch in der ersten Zeile des Textes der Antwort erscheinen. --------------------------------------------------------------- -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: LMTP on unix socket

by Mark Sapiro

On 10/20/19 3:55 PM, Hristo Venev via Mailman-users wrote: > How do I configure mailman to use a unix socket for lmtp connections? > Setting > > [mta] > incoming: mailman.mta.null.NullMTA > lmtp_host: /path/to/socket > > does not work. Mailman still tries to create a TCP socket. You can't do this. Mail Delivery is to Mailman's lmtp runner which uses the LMTP class in aiosmtpd <https://aiosmtpd.readthedocs.io/en/latest/> to create an LMTP server which listens for tcp connection on lmtp_host:lmtp_port. You would have to modify mailman/runners/lmtp.py to listen on a unix socket. The docs imply the aiosmtpd.controller.Controller class has a make_socket() method which "allows subclasses to customize the creation of the socket before binding" which I suppose could be used to create a unix socket, but mailman/runners/lmtp.py currently doesn't make use of that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

[MM3-users] Re: HyperKitty async tasks runner: systemd qcluster service fails eventually

by Mark Sapiro

On 12/5/19 6:17 AM, actionmystique(a)gmail.com wrote: > I think I have a lead: after having removed ```Restart=always``` which masked the details about the systemd service failure, I get: ...> Dec 05 15:04:06 samsung4-ubuntu django-admin[1199893]: File "/usr/lib/python3.7/logging/config.py", line 571, in configure > Dec 05 15:04:06 samsung4-ubuntu django-admin[1199893]: '%r' % name) from e > Dec 05 15:04:06 samsung4-ubuntu django-admin[1199893]: ValueError: Unable to configure handler 'file' ... > ... > 'file':{ > 'level': 'INFO', > #'class': 'logging.handlers.RotatingFileHandler', > 'class': 'logging.handlers.WatchedFileHandler', > ### 'filename': os.path.join(BASE_DIR, 'logs', 'mailmansuite.log'), > 'filename': '/var/log/mailman3/mailmansuite.log', Does the mailman user, 'list' or whatever you have for User=<user> and Group=<group> in the systemd service file have permission to create/write /var/log/mailman3/mailmansuite.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 8 months

[MM3-users] Re: MM3 shunting mails

by Mark Sapiro

On 12/5/19 1:40 PM, ikemulder(a)hotmail.com wrote: > > In the script I am filtering for 'mhonarc' ListArchivers, since the duplicate ListArchivers always seem to be mhonarc archivers. > > If this is not the appropriate place, please let me know - I would like to get to the bottom of this :). I see you've also filed <https://gitlab.com/mailman/mailman/issues/657>. Thank you for that. We are as puzzled as you are by this. It would help if you could detect this duplication when it happens and try to get more information. The problem is I can't see how to do that. I would start by adding some logging to the patch_put method of the ListArchivers class in mailman/rest/lists.py to log the list and the request. Then when you see the duplicate, you can check this log to see if anything suspicious happened just prior to that? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 7 months

Search results for query "sapiro"