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

[MM3-users] Re: Deliverability and Spam Filtering

by Mark Sapiro

On 1/30/20 1:58 PM, Tom @ Gather wrote: > Interesting! Does the `in` queue also work for emails to subaddresses like > foo-owner, etc? Or is it only for list posts? -bounces goes to bounces -confirm, -join, -leave (and their synonyms -subscribe and -unsubscribe) and -request go to command -owner goes to in. But there's more to it that that. There's also things put in the metadata in the queue entry such as mail to -owner sets to_owner = True > Relatedly, why is `list_id` a required parameter? Isn't that information > contained in the email? Possibly not. The recipient list is the envelope recipient which may or may not be in the message headers - it could be a Bcc to the list. Thus, listid needs to be set in the metadata as well. You need to look at mailman/runners/lmtp.py and emulate what it does. -- 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: Mailman Suite installation on CentOS 7

by Mark Sapiro

On 11/8/21 4:18 AM, Kimmo L wrote: > Hello! > > I want to install fresh Mailman, which is combined with hyperkitty+postorius. After checking documentation i found, that Mailman Suite is perfect for me. > But i have some misunderstandings about installation. I only found this part in documentation, which explains how to clone and start using Mailman Suite (https://docs.mailman3.org/en/latest/devsetup.html#run-the-mailman-suite-com…) > > But am i correct, that before doing so, i need to install mailman core, mailman client, django-mailman3 ? > Or what would be the correct steps to build up my first Mailman Suite on CentOS? The docs you want to look at are https://docs.mailman3.org/en/latest/#the-pre-installation-guide and https://docs.mailman3.org/en/latest/install/install.html. There is also information at https://wiki.list.org/x/17891998 and in docs linked from thefirst paragraph thereof. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: Messages not picking up header or footer template

by Mark Sapiro

On 2/26/23 13:04, benjamin(a)tougshire.com wrote: > > I can see the entry in the database with the uri: http://localhost:8000/mailman3/api/templates/list/testing.comms.sdcvirginia… > > I can do a wget on that uri and download a copy of the footer, and it looks right > > But when I send a message to the list and the message is forwarded, the footer isn't on the messages that members receive > > Looking at mailman.log, I cannot see any attempt to access the footer. I can see connections to the REST API (config, roster/owner, roster/moderator) that correspond to the time I sent the message Can you see an attempt to GET /mailman3/api/templates/list/testing.comms.sdcvirginia.org/list:member:regular:footer in your web server's logs? Is there anything in Django's log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: Social signup?

by Mark Sapiro

On 3/15/23 05:08, Duane Raymond wrote: > > I'll jump over to the developers list when I start this (I'm about to > travel for a week to run an annual event in Oxford - so the far removed > from programming)...but which chatGPT suggested so far was > > 1. Extending postorius/signups.html with a loop to get the configured > social login providers PLUS adding a csrf_token field to the form > 2. Modifying postorius/views.py (which doesn't seem to exist but there > is a postorius/views folder) - so perhaps this is views/urls.py This is not what you want to do for this. The changes need to be in django-mailman3, not postorius. I have attached a patch which might work for you. I think it is good, but some of the wording is stuff that may not be appropriate. See what you think. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: unrequested unsubscription

by Mark Sapiro

On 6/14/23 19:40, Mike Wertheim wrote: > I have a Mailman 3 email list, running on Mailman 3.3.3 on Debian 11. > > A few of the list members are reporting that they received Email Address > Unsubscription Confirmation emails, but claim that they never requested to > be unsubscribed. (All are Gmail users. but they might be coincidental, > since most list members are Gmail users.) > > Has anyone seen this behavior before? Any ideas on what might be happening? Yes. This is someone sending an email `leave` or `unsubscribe` command for the user in question. This may be malicious, i.e. someone doesn't like a user's posts and tries to unsubscribe them, or it may be just spam of some sort. the user should just ignore the email. Beyond that, there's not much you can do unless you can identify from mail logs the source of the requests. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: Removing the footer from mailing list messages

by Mark Sapiro

On 12/7/25 14:00, MegaBrutal via Mailman-users wrote: > > What I already tried: define a custom template for > list:member:regular:footer. The result was that the mailing list stopped > operating altogether, no messages passed through until I deleted this > template. After I deleted it, all delayed e-mails were forwarded at once. How did you create the footer? If you created a file at Mailman's var/templates/whatever/list:member:regular:footer.txt, it probably was not readable by the Mailman user. If you created it via Postorius there is probably and issue with your setting for POSTORIUS_TEMPLATE_BASE_URL. > What would be the right way to remove the footer? For all lists sudo -u mailman cp /dev/null var/templates/site/en/list:member:regular:footer.txt For a single list sudo -u mailman cp /dev/null var/templates/lists/LIST-ID/en/list:member:regular:footer.txt -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 1 week

[MM3-users] Re: Disable Sign-up per domain

by Mark Sapiro

On 7/31/25 23:00, Mark wrote: > > The traceback does suggest that the SITE does not exist... Yes. Please confirm that the issue only occurs with the modified /opt/mailman/venv/lib/python3.11/site-packages/django_mailman3/views/user_adapter.py and does not occur with the original .../user_adapter.py. Also, prior to installing the modified /opt/mailman/venv/lib/python3.11/site-packages/django_mailman3/views/user_adapter.py did you have ACCOUNT_ADAPTER = 'django_mailman3.views.user_adapter.DisableSignupAdapter' in your settings or did you only add that with the modified .../user_adapter.py I.e., I'm trying to determine if there is some issue with the modified ../user_adapter.py or if the issue does not involve the modification, but rather just the setting of ACCOUNT_ADAPTER Also, when does this error occur? Does it occur an all web access to the site or only on access to the accounts/signup page? and does the host in the https request make a difference? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

[MM3-users] Re: How to build docs and how to contribute documentation

by Mark Sapiro

On 5/5/26 15:37, Craig Leres via Mailman-users wrote: > On 5/1/26 09:18, Stephen J. Turnbull wrote: >> >> We ask that you write a NEWS item (docs/NEWS.rst), and include that in >> the MR. Add "(:mr:42)" at the end, for value of "42" = the merge >> request number assigned by GitLab. Just a one-liner saying docs for >> Sendmail configuration were added is fine. > > I don't quite understand this step. My mr is 1496 and the "docs" > pipeline seems happy. Do I add a commit to the mr I just created and add > something to src/mailman/docs/NEWS.rst? I would guess under "3.3.11" in > the "Other" section? Yes, adding the item in the 3.3.11 Other section is appropriate. The reference would be (:mr:1496) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 2 weeks

[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

5 years

[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, 7 months

Search results for query "sapiro"