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

[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, 7 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, 6 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

10 months, 1 week

[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

5 years, 5 months

[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

4 years, 5 months

[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, 4 months

[MM3-users] Re: Core, Hyperkitty and Postorius releases

by Mark Sapiro

On 5/14/21 12:50 PM, Odhiambo Washington wrote: > On Fri, May 14, 2021 at 7:04 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 5/14/21 5:02 AM, Odhiambo Washington wrote: >>> On Fri, May 14, 2021 at 2:52 PM Jeff Steele <jeff(a)steele.com> wrote: >>> >>>> >>>> >>>> On May 14, 2021, at 7:49 AM, Odhiambo Washington <odhiambo(a)gmail.com> >>>> wrote: >>>> >>>> /bin/sh: sass: Permission denied* ... >> Try `which sass` >> > > root@gw:/usr/home/wash # su mailman3 > (venv) [mailman3@gw /usr/home/wash]$ which sass > (venv) [mailman3@gw /usr/home/wash]$ > > There is no sass. There has to be. You can't get a permissions error on sass if it doesn't exist (well, maybe if you don't have permission to search a superordinate directory, but that's unlikely). Try `find /usr -name sass` -- 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: Which crontab?

by Mark Sapiro

On 11/06/2017 08:52 AM, Mark Sapiro wrote: > On 11/05/2017 09:18 PM, Pierre Abbat wrote: >> >> /etc/mailman.cfg should be owned by mailman? I checked my primary mailserver, >> my laptop, and my new Mailman box. ALL files in /etc (except links, which are >> lrwxrwxrwx and I didn't check what they point to) are owned by root.root or >> owned by root.<other> and not group writable, except one, the directory /etc/ >> mailman/, which is owned by root.list and is group writable (drwxrwsr-x). Are >> you saying that Mailman should be able to change its own config file? > > > It looks like your Mailman user is 'list'. That is the user that should > be running mailman commands. This may be "off the wall" but is the mailman you installed perhaps a Debian/Ubuntu Mailman 2.1 package? If so, you are reading the wrong docs and posting to the wrong list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 8 months

[MM3-users] Re: Member Issue Discovered

by Mark Sapiro

On 10/23/20 1:13 PM, Brian Carpenter wrote: > > On 10/23/20 1:04 PM, Mark Sapiro wrote: >> >> Everyone who is or has been a member, non-member, owner or moderator of >> a list has a user and one or more address records in Mailman core. > > And those records are kept in the database? Is that correct? Yes, the user record is in the `user` table and the address record(s) are in the `address` table. You can query these and create users and addresses via REST. You can also PATCH user attributes via REST, but not (yet) address attributes. >> Here's a take on this that is intended to be humorous, but is actually >> quite frightening. https://xkcd.com/2347/ > > I actually came across that cartoon months ago and that one person > reminded me of you. So the fact that you are sharing that cartoon is > ironic and very funny! Yes, quite. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Configuring the List-Archive and Archived-At headers

by Mark Sapiro

On 3/20/19 6:50 PM, Mark Sapiro wrote: > On 3/20/19 5:43 PM, Ralph Seichter wrote: >> With archiving enabled, mail is sent with headers like the following: >> >> Archived-At: <https://example.com/hyperkitty/list/foo-users@lists.example.com/message/ABC/> >> List-Archive: <https://example.com/hyperkitty/list/foo-users@lists.example.com/> >> List-Post: <mailto:foo-users@lists.example.com> >> List-Subscribe: <mailto:foo-users-join@lists.example.com> ... > What that means is the lists.example.com domain must first be known to > Django at <https://lists.example.com/admin/sites/site/ > > Then at https://lists.example.com/postorius/domains/, the Web Host for > the example.com domain needs to be lists.example.com I didn't look carefully enough at your example. If the mailto: links are @lists.example.com, then that is the Mail Host at https://lists.example.com/postorius/domains/ for which the Web Host needs to be lists.example.com. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

Search results for query "sapiro"