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

[MM3-users] Re: Caching problem with templates

by Mark Sapiro

On 6/28/25 22:05, Mark wrote: > > 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. The template caching occurs on retrieval. Editing the template in Postorius does not change the URI in the template table, so a subsequent retrieval still gets the old cached value. The task runner will delete the expired template the next time it runs but with default settings that's up to an hour later. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 3 weeks

[MM3-users] Re: Internal Server Error: /mailman3/postorius/lists/.../held_messages - humanize: where to put?

by Mark Sapiro

On 8/25/25 15:07, Flo via Mailman-users wrote: > > In /usr/share/mailman3-web/settings.py there is: > > INSTALLED_APPS = ( > ... > 'django.contrib.humanize', > ... > ) Then I don't understand why you are getting the error. django.contrib.humanize is required because it is referenced by django-allauth in templates here https://codeberg.org/allauth/django-allauth/src/commit/5baeee79b2915dbb881d… and here https://codeberg.org/allauth/django-allauth/src/commit/5baeee79b2915dbb881d… If django.contrib.humanize is loaded, those references should be satisfied. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 3 weeks

[MM3-users] Re: Internal Server Error: /mailman3/accounts/fedora/login/

by Mark Sapiro

On 11/19/25 6:28 AM, Bernie Hoeneisen wrote: > Addendum: > > In my case the URL triggering the Error `https://<your_site_url>/mailman3/accounts/fedora/login/?process=login&next=%2Fmailman3%2Faccounts%2Fsignup%2F` is returned by: > > - `https://<your_site_url>/mailman3/accounts/signup/?next=%2Fmailman3%2Faccounts%2Fsignup%2F` I think this issue is caused by fedora dropping support for OpenID and moving to OpenIDConnect. This is https://gitlab.com/mailman/django-mailman3/-/issues/83 which is partially fixed by https://gitlab.com/mailman/django-mailman3/-/merge_requests/262/ but also requires configuration changes as discussed in the `Migration from Fedora OpenID backend` section of https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst -- 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: Installing mailman 3

by Mark Sapiro

On 07/25/2017 01:19 PM, Rafael Mora wrote: > What should I do to tell Postfix to use my domain?? for example send emails > using the email account mailing(a)labbrands.com If what you're asking is how to configure Postfix to relay all outbound mail via some other email server, that is a Postfix configuration question. If I thought I could give you a simple answer and that would be the end of it, I'd try, but in your case every answer leads to another question, so I suggest you start here to learn about configuring Postfix <http://www.postfix.org/documentation.html>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 10 months

[MM3-users] Re: Missing mailman archives?

by Mark Sapiro

On 8/12/20 11:37 AM, Marco Marinello wrote: > Thank you, Mark, it worked. Hyperkitty is now successfully archiving. > I submitted https://gitlab.com/mailman/hyperkitty/-/merge_requests/276 to better document this dependency. Maybe it could just be added to Mailman's requirements.txt. OK. > I tried to import the missing mails, unsuccessfully. I saved the .eml files from Thunderbird and then did > cat * >> ../missing.mbox This will not make a .mbox because the 'From ' message separators will be missing. Each message has to have an initial line of the form From user(a)example.com Ddd Mmm dd hh:mm:ss yyyy -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Re: messages go to shunt queue

by Mark Sapiro

On 9/10/20 6:43 AM, Danil Smirnov wrote: > Hi guys, > > I've faced weird Core behaviour after the last upgrade of the docker > images. All the messages sent to a list now go straight to shunt queue with > the following error in the logs: > > --- > Sep 06 22:41:32 2020 (27) Traceback (most recent call last): ... > File "/usr/lib/python3.8/site-packages/mailman/rules/dmarc.py", line 217, > in is_reject_or_quarantine > for record in txt_rec.items[0].strings) > KeyError: 0 > Sep 06 22:41:32 2020 (27) SHUNTING: > 1599432092.4326646+4cbb58a0dd5d9705946ca583835e63ec175536e3 See <https://gitlab.com/mailman/mailman/-/issues/743>. -- 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: Member Issue Discovered

by Mark Sapiro

On 10/28/20 11:11 AM, Apollinaris Schöll wrote: > > Most important is to offer an UI to completely delete users for subscribers and list admins. Currently delete account shows this message "Are you sure you want to delete your account? This will remove your account along with all your subscriptions.” > This is not true and needs to be done. Why do you think it's not true? With current Mailman from the HEADs of the GitLab branches, the only thing not removed is posts from the archives. The Django account and the Mailman core user and address records are all removed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: mailman3-web and the django middleware problem

by Mark Sapiro

On 4/25/24 12:34, Thomas Stein wrote: > > I'm not sure how to add that to my django settings. Adding: > > x = list(MIDDLEWARE) > x.insert(0, 'allauth.account.middleware.AccountMiddleware') > MIDDLEWARE = x > > did not help. Any hints? I don't know how things are arranged in the Debian/Ubuntu package, but you may have a settings.py which at the end does something like ``` try: from settings_local import * except ImportError: pass ``` If that is the case, adding the above snippet to the end of settings_local.py should work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Re: hyperkitty threads by month question

by Mark Sapiro

On 7/9/24 11:07 AM, Bryan Fields wrote: > I have installed a testing server for an organization I'm working with > to explore migration from MM2 to MM3. Our main list has archives from > 1992, and when importing the mbox into hyperkitty/mm3 I notice the > archives by month only go back to July 2007, but the messages are there > when I search for specific ones from the old archive in the 1992-2007 > range. See this post and maybe more of that thread which may help. https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: Required permissions for mass operations

by Mark Sapiro

On 9/15/24 03:12, mailman3(a)werner.by wrote: > > To give them the moderation permission is quite easy: I add the users to the moderators of the lists. But for the user management I've to add the users to the list owners and then is there no restriction anymore to change the full list configuration. What can I do? I link to a documentation for this would help as well, but I found nothing. There is no role that allows a user to do exactly what you want. Implementation of such a role would be a significant effort. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

Search results for query "sapiro"