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, 3 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, 5 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, 2 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, 1 month

[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

2 years, 10 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

5 months

[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

9 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

2 days, 7 hours

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

Search results for query "sapiro"