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

[MM3-users] Re: Unable to ban users via mailman-shell

by Mihai Moldovan

* On 4/13/25 17:19, Mark Sapiro wrote: > Do you have a setting for `banner` in the `[shell]` section of your > mailman.cfg? Whoops, yes, I do. Removed it, and the messages appear correctly, of course. It's a downstream packaging bug, the sample config they created only includes the first line: https://git.launchpad.net/ubuntu/+source/mailman3/tree/debian/contrib/mailm… Thanks. Bug report time to Ubuntu it is. Mihai

1 year, 4 months

[MM3-users] Re: Setup Question: Disk-Layout (Migrating from Mailman 2.1)

by Mihai Moldovan

* On 4/17/25 19:38, Mark Sapiro wrote: > There is no Mailman command to do this, but a Python script is very > simple. Something like > ``` > [script] > ``` Great, that will definitely create it in the format expected by Python and hence mailman! Thank you very much. Mihai

1 year, 4 months

[MM3-users] Re: configuring postfix local recipient table

by Alexander Inzinger-Zrock

Splitting up answer: Am 29.04.25 um 18:27 schrieb Mark Sapiro: > Also, is there anything in Mailman's logs from the time you ran `mailman > aliases`? Nothing in logs (before or) after command ''mailman aliases'' and debug level everywhere is: info. What logs? Everything under /opt/mailman/mm/var/logs: + bounce.log + debug.log + mailman.log + plugins.log + smtp.log All empty. lg aiz

1 year, 3 months

[MM3-users] Re: Masking email addresses in the archives

by Odhiambo Washington

On Mon, May 26, 2025 at 5:31 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/26/25 9:47 AM, Odhiambo Washington via Mailman-users wrote: > > I must have missed this if it was ever discussed, but is it possible to > > mask the list members' email addresses in the archives? > > > See https://gitlab.com/mailman/hyperkitty/-/issues/508 Thank you. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 2 months

[MM3-users] Re: Caching problem with templates

by Mark

On Sat, 2025-06-28 at 20:56 -0700, Mark Sapiro wrote: > > > A much simpler way to accomplish the same thing is to set > > cache_life: 1m > > in the [mailman] section of mailman.cfg. > Yes, I thought so too. I also tried 0d -- which wrote the expiry date the same as the created date (to the second). # /etc/mailman3/mailman.cfg [mailman] cache_life: 0d But, just as with writing in a past date, it didn't solve the problem. I also spun up a brand new server to thrash it out there, but no joy there either.

1 year, 1 month

[MM3-users] Re: Caching problem with templates

by Mark

On Sat, 2025-06-28 at 21:55 -0700, Mark Sapiro wrote: > > See https://gitlab.com/mailman/mailman/-/issues/1230 > > I intend to implement disabling the cache entirely by setting > cache_life > to any zero value, i.e. 0s, 0m, 0h, etc. > Setting the cache_life to a zero value only writes the expiry date as "now". The cached file is still there. And it doesn't appear to be getting overwritten (as expected) when the template is edited.

1 year, 1 month

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

by Mark

On 2025-08-01 02:46, Mark Sapiro wrote: >> And here I had >> >> return super().is_open_for_signup(self, req) >> >> which should return the is_open_for_signup result from >> allauth.account.adapter.DefaultAccountAdapter but since that result is >> an unconditional True, what you have is OK too. > > > Actually, that too was wrong. It should have been > > return super().is_open_for_signup(req) > > but that is now moot as > > return True > > is fine. Ahhh. Thank you for letting me know that. I had used "return True" in an act of desperation. Is good to be shown how to do it right. :-)

1 year

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

by Mark

On 2025-08-01 19:40, Mark Sapiro wrote: > 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 If I leave the modified "user_adapter.py" in place, and remove the ACCOUNT_ADAPTER string from the "settings.py" file all is well ie. the SignUp pages display as they should.

1 year

[MM3-users] Re: Subscription Request asking for Confirmation instead of Moderation

by Henry Hartley

> -----Original Message----- > From: Mark Sapiro <mark(a)msapiro.net> > Sent: Thursday, August 28, 2025 18:57 > > What does the mail to the user, FIRSTLAST(a)SCHOOL.edu, say? I.e., if the > subscription is waiting confirmation there should be a mail to the user with > Subject: Your confirmation is needed to join the MAILINGLIST mailing list I've having the users do some testing to see if a) they can reproduce the problem and b) if so whether or not the confirmation email is sent. -- Henry Hartley Westat RB 2151

11 months, 3 weeks

[MM3-users] Re: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/lists/test2.***/settings/message_acceptance MultipleObjectsReturned .. get() returned more than one EmailAddress -- it returned 2!

by ^m'e

Mark Sapiro wrote: > https://www.msapiro.net/scripts/UC_fix to fix this and one at > https://www.msapiro.net/scripts/Mult_primary to fix a possible side > effect of the other. The same problem appeared today with my mariadb-based installation. @Mark, do you have a mysql version of your scripts? -- ^m'e

11 months, 2 weeks

Search results for query "sapiro"