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

[MM3-users] Re: Migrating archives from Mailman21 to Mailman3

by Mark Sapiro

On 9/24/24 12:03, Odhiambo Washington via Mailman-users wrote: > On Tue, Sep 24, 2024 at 7:38 PM Mark Sapiro <mark(a)msapiro.net> wrote: >> >> Yes. There is no requirement that archives have a matching list in >> Mailman core. > > > So the documentation at https://docs.mailman3.org/en/latest/migration.html > needs revision as it creates the impression that a matching list needs to > be there: > ``` > $ python manage.py hyperkitty_import -l foo-list(a)example.com > $var_prefix/archives/private/foo-list.mbox/foo-list.mbox > ``` Are you saying that the above quoted command is what gives that impression? I don't see that `foo-list(a)example.com` is the name of the list for the HyperKitty archive only and `$var_prefix/archives/private/foo-list.mbox/foo-list.mbox` is the MM 2.1 mbox. If you are saying something else gives that impression, what in particular is that? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

[MM3-users] Re: 502 Bad Gateway??? Trying to change stuff

by Mark Sapiro

On 04/23/2017 12:57 PM, Mark Sapiro wrote: >> I am trying to change my email address, but forgot password. The screen for >> reset gets >> >> 502 Bad Gateway >> ------------------------------ >> nginx/1.4.6 (Ubuntu) >> any way someone can fix this???? > > If this is on <https://lists.mailman3.org/accounts/password/reset/>, it works for me, and I don't see any relevant 502s in logs. If it is on another server, you'll have to contact them. Additional info. This was on lists.mailman3.org. There were some serious issues with the server on Saturday. All or parts of Mailman were down for several hours. Those issues have been addressed and a fix installed so the same thing won't happen in the future. Anyway, that was almost certainly the reason for the 502 which is no longer occurring for the OP. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 7 months

[MM3-users] Re: lists.mailman3.org web site.

by Mark Sapiro

On 08/30/2016 09:10 AM, Barry Warsaw wrote: > On Aug 30, 2016, at 12:01 AM, Mark Sapiro wrote: > >> Django Allauth is now properly configured and working on >> lists.mailman3.org. You can log in by email/password as noted above or via >> OAuth2 with a GitHub, GitLab, Google or Facebook identity. ... > I'd mildly like to see Launchpad support, but I understand 1) it's a minority > platform; 2) it only supports OAuth 1. The current list of Django Allauth 3rd party providers (unfortunately, Launchpad isn't one) is at <https://django-allauth.readthedocs.io/en/latest/providers.html>. I don't see much point in adding a large number as it would just create clutter without much benefit, but other than not wanting to add OpenID/Yahoo at least until we get DMARC mitigations, if anyone has a strong interest in one of the others, I can add it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 3 months

[MM3-users] Re: Error while Approving a Post Through Email

by Mark Sapiro

On 12/14/22 15:40, Mark Sapiro wrote: > > It is a bug, but that isn't the correct fix. The list's > moderator_password attribute should already be encrypted. The bug is we > don't catch the passlib.exc.UnknownHashError. This is reported at https://gitlab.com/mailman/mailman/-/issues/1046 and fixed at https://gitlab.com/mailman/mailman/-/merge_requests/1072. > It appears you either have not set the lists moderator_password or you > have not set it to a properly encrypted value. Did you set it and if so, > how? The above fix won't fix your underlying issue but will report that your confirmation failed for 'Invalid Approved: password'. If you set the list's moderator_password via REST, it will be properly encrypted. If you set it via mailman shell, instead of ``` mlist.moderator_password = 'password' ``` you need ``` mlist.moderator_password = config.password_context.encrypt('password') ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: Welcome message template errors

by Mark Sapiro

Mark Sapiro wrote: > I just did a test on my development system and I see the same timeout > error, so it's not just you. I'll work on this. This is very strange. In my test, I see this in the apache log: 127.0.0.1 - - [26/Apr/2024:08:59:25 -0700] "GET /mailman3/api/templates/list/test.msapiro.net/list:user:notice:welcome HTTP/1.1" 200 4215 "-" "python-requests/2.28.1" I.e., apache gets the request and serves the template, and then 5 seconds later I see Apr 26 08:59:30 2024 (2592) deque: Traceback (most recent call last): ... socket.timeout: The read operation timed out I also note that this timeout only occurs when it is a subscription via REST. I.e. subscription via email or `mailman addmembers` sends the proper welcome message. So it has something to do with the retrieval being done by a rest runner, but I still don't know what the underlying issue is. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users] Re: Mailman - delete or backup old archived messages

by Mark Sapiro

On 6/30/21 9:23 PM, Mark Sapiro wrote: > On 6/30/21 6:23 AM, Lucia Moreno wrote: >> Hi Mark, >> >> We are facing the same issue. My postgres database is growing too fast >> and >> I would need to do some creaning of old archives dated from 2001 and keep >> only the last, lets say... 5 years. >> >> Could you please help us with the development of such a script? I have no >> experience in python. > > The attached script is a rough idea. Another way to do this that might actually be preferable is to download the entire archive from HyperKitty as a mbox, then split the mbox into what you want to keep and what you don't, delete the list from HyperKitty and then run hyperkitty_import to import only the messages you want to keep. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: Error while Approving a Post Through Email

by Mark Sapiro

On 12/14/22 09:41, Mark Sapiro wrote: > > I don't have more time to look at this now, but I think it's a bug. This > patch > ``` > --- a/src/mailman/rules/approved.py > +++ b/src/mailman/rules/approved.py > @@ -140,6 +140,7 @@ class Approved: > mpw = mlist.moderator_password > else: > mpw = mlist.moderator_password.decode('utf-8') > + mpw = config.password_context.encrypt(mpw) > is_valid, new_hash = config.password_context.verify(password, > mpw) > if is_valid and new_hash: > # Hash algorithm migration. > ``` > may fix it. It is a bug, but that isn't the correct fix. The list's moderator_password attribute should already be encrypted. The bug is we don't catch the passlib.exc.UnknownHashError. It appears you either have not set the lists moderator_password or you have not set it to a properly encrypted value. Did you set it and if so, how? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: Issues with cross posted emails after upgrading to mailman 3.3.6

by Mark Sapiro

On 11/7/21 5:19 PM, Simon Coggins wrote: > > > On 8 Nov 2021, at 11:11 am, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: > > I made a small change to defend against 'impossible' situations. See https://gitlab.com/mailman/mailman/-/merge_requests/933/diffs<https://gitlab.com/mailman/mailman/-/merge_requests/933/diffs> > > Thanks for the heads up. I did a bunch of testing with the original patch and was happy with it so we’re running that in prod now. How far off is 3.3.6? Just working out if I apply this slight change or wait for the full release. We don't have a specific release schedule. I think it could be several months before a 3.3.6 release. I don't think this change is critical. I was just considering 'what ifs' that actually shouldn't occur, but I suggest going ahead and applying the change. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] Re: Broken web UI after upgrade

by Mark Sapiro

On 12/16/22 21:47, Odhiambo Washington wrote: > On Fri, Dec 16, 2022 at 11:17 PM Mark Sapiro <mark(a)msapiro.net> wrote: >> >> I suggest you run >> ``` >> django-admin collectstatic --clear --noinput --verbosity 2 >> > > The output is here: https://pastebin.ubuntu.com/p/qkR2bDYv3G/ > > > >> django-admin compress --verbosity 2 >> > > The output of the above is here: https://pastebin.ubuntu.com/p/T7jQPrs3JX/ Those look OK. I suggest you look at ownership and permissions. ``` find /opt/mailman/mm/static/ -not -user mailman find /opt/mailman/mm/static/ -not -perm -u+rw find /opt/mailman/mm/static/ -type d -not -perm -u+x ``` and the same on /opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/ > If the above doesn't reveal anything substantial, then let me know and I > can bump up the verbosity. I don't know if --verbosity 3 will reveal anything or not. You could try. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: slow restart time for mailmanweb

by Mark Sapiro

On 12/28/21 3:51 PM, David Newman wrote: > On 12/28/21 1:20 PM, Mark Sapiro wrote: > > > If so, try adding > > > > KillSignal=SIGQUIT > > > > to the Service section and see if that fixes it. > > root@myhost:/etc/mailman3# time systemctl restart mailmanweb > > real 0m1.026s > user 0m0.008s > sys 0m0.004s > > My limited understanding of SIGQUIT is that it dumps core, but 'find / > -type f -name '*.core' did not return any core dumps from this event. Actually, SIGINT is probably better, but they should be equivalent. See https://uwsgi-docs.readthedocs.io/en/latest/Management.html#signals-for-con… and https://uwsgi-docs.readthedocs.io/en/latest/Management.html#stopping-the-se… I'll update the doc. > Still unsure why the service hung on stop, but thanks! It hung on stop because systemd wasn't told how to stop uwsgi so it sent a SIGTERM which doesn't stop it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

Search results for query "sapiro"