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

[MM3-users] Re: Configure new list via REST API - trying to add moderators

by Mark Sapiro

On 9/12/24 06:08, Andy Matthews wrote: > Unfortunately no. What is different between what I show at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and what you are doing? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: CSV import for mass subscription

by Mark Sapiro

On 9/20/24 01:44, Odhiambo Washington via Mailman-users wrote: > > I believe the link to make feature requests is > https://gitlab.com/mailman/mailman/-/issues/?label_name%5B%5D=feature%20req… Actually, that URL will produce a list of current issues which are tagged `feature request`. To submit a new one, go to https://gitlab.com/mailman/mailman/-/issues/new and create the issue and tag it as a feature request. -- 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: CSV import for mass subscription

by Mark Sapiro

On 9/20/24 01:26, Markus Grandpré wrote: > Dear list, > > we noticed that there is a function to convert the member list into a > CSV format and save it.Therefore, we would like to know if the > implementation of a CVS import for mass subscription is already planned? > If not, how can we submit a corresponding feature request? The exported CSV is just a list of email addresses, and that could be easily just pasted into the mass subscription form. -- 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: CSV import for mass subscription

by Mark Sapiro

On 9/20/24 12:00, Odhiambo Washington via Mailman-users wrote: > > Why was it called a CSV? Appropriateness or future plans to download a true > CSV? It is a CSV, albeit with only one column. It was implemented by <https://gitlab.com/mailman/postorius/-/commit/f9121a7afca0e0d4aac49509598b2…>. You'd have to ask the author if anything further was planned. -- 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: Migrating archives from Mailman21 to Mailman3

by Mark Sapiro

On 9/24/24 05:49, Markus Grandpré wrote: > Dear List, > > I have a question about migrating archives from Mailman21 to Mailman3: > Is it possible to migrate only the archive of a list, but not the list? Yes. There is no requirement that archives have a matching list in Mailman core. -- 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: Can we let member moderation settings be considered after the header filters let the message through?

by Mark Sapiro

On 9/24/24 01:52, Marco van Tol wrote: > > Is there any way we can discard spam messages from members before they > become moderated? This is fixed by https://gitlab.com/mailman/mailman/-/merge_requests/1237 (released in Mailman core 3.3.10b1). Headel filters are now checked before emergency, member and nonmember moderation. -- 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: Migrating archives from Mailman21 to Mailman3

by Mark Sapiro

On 9/28/24 08:00, Odhiambo Washington via Mailman-users wrote: > > My thinking around the above was that `foo-list(a)example.com` refers to a > Mailman list. > But now I am beginning to think that it's only a listname for HyperKitty > and the list doesn't necessarily have to exist in Mailman Core. > Is that right? Yes. -- 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: makemigrations --merge error after Debian upgrade

by Mark Sapiro

On 10/1/24 06:46, Chupin Maxime via Mailman-users wrote: > Thanks. > Unfortunately, whereas TIMEOUT is set to 59 and RETRY to 60, I still get the warn... Very weird. We recommend Q_CLUSTER = { 'timeout': 300, 'retry': 360, 'save_limit': 100, 'orm': 'default', } -- 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: makemigrations --merge error after Debian upgrade

by Mark Sapiro

On 10/1/24 06:49, Chupin Maxime via Mailman-users wrote: > Thank you, but still asking for Password to execute mailman-web... Look at the contents of the mailman-web script. My guess is it contains `sudo -u list ...` -- 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: makemigrations --merge error after Debian upgrade

by Mark Sapiro

On 10/2/24 05:58, Chupin Maxime via Mailman-users wrote: > Tried to add these lines before the test in the `conf.py`and nothing changes. Should I remove the test on TIMEOUT ? You should be reporting these issues (this and the migrations issue) to Debian. We don't know how to deal with Debian packaging issues. -- 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"