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

[MM3-users] Re: settings.ACCOUNT_EMAIL_REQUIRED is deprecated in allauth-65.5.0

by Andreas Vetter

On Montag, 17. März 2025 14:41:40 CET Mark Sapiro wrote: > On 3/17/25 6:11 PM, Andreas Vetter wrote: > > What would be the correct setting for the new > > ACCOUNT_SIGNUP_FIELDS > > See > https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/settings/ma > ilman.py?ref_type=heads#L31 I just added the line del ACCOUNT_EMAIL_REQUIRED in my etc/mailman3/settings.py Since I disabled signup, this is enough for me. -- Mit freundlichen Gruessen, Andreas Vetter

5 months, 3 weeks

[MM3-users] Re: Can't post to my own list from HyperKitty

by MegaBrutal

Mark Sapiro <mark(a)msapiro.net> ezt írta (időpont: 2025. ápr. 7., H, 2:43): > On 4/6/25 17:30, MegaBrutal via Mailman-users wrote: > >> > > No, it doesn't say anything like that. It says if I'm not subscribed, > > sending the message would subscribe me – no address is shown there at > all. > > Compare your hyperkitty/templates/hyperkitty/fragments/send_as.html to > > https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/templates/hy… 100% match: fa83f9809576572bf6d40b9ce322bd8f6a939ec80f08186be0d184d62bc4a42e *./venv/lib/python3.9/site-packages/hyperkitty/templates/hyperkitty/fragments/send_as.html fa83f9809576572bf6d40b9ce322bd8f6a939ec80f08186be0d184d62bc4a42e */tmp/send_as.html

5 months

[MM3-users] Re: Can't post to my own list from HyperKitty

by MegaBrutal

On Mon, Apr 7, 2025, 03:04 Mark Sapiro <mark(a)msapiro.net> wrote: > so it is saying there is only one choice for sender which I think means > there is only one address associated with your login. That still doesn't > explain why it thinks you're not a list member. > Indeed, it doesn't explain. Are there any maintenance scripts or DB queries you recommend to run to get to see what's happening under the hood? I've already tried ``mailman-web mailman_sync``, but it didn't do anything. >

5 months

[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

4 months, 3 weeks

[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

4 months, 3 weeks

[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

4 months, 1 week

[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]

3 months, 2 weeks

[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.

2 months, 1 week

[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.

2 months, 1 week

[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 month, 1 week

Search results for query "sapiro"