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

[MM3-users] Re: Cron Error: <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs monthly

by Odhiambo Washington

On Fri, Feb 3, 2023 at 3:23 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/2/23 04:26, Odhiambo Washington wrote: > > > > Okay. This is a bit off from my understanding. > > > > What is the cause and how do I mitigate it? > > The cause is the monthly hyperkitty update_and_clean_index job runs for > a long time, i.e. hours, because it is rebuilding the entire search > index so during the time it's running multiple hourly hyperkitty > update_index jobs are started and they are competing for the same lock. > > See > > https://gitlab.com/mailman/hyperkitty/-/blob/master/example_project/setting… > for mitigation. What is the danger of replacing my settings.py with this one, seeing as it differs in a number of ways with mine? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 8 months

[MM3-users] Re: Subscription requests = 0 ? Bug or feature?

by Odhiambo Washington

On Fri, Mar 24, 2023 at 6:59 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/24/23 04:15, Odhiambo Washington wrote: > > Even though I have a "Pending confirmation" request, the total entries > > under the subscription requests reads zero. > > I thought it should read whatever the total of (pending confirmation + > > pending approval) is. > > It only counts the requests waiting moderator approval because this is > the number requiring moderator action. It doesn't count the requests > waiting user confirmation. The only reason these are even available in > the moderator interface is so the moderator can discard them in cases > where the user has lost the confirmation email and can't confirm and > can't subscribe again because of the pending confirmation. > Thank you for the explanation. The logic is justified. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 7 months

[MM3-users] Re: mailman3 postorius cannot retrieve template

by Wolfgang Bock

Hello Mark, I reconstruct the configuration problems regarding the creation of templates in mm3: I installaed mailman3 via the debian bullseye package(s). BTW: My experience is to install it step by step, not as mailman3-full, but as mailman-3, mailman3-doc, mailman3-web and python3-django-mailman3. In my case the full installation did not run clean, the step-by-step variant run clean. The debian bullseye variant comes with a nginx conf-file in /etc/mailman3/nginx.conf ... # This nginx config file is part of the mailman3-web package. # # This nginx configuration file is a vhost configuration. ... # Nginx SSL snippet. To enable it, please uncomment and update the server_name and the ... server { listen 443; listen [::]:443; server_name mailman.example.com; server_tokens off; # # ## Strong SSL Security # ## https://raymii.org/s/tutorials/Strong_SSL_Security_On_nginx.html & https://cipherli.st/ ssl on; ssl_certificate /etc/letsencrypt/live/mailman.example.com/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/mailman.example.com/privkey.pem; # ... The configuration "ssl on" is outdated as nginx -t comments. The actual configuration should be: /etc/nginx/ /etc/nginx/sites-available/nginx.lists.mydomain.ssl (and /sites-enabled) .... server { listen 443 ssl http2; listen [::]:443 ssl http2; server_name lists.mydomain.com; # for example server_tokens off; ssl_certificate /etc/letsencrypt/live/mydomain.com/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/mydomain.com/privkey.pem; ... If you - as proposed in the mailman3 nginx.conf - include in nginx.lists.mydomain.ssl the following: .... upstream mailman3 { server unix:/run/mailman3-web/uwsgi.sock fail_timeout=0; } .... you cannot in include this in another vhost-nginx configuration (for example): /etc/nginx/sites-available/nginx.lists.mydomain_2.ssl as nginx -t says something like "no double entries please". So I put this in another file like /etc/nginx/sites-available/nginx.00.mailman3.upstream (and via symlink in .../enabled/...) and both nginx-domain-files work. The debian bullseye also serves a file mailman-web.py with an entry ... POSTORIUS_TEMPLATE_BASE_URL = 'https://localhost/mailman3/' ... As mentioned in a mail before that could not work: 1. letsencrypt doesnt serve an entry match for localhost. That floods your syslog. 2. "localhost" doesnt match with the nginx.conf-proposal. It must be something like /etc/mailman3/mailman-web.py .... POSTORIUS_TEMPLATE_BASE_URL = 'lists.mydomain.com/' .... In this combination the creating of templates on the postorius website works. My conclusion: I ask you to consider these experiences in an update for the mailman3 packages in debian bullseye. It would save time, questions and nerves. Regards Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Dienstag, 2. November 2021 23:44 An: mailman-users(a)mailman3.org Betreff: [MM3-users] Re: mailman3 postorius cannot retrieve template On 11/2/21 3:28 PM, Wolfgang Bock via Mailman-users wrote: > > I get an db-entry in the mailman3 table template which doesnt lead to > a suitable link: > https://localhost/postorius/api/templates/list/testliste01.mydomain.de/list: > member:regular:footer > > In the next stept it leads to a flood of entries in my syslog because > django is asking for a certificate match for "localhost": > Nov 2 11:47:49 myserver mailman3[175334]: Nov 02 11:47:49 2021 > (175334) Certificate did not match expected hostname: localhost. Certificate: ... > > Letsencrypt cannot deliver this match for "localhost", it is > impossible to configurate letsencrypt to do so. > > The running script must create a postgres INSERT database command > which includes the correct domain-name including the correct path > .../mailman3/api/templates .... and not ... postorius/api/.... > > I dont know, where is the place to correct this. > - in mailman-web.py ?? > ... > ALLOWED_HOSTS ... '*' > or > MAILMAN_REST_API_URL = 'http://localhost:8001' > or > POSTORIUS_TEMPLATE_BASE_URL = 'https://localhost/mailman3/' If you normally access Postorius on your site at something like https://www.example.com/postorius, than set that as POSTORIUS_TEMPLATE_BASE_URL -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

3 years, 11 months

[MM3-users] Re: search this list searches more then just this list

by Marco van Tol

Yes, thank you! I’ll have a look into changing our backend to Xapian. Hopefully it will be trivial :) Marco van Tol > Op 16 jan 2024, om 09:20 heeft Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> het volgende geschreven: > > Mark Sapiro writes: > >> I have tested and I can confirm that with two lists in the same >> domain named `test` and `x-test` and with Whoosh as the backend >> searching the `test` list returns hits from both lists, but with >> Xapian as the backend, only hits from the `test` list are returned. > > Wow! Thanks, Mark! > > Steve > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to mvantol(a)ripe.net >

1 year, 9 months

[MM3-users] Re: Sign and encrypt e-mail responses

by Markus Grandpre

Dear Mark, thank you very much for your response. Is there already a way to enable signing in Mailman v3.3.8 / v3.1 or does the signing support still have to be implemented? Best regards, Markus Grandpré Am 6/3/24 um 18:51 schrieb Mark Sapiro: > On 6/2/24 11:51 PM, Markus Grandpré wrote: >> Dear List, >> >> is it possible to sign and encrypt all e-mail responses from the Mailman3 server with a digital certificate? > > > Not without significant code changes. Signing alone should not be difficult. Encryption is more difficult if the > recipients are going to be able to read the encrypted mail without access to the server's private key. This would > require mail to be personalized, which digests currently aren't, and encrypted with the recipient's public key which > requires the server to have all those keys. > -- Markus Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur, Tel: ++49 7531 88 4342

1 year, 4 months

[MM3-users] Re: Pd CRON mailman gatenews

by Pierre Malard

Hi Mark, Thanks for your answer and your lead > Le 16 mars 2023 à 18:34, Mark Sapiro <mark(a)msapiro.net> a écrit : > > On 3/15/23 23:31, Pierre Malard via Mailman-users wrote: > >> File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 502, in _read >> with open(self._lockfile) as fp: >> PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/locks/dbcreate.lck' >> —————————————————————————————————————————————————— >> CRON content: >> —————————————————————————————————————————————————— > ... >> # Every 15 minutes, gate messages from usenet to those lists which have the gateway configured >> */15 * * * * list if [ -x /usr/bin/mailman ]; then /usr/bin/mailman gatenews; fi > > Do you have any list's for which Gateway to mail is set to yes or for which there is a Linked Newsgroup?. If not, running gatenews is superfluous. No, we don’t have > >> I thought, given the last line, a problem of rights. It is not the case ! The directory and the files contained in /var/lib/mailman3/locks belong to the user "list". >> When I run "/usr/bin/mailman gatenews" by hand everything is correct. > > Can you do `sudo -u list cat /var/lib/mailman3/locks/dbcreate.lck`. If that succeeds, this may be a SELinux or other security manager issue. Their is no file with this name! listesman:~# ls -ld /var/lib/mailman3/locks/dbcreate.lck ls: impossible d'accéder à '/var/lib/mailman3/locks/dbcreate.lck': Aucun fichier ou dossier de ce type > > >> The questions I have are these: >> We have 8000 files "dbcreate.lck..." in the directory "/var/lib/mailman3/locks". >> What are they for? >> Can we delete them? > > They are probably all orphaned lock files due the the gatenews failure. To be certain that none are current you could stop Mailman core. Then with Mailman core stopped, any files in /var/lib/mailman3/locks are orphaned and should be removed. Ok, is done. We will see today if it continues > >> We have 2 files "master.lck..." dated from the day after tomorrow ! >> What is this date? >> Aren't these files the problem? > > > Those files are normal. They are the master lock that prevents Mailman core from being started when it's already running. The future date is the way flufl.lock handles lock lifetimes. Locks when set have a lifetime, after which they can be broken. This is implemented in flufl.lock by setting the file's date that far into the future. Ok, that’s smart :-) > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to plm(a)teledetection.fr -- Pierre Malard Responsable architectures système CDS DINAMIS/THEIA Montpellier IRD - UMR Espace-Dev - UAR CPST - IR Data-Terra Maison de la Télédétection 500 rue Jean-François Breton 34093 Montpellier Cx 5 France « Je n'ai jamais séparé la République des idées de justice sociale, sans laquelle elle n'est qu'un mot » Jean Jaures - 1887 |\ _,,,---,,_ /,`.-'`' -. ;-;;,_ |,4- ) )-,_. ,\ ( `'-' '---''(_/--' `-'\_) πr perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-. ;-;;,_: |,A- ) )-,_. ,\ ( `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"' `-'"'"'\_): 24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print' - --> Ce message n’engage que son auteur <-- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

2 years, 7 months

[MM3-users] Re: Feature request, hyperkitty, low volume lists

by Alain D D Williams

On Thu, Jan 09, 2025 at 10:19:17AM -0800, Mark Sapiro wrote: > This is a long standing issue. See > https://gitlab.com/mailman/hyperkitty/-/issues/79 Thanks > > For an example see: > > > > https://fridayfolk.phcomp.co.uk/mailman3/hyperkitty/list/announce@fridayfol… > > The style of this page is not standard. Is this a downstream packaged > HyperKitty? See > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/2025/1/ > for the standard page or > https://mail.python.org/archives/list/mailman-i18n@python.org/2024/12/ for > one with no posts. I installed from the Debian repositories as it seemed more straightforward than following the instructions on the mailman project. But it has left me running code that is ~2 years old. I might try to migrate at some point. -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

9 months, 2 weeks

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

by Odhiambo Washington

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* > >> > >> > >> > >> Did you check the permissions on your sass binary? > >> > > > > My mailman installed in /opt/mailman/mm > > > > find /opt/mailman/ -type f -name sass > > > > yielded nothing! > > > > 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. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

4 years, 5 months

[MM3-users] Re: Recommended way to backup a mailman3 instance

by Gilles Filippini

Andrew Hodgson a écrit le 18/04/2020 à 12:26 : > Mark Sapiro wrote: > >> On 4/17/20 4:51 PM, Abhilash Raj wrote: >>> >>> If they are empty, perhaps the digest creation process should just re-create them instead of failing to create/send digests? We don't really need the directory structure to exist. > >> I created <https://gitlab.com/mailman/mailman/-/issues/699> for this. > > In my situation I noticed the directories weren't created very quickly as my Exim config looks for the list directories to identify whether that address exists. I don't know how Postfix does the aliasing but for my case it would make sense to get the directories created as soon as possible, not sure if the digest handler would be soon enough or not. There is no need for these directories on the Exim side actually. You can safely drop the related checks from the Exim configuration [1]. [1] https://github.com/maxking/docker-mailman/pull/371 _g.

5 years, 6 months

[MM3-users] Re: Chinese characters in list name shows question mark (?)

by Franklin Weng

Franklin Weng 於 2019/10/24 上午8:05 寫道: > Hi Mark, > > Thanks for your reply. > > Mark Sapiro 於 2019/10/24 上午6:10 寫道: >>> Is there any other setting I should look at? >> The list's preferred_language setting (Postorius -> Settings -> List >> Identity -> Preferred Language. The list welcome message is encoded in >> Mailman's character set for the list's preferred_language. If this is >> English (USA), the character set is us-ascii. If it is set to Chinese >> (Taiwan), the character set is utf-8, and it should work. > However in my settings -> List Identity page I didn't see Preferred > Language option. > > https://nextcloud.slat.org/index.php/s/45tGaE7ALgAFQFK > > What may be possible wrong that I couldn't see Preferred Language > settings in the web interface? I got it. It is implemented in postorius 1.2.5 but my Debian buster contains 1.2.4-1 for now. Franklin

6 years

Search results for query "sapiro"