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

[MM3-users] Re: parallel processing of out queue messages

by Mark Sapiro

Dan Caballero writes: > > So is there a 1:1 relationship between the number of runners and the maximum number of messages that may be processed with .bak files in the out queue? Yes. The way this works is the runner gets the first message in it's slice from the .pck file and renames the .pck to .bak. It then processes the message and upon successful completion removes the .bak. I.e., the .bak file contains the message currently being processed by that runner. The purpose of the .bak is disaster recovery in case the runner gets killed (say by a power failure), when it starts again it recovers the .bak file. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/core/switchboa… for the details of how all this, including slicing, works. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

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

by Mark Sapiro

On 7/30/25 16:10, Mark wrote: > > Disabling the Account "Sign-up" globally can be done by adding the > following to "/etc/mailman3/settings.py". > > ACCOUNT_ADAPTER = 'django_mailman3.views.user_adapter.DisableSignupAdapter' > > I have several domains on the server. Is it possible to disable the > Sign-up for only one of the domains ? Anything is possible, it's only code ;) You could make your own user_adapter.py which is modified like ``` --- a/django_mailman3/views/user_adapter.py +++ b/django_mailman3/views/user_adapter.py @@ -31,7 +31,10 @@ class DisableSignupAdapter(DefaultAccountAdapter): """ def is_open_for_signup(self, req): - return False + if req.META.HTTP_HOST == 'the.domain': + return False + else: + return super().is_open_for_signup(self, req) class EnableSocialSignupAdapter(DefaultSocialAccountAdapter): ``` and set that as the ACCOUNT_ADAPTER. This depends on whatever is proxying to Django setting the appropriate HTTP_HOST header. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months

[MM3-users] Re: After server upgrade debian 11→12 and reinstalling everything in (venv), I got this error when accessing → mailman3/lists

by Mark Sapiro

On 8/29/25 09:26, Wikinaut wrote: > Just two follow-up questions. > > 1. Is this documented somewhere (where)? See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… Also https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n… > 2. If I create /opt/mailman/mm/var/templates/site/LC/list:member:generic:footer.txt as suggested, I suppose that this then the new default for those lists, where no distinct /opt/mailman/mm/var/templates/lists/LIST_ID/LC/list:member:generic:footer.txt footer exists . Pls. can you confirm, or correct me? That's correct as long as there is no /opt/mailman/mm/var/templates/domains/MAIL_HOST/LC/list:member:generic:footer.txt -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months

[MM3-users] Re: Problems with SPOOFED_UNAUTH

by Mark Sapiro

On 9/9/25 09:56, M.Ede via Mailman-users wrote: > Thanks for your quick response und the links :-) > > When I switch list configuration to > Anonymous list: No > DMARC mitigation action: No DMARC mitigatins > everythings works fine, rspamd is fine with my mail. > > But with > Anonymous list: Yes > DMARC mitigation action: Replace From: with list address > I get the SPOOFED_UNAUTH. First of all, DMARC mitigations are not applied to anonymous lists because the From: header in mail from an anonymous list is already the list address. That said, it looks like the issue is caused when the From: address is the list address. I don't know why that would be but I'm guessing what you need is some setting in mailcow/rspamd to authorize the list address. -- 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: Mailing lists sometimes do not honor moderation_action of non-members

by Mark Sapiro

On 11/1/19 2:30 AM, Alan So wrote: > Double check the list that have issue: > > On mailman 2, > accept_these_nonmembers is empty > discard_these_nonmembers is empty > hold_these_nonmembers have a few email addresses > > The list was imported to mailman 3 a few months ago. > > On mailman 3, > accept_these_nonmembers is empty > hold_these_nonmembers is empty > discard_these_nonmembers have a few email addresses which is the same as those in hold_these_nonmembers on mailman 2. > > Therefore the import21 seem not importing the lists correctly. See <https://gitlab.com/mailman/mailman/issues/588>. import21 should convert addresses in MM 2.1 *_these_nonmembers to MM 3 nonmembers with appropriate moderation_action and keep only regexp patterns in MM 3 *_these_nonmembers. Prior to core 3.3.0 this was not working. -- 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: Disable Sign-up per domain

by Mark Sapiro

On 8/2/25 16:16, Mark wrote: > > It fails for both domains on the server with the ACCOUNT_ADAPTER string > in "settings.py" and the unmodified "user_adapter.py". > > This says to me that the "settings.py" is calling the "user_adapter.py" > which, for some strange reason, is still trying to match a site(host) name. I don't think that's it. I think it's earlier in the processing than that. What happens if you put ``` ACCOUNT_ADAPTER = 'allauth.account.adapter.DefaultAccountAdapter' ``` in settings.py. Also, what are the settings in your web server for proxying to Mailman. I have tried this in a test installation with two domains and ``` SITE_ID = 0 ACCOUNT_ADAPTER = 'django_mailman3.views.user_adapter.DisableSignupAdapter' ``` and I have no issue accessing accounts/signup at either domain. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 3 weeks

[MM3-users] Re: [Bug] Someone not a member of list is treated as member - strange

by Mark Sapiro

On 8/23/25 05:57, Wikinaut wrote: > > When sending from address2, my mail is accepted. When I, for sake of completeness switch 1. to moderate mails from member[sic], my mail from address2 gets moderated. If any of the From: header, the envelope sender, the Reply-To: header if any or the Sender: header if any of a post contains a member address, the post is considered to be from that member. That is the default list, but it can be modified by setting sender_headers in the [mailman] section of mailman.cfg. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/email/message.… and https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.… Does this explain the issue? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months

[MM3-users] Re: How to connect mailman into existing postfix server

by Mark Sapiro

On 09/16/2018 02:07 AM, Hagen Bauer wrote: > Hi to all, > > I am trying to setup mailman3 with the Docker Image. Everythings works > relative nicely but I am blocked by the Postfix integration part. > > I have a small postfix server that is delivering mails to known domains > and an alias map. The standard use case assumes that the external > postfix is only routing mails to the mailman lmtp. If I do this all my > old users are recected. If your list domain is a virtual alias domain, see <https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#unusual-…>. This is written assuming 'hash' tables and I think the Docker image generates 'regexp' tables, but it should work with those. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 5 months

[MM3-users] Re: Hyperkitty issue(s)

by Mark Sapiro

On 5/28/20 8:06 AM, brylon(a)oit.rutgers.edu wrote: > Yes, I've stopped/started Mailman (quite a few times). > > Is there a particular order to undo Hyperkitty and re-do? Or perhaps add some debug lines to a particular file to get at the root cause? I'm not certain, but I don't think your issue has anything to do with the installation of HyperKitty itself. From the OP, the issue occurs in REST upon a get of /3.1/lists/bry_test4.lists-test.rutgers.edu/archivers which is probably coming from Postorius -> Settings -> Archiving. The actual error occurs in Core trying to process that request, and while it clearly has to do with archiving configuration, I don't think the installation of Hyperkitty is the issue. What happens if you set [archiver.hyperkitty] enable: no and restart Mailman? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: LTMP to Postfix problem

by Mark Sapiro

On 6/18/20 2:24 PM, Brian Carpenter wrote: > > The log entry posted today was: > > Jun 18 15:07:32 2020 (29862) lmtp runner started. > > That was when I restarted Mailman core. If it happens again, I will see > if the lmtp runner is running. My feeling is it died but I don't know > for sure. If you have it, look through the mailman.log for entries around the last time the connections started to be refused. See if there are entries about the runner exiting. Also, just before you restarted, there will be several runner caught SIGTERM. Stopping. and runner exiting. messages. If lmtp runner is among those, it was still running when you restarted. What you are looking for is some exception/traceback from the time connections start to be refused. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

Search results for query "sapiro"