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

[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

10 months, 4 weeks

[MM3-users] Re: Time Zone Issue in Postorius

by Mark Sapiro

On 2/7/22 21:18, David Newman wrote: > On 2/4/22 10:29 AM, Mark Sapiro wrote: >> >> The appropriate setting for Django is always `TIME_ZONE = >> 'UTC'`because the time passed from Mailman core is a naive >> datetime.datetime object and is actually UTC. > > Could use clarification on this. Are you referring to the settings.py > file, or something else? Settings.py > Asking because my settings.py currently has: > > # Django time zones > USE_TZ = True > TIME_ZONE = 'America/Los_Angeles' It should be TIME_ZONE = 'UTC' Times passed from Mailman core are naive times, I.e. they don't have time zone info, but they are in UTC. Thus for Django to get the correct time with time zone you need USE_TZ = True (without that, Django will throw an exception about naive times) and the TIME_ZONE to apply is UTC. With those settings, Django has the correct time zone aware times. > and list timestamps appear to work OK both in Hyperkitty and as received > by members' mail clients. Mail sent to list members is not at all affected by this. That involves Mailman core only. Also, time stamps on posts in HyperKitty come from Date: headers or Django internal times. Where you see this manifested is for example when looking at a held message in Postorius and seeing the hold time. which is a time stamp generated by Mailman core. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 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

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

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

6 years, 1 month

[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, 11 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, 5 months

[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

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

2 years, 1 month

[MM3-users] Re: MM2 to MM3 Archives Loading

by Mark Sapiro

On 11/21/24 13:16, Joshua Bushe wrote: > > I’ve successfully converted a list from Mailman 2 to Mailman 3, and most things are working smoothly. However, I’m encountering an issue with the archives in the GUI: > > Problem: The archives don’t load on the overview page. > Odd Behavior: If I use the search function, the archives appear as expected, but they remain invisible on the main overview. > Has anyone encountered this issue or have suggestions for troubleshooting? Are either of the Hide inactive or Hide private boxes checked? Is there anything relevant in Django's logs? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

Search results for query "sapiro"