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

[MM3-users] Re: Emergency Moderation

by Mark Sapiro

On 5/25/20 8:21 PM, Allan Hansen wrote: > > Not sure what is the difference between ‘emergency moderation’ and ‘Hold for moderation.’ It appears redundant. `emergency` moderation is meant for emergencies such as flame wars on and otherwise open list. It trumps essentially everything else except pre-approval with and Approved: <password> header. It is not really intended as a "normal" list setting, although it can be used that way if you want to hold all posts. The default action "Hold for moderation" for members and non-members only applies to those whose individual moderation is set to "List default". To fully understand the difference, you have to know the order in which the various checks are applied. This is defined at <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/chains/builtin…>. You will see for example that emergency with a hold action comes before banned-address with a discard action. This means that if emergency is True, a post from a banned address will be held and not discarded, at least initially. -- 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: MM3 to MM3 migration

by Mark Sapiro

On 1/31/23 13:34, David Newman wrote: > > Is this really as simple as building the new server, creating the same > lists on the new server, and rsync’ing the archives from the old server? > If not, how to do the migration? If you want to mirror the entire installation, you can dump the databases off the old server and import them to the new server. Depending on the installation, everything may be in one database or there may be separate ones for mailman core and mailman web. This is a little tricky because some of the tables have to do with Django stuff. To do only selected lists is much more difficult and there are no scripts that I am aware of. HyperKitty can dump a list's archive as a mbox which could then be used as input to hyperkitty_import on the new server to move archives, but there are no similar scripts to dump list settings, users, memberships, etc. in a format that can be imported. -- 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: Moderated unsub requests are not provided by mailman3 service

by Mark Sapiro

On 11/29/24 4:47 PM, Joachim Schrod wrote: > > The unsubscriptions requests are not shown in the web interface. I > suppose they should appear in the UI section "Subscription requests", > either as "Pending Approval" or "Pending Confirmation". (Frankly, I > don't understand the difference between these two options at all.) Subscriptions pending confirmation are those waiting for the user to confirm. Those pending approval are waiting for moderator approval. Unsubscription requests not being shown is https://gitlab.com/mailman/postorius/-/issues/332 which was fixed in Postorius 1,3.6 released over 3 years ago. Current release is 1.3.13. > System information: mailman3 3.3.3; Postorius (mailman3-web) 1.3.4; > both on Debian 11 (bullseye). > > I know that this is out of date; thus a definitive info "this is fixed > by now" is quite OK for me. (Debian upgrade is planned as the next > action after getting Mailman3 to work for that use case.) Yes, this is fixed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Re: Errors in MM3

by Mark Sapiro

On 4/7/25 04:08, Odhiambo Washington via Mailman-users wrote: > I am using uwsgi+APache2. > I am suddenly seeing hundreds of errors in my mailmanweb and uwsgi logfiles: > > 1. mailmanweb.log has hundreds of such lines: > [WARNING] [2025-04-07 13:01:50,162] [log] 317562 139768548886080 Method Not > Allowed (GET): /archives/list/ > kictanet@lists.kictanet.or.ke/message/YOPKCEWPHX4BV7U5MOTCVCNSWR2J2JOZ/vote ... > [WARNING] [2025-04-07 13:02:37,567] [log] 317562 139768548886080 Method Not > Allowed (GET): /archives/list/ > kictanet@lists.kictanet.or.ke/thread/MICNFIHVLOETVE4PXEDO5MBYWG7SN57H/favorite ... > > Any clues as to what needs to be done to mitigate the above? A web crawler is issuing GETs for those URLs which only allow POST. If you look in your web server logs, you can find the IPs they are coming from. If it's only a few, you can block them with a firewall or using access controls in your web server. If its a compliant web crawler, you may be able to use robots.txt to stop it. Also see https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

[MM3-users] Re: Hyperkitty archive: date format in thread overview of list does not honor DATETIME_FORMAT of settings.py

by Mark Sapiro

On 5/24/25 5:04 AM, Stephen J. Turnbull wrote: > Christian Schneider writes: > > > In settings.py I set DATETIME_FORMAT to 'd-m-Y H:i:s' but the > > format did not change. > > I'm not sure what DATETIME_FORMAT is used for in Django 3.x. I doubt the OP is using Django 3.2. I suspect the URL <https://docs.djangoproject.com/en/3.1/ref/settings/#std:setting-DATETIME_FO…> came from a search result and the OP actually has Django 4.2 or 5.0 (django_mailman3 >= 1.3.12 requires django>=4.2,<5.1). Note that the doc for DATETIME_FORMAT for Django >=5.0 removes the note about USE_L10N = True and says "Note that the locale-dictated format has higher precedence and will be applied instead." Thus, with Django >= 5.0 I think the setting for DATETIME_FORMAT is ignored for output and the locale's format is used in all cases. -- 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: Cannot Create New List

by Mark Sapiro

On 11/8/25 12:45, dap1--- via Mailman-users wrote: > <venv> $ ls -l /etc/mailman3 > total 20 > -rw-rw-r-- 1 mailman mailman 490 Nov 1 14:53 gunicorn.py > -rw-rw-r-- 1 mailman mailman 841 Oct 19 11:35 mailman.cfg > -rw-rw-r-- 1 mailman mailman 87 Oct 18 17:37 mailman-hyperkitty.cfg > drwxrwxr-x 2 mailman mailman 4096 Nov 4 14:11 __pycache__ > -rw-r--r-- 1 root root 2875 Nov 4 14:10 settings.py > > I don't suppose settings.py is the problem. Is there a place to change that path somewhere? There is no need to change that path. Django is getting it correctly per your reply about mailman-web diffsettings|grep DATABASES You could sudo chown mailman:mailman /etc/mailman3/settings.py but it's world readable so that isn't needed. > I wonder if it would be easier to blow the whole thing away and start over. At one point that was probably true, but you're almost there. See 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

9 months, 1 week

[MM3-users] Re: MM3 on debian - redirect problem

by Mark Sapiro

On 4/27/20 8:17 AM, Gelpi Andrea wrote: > Hi, > on a debian10 I have mm3 installed via apt-get > > apt-get install mailman3-full > dpkg-reconfigure mailman3 > dpkg-reconfigure mailman3-web > > I have this minor issue > > https://webserver/mailman3 redirects to > http://webserver/mailman/postorius/lists/ > > that doesn't exist. > > The same problem form django admin page to return to lists > > https://website/mailman3/admin/sites/site > > In the upper right corner I have a link to https://webserver/mailman3 > that redirects to https://mailman/postorius/lists/ > > I searched for a redirect but without success. The redirection must be a web server issue. There is a urls.py file probably in the same directory as your django settings - probably /usr/share/mailman3-web/urls.py in your case. You can make a URL like http://webserver/mailman/postorius/lists/ work by adding url(r'^mailman/postorius/', include('postorius.urls')), to the urlpatterns list in the urls.py file. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

[MM3-users] Re: Errors while importing mm2 list archives - SOLVED

by Mark Sapiro

On 12/20/22 06:48, Odhiambo Washington wrote: > > There is a WARNING on > https://docs.list.org/en/latest/install/virtualenv.html#virtualenv-install > which says one must create the config file as /etc/mailman3/mailman.cfg > How to force mailman to read that file is something I haven't understood, > but turns out to be what has taken me days trying to get things right. If you run the `mailman` command without any -C option, it will look for a config in /etc/mailman3/mailman.cfg > Ultimately, when I did the import, there was only one email from the > archives that failed to be imported - which I honestly don't mind, but > maybe there is a solution for this > "'utf-8' codec can't encode character '\udcae' in position 331: surrogates > not allowed" ?? If you provide a copy of that message from the mbox, either on the list or to me directly, I'll investigate. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: Change delivery_status of a member by using the rest api

by Mark Sapiro

On 5/4/23 12:30, Michael Schaarschmidt wrote: > Hello, > > I would like to set or change the delivery_status of a list member by > using the rest api. The curl request looks like > > curl \ > -X PATCH \ > -H "Content-Type: application/json“ \ > -H "Accept: application/json“ \ > -u restadmin:secret_password \ > -d "@./foo_patch.json“ \ > "http://127.0.0.1:8001/3.1/members/ebcdd09bb8d84758a135c3449023701e“ > > With the json-file: > > { „delivery_status“: „by_user“ } I assume those fancy quotes are an artifact of your mail client. > I get an error message: > > {"title": "400 Bad Request", "description": "Unexpected parameters: > delivery_status“} > > > Is there a way to change the attribute `delivery_status` of an existing > member by using the rest api? You can't set a memnber's delivery status directly. It is an attribute of the member's preferences. The correct endpoint is "http://127.0.0.1:8001/3.1/members/ebcdd09bb8d84758a135c3449023701e/preferen…" -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: Problems with mailman core translation and other details

by Mark Sapiro

On 2/6/24 2:41 PM, celi--- via Mailman-users wrote: > It´s the case below: the pair msgid/msgstr seems to be OK, but this particular sentence is not being translated. > > #: templates/postorius/lists/summary.html:88 > #, python-format > msgid "" > "\n" > " To subscribe you can send an email with 'subscribe' in the" > "subject to\n" > " <a href=\"mailto:%(address)s?subject=Subscribe\">" > "%(address)s</a>\n" > " or use the form below:\n" > "" > msgstr "" > "\n" > " Para se inscrever você pode enviar um e-mail com o assunto" > "'subscribe' para\n" > " <a href=\"mailto:%(address)s?subject=Subscribe\">" > "%(address)s</a>\n" > " ou use o formulário abaixo:\n" > > What am I doing wrong? Or what can I do to make things suitable? Is the rest of that page translated appropriately? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

Search results for query "sapiro"