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

[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, 10 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, 8 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

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

[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

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

4 years, 2 months

[MM3-users] Re: Phantom Email Address in Nonmember List

by Mark Sapiro

On 9/18/24 09:35, Steve Brown via Mailman-users wrote: > Mark Sapiro wrote: > >> Are you saying that the bounce+... address ends up as a nonmember of >> the list you are sending to. I don't think that should happen. Actually, it should. See below. > Yes, that is what is happening, but only for messages from the steve@stevebrown address. There are two things involved here. First, messages From: the steve@stevebrown address have the bounces+... address as the envelope sender. And, if a post is not from a member or is from a member whose moderation_action is defer, all of the message's senders including the envelope sender who are not yet members or nonmembers of the list will be added as nonmembers. Thus, given that the envelope sender of messages From: the steve@stevebrown address is the bounces+... address, that address will be added as a nonmember. This is expected -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: Cannot setup announce-only mailing list

by Mark Sapiro

On 2/1/20 9:53 AM, Abhilash Raj wrote: > > > On Thu, Jan 30, 2020, at 9:58 AM, Mark Sapiro wrote: >> >> In short, you need to set this up manually using things like moderation >> settings and custom templates for the welcome message. > > Mark, do you think we should make the actual announce-only style reflect > these settings so folks don't have to manually set these after they create > a announce-only list? > > I am not sure the reason behind these settings lacking for the current > announce-only style. Are there situations where announce-only list would > have different list setting? I think it was probably done as it is just as a start. I do think it would be good to set more things appropriately for the announce-only style, ultimately we may need to add templates for post rejection notices and things like that. -- 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: spanish localization

by Mark Sapiro

On 2/12/21 12:04 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > On 11/2/21 20:15, Mark Sapiro wrote: >> >> For the web UI you need to run the django management `compilemessages` >> command. > > I tried to run this using the same command as I did for the > "collectstatic" (that solved all my previous problems for the upgrade) > and "migrate" runs but it shows me an error: > > su -m mailman3 -c "python3 manage.py compilemessages" > CommandError: This script should be run from the Django Git checkout or > your project or app tree, or with the settings module specified. The documentation is at, e.g., https://docs.djangoproject.com/en/3.1/ref/django-admin/. If the manage.py in the directory in which you ran this is the correct one for your Mailman Django project, I don't know why it didn't work. Is your Mailman installed in a virtualenv? If so, was the virtualenv activated? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: Moderate mails from owner

by Mark Sapiro

On 3/22/19 6:17 AM, Malcolm Austen wrote: > On Thu, 21 Mar 2019 17:27:01 -0000, Mark Sapiro <mark(a)msapiro.net> wrote: >> >> New (non-)members always have Moderation set to List default. This means >> their posts are governed by the applicable Settings -> Message >> Acceptance settings. > > I suspect that everyone on the rootsweb system was mistakenly set to > 'Default processing' when they were bulk-imported from Mailman2. It wasn't a mistake. When I said "New (non-)members always have Moderation set to List default." I was thinking only of members being added to a list in any of the 'usual' ways, not members imported from Mailman 2.1. When members are imported from Mailman 2.1 by the 'mailman import21' command, the MM 3 moderation setting for the member is set to Default Processing if the MM 2.1 member is not moderated and otherwise is set based on the MM 2.1 member_moderation_action setting. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 11 months

Search results for query "sapiro"