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

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

by Alain D D Williams

On Thu, Jan 09, 2025 at 09:06:56AM -0800, Mark Sapiro wrote: > On 1/9/25 06:07, Alain D D Williams wrote: > > > > For an example see: > > > > https://fridayfolk.phcomp.co.uk/mailman3/hyperkitty/list/announce@fridayfol… > > The above URL and also https://fridayfolk.phcomp.co.uk/mailman3/hyperkitty/list/announce@fridayfol… > and even https://fridayfolk.phcomp.co.uk/mailman3/hyperkitty/ all give a 500 > internal server error response. Sigh - try again. The 500 error happens several times a day. After 5 minutes it behaves as it should ... until it happens again some time later. I have not found out what is happening; nothing obvious in the logs, not high system load. I can live with it for now as I am busy elsewhere. -- 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>

1 year, 2 months

[MM3-users] Re: Reset bounce count in MM3

by iMark

>> On 3/8/26 17:20, iMark wrote: >> Is there an equivalent of Mailman 2's "bin/reset_bounce.py" in Mailman >> 3 ? ================= > On 2026-03-09 01:43, Mark Sapiro wrote: > reset_bounce.py is not part of Mailman 2.1. It is one of my scripts > <https://www.msapiro.net/scripts/reset_bounce.py>. Currently there is > no Mailman3 equivalent. It wouldn't be hard to make one, but I haven't > done so yet. ================= Thanks for that info (and thank you for the MM2 reset_bounce.py script). I can see on a MM3 list's administration panel that a member has a bounce count of 4. When I query the "bounceevent" table in the mailman database ... SELECT * FROM mailman.public.bounceevent WHERE list_id = '<MY_LIST_ID>' AND email = '<MEMBERS_EMAIL_ADDRESS>' ... the result is only 2 records from the last 24 hours. It appears that the table only stores 24 hours worth. So I figure I'm looking in the wrong place. Where should I be looking?

4 weeks, 1 day

[MM3-users] Re: changing the main template for subscriptions and more

by Andreas Barth

* Mark Sapiro (mark(a)msapiro.net) [210622 14:22]: > It isn't necessary to patch the source in this way. If you put the > modified templates in Mailman's var/templates/site/de/ directory, > ensuring that the Mailman user can read them, they will be used and > you won't have to patch the source every time you upgrade. Thanks Mark for pointing that out. I also should have mentioned that this would be the recommendation for operations, especially if mailman is install by some normal means (pip, distribution packages, etc). I perhaps took it for granted too much to never touch files coming out of automated systems by hand (except where the automated system caters for, e.g. debian conffiles), because that is a sure way to get into trouble with the next upgrade. (My mailman installation is the exception and not the rule, so unless you know what you're doing and have done similar before, just follow Marks advice) Andi

4 years, 9 months

[MM3-users] Re: AttributeError: ,> 'ReopenableFileHandler' object has no attribute '_stream'

by David Newman

On 11/19/21 10:04 PM, Mark Sapiro wrote: >> but then mailman3 wanted me to create a bunch of directories under >> /etc, even though $var_dir was set to /var/lib/mailman3. Things seem >> to go better, except for the confusion between lists/mailman >> ownership, when I set layout to "debian", which was the default. > > > It seems you may be using the Debian packages as our source has no > `debian` layout. Thank you for spotting that. I'd cloned a test server from a production machine that did have the Debian mailman3 package installed, something I should have checked first. The rest of the installation went OK. I'm using MariaDB and not Postgres, and that required a few deviations from the Virtualenv Installation documentation, but those tweaks things went OK from there. I have a follow-up question about post-installation setup but will start a new thread for that. Thanks again! dn

4 years, 4 months

[MM3-users] Re: re-sending confirmation mails (was Re: Re: pending subscriptions lost?)

by Andreas Barth

* Mark Sapiro (mark(a)msapiro.net) [220315 23:31]: > I understand that, but even Debian sid has mailman3 3.3.3-1 and > mailman3-web 0+20200530-2 which are quite old for a package like > Mailman 3 which is still in active development. If we speak about unstable, that's something else. However, Debians next stable release won't release with mailman 3.3.3, as this package is removed from testing at the moment. I'd be happy if someone would update this package, however, I don't think I should get myself also involved there. ('Removed from testing' means: the current unstable package is considered not to be in shape to be released with the next stable release). So, if someone wants to get involved into Debian package maintainership with mailman3 (and related packages), that would be great, and I'm happy to support. As said, the most easiest way to get things fixed in Debian is by doing it. Andi

4 years

[MM3-users] Re: Mailman web interface / uwsgi

by Jan Eden

On 2022-11-27 07:08, Mark Sapiro wrote: > On 11/27/22 00:19, Jan Eden via Mailman-users wrote: > > > > I see. But the mailman.cfg is placed in /etc/mailman3, and this file > > also belongs to the core, doesn't it? In any case, I changed the > > configuration parameter for [archiver.hyperkitty] as you suggested and > > all settings are in one place now. > > > In that case, it's probably just an oversight. The instructions at > https://docs.mailman3.org/en/latest/install/virtualenv.html are an evolution > of a process that started with an obsolete mailman-bundler package, the > initial iterations of which are documented at > https://wiki.list.org/x/17891998 and prior revisions of that page. > https://docs.mailman3.org/en/latest/install/virtualenv.html is still a work > in progress. Ok – as long as I can consolidate all settings in one place for backup purposes (with symlinks, if need be), any layout is fine. Thank you, Jan

3 years, 4 months

[MM3-users] Re: RemoteUserBackend for Mailman3?

by Markus Grandpré

Dear Mr Spiro, thank you so much for your reply. On my Debian 11 system I don't find 'django_mailman3.lib.auth.fedora' in my Django settings in </usr/lib/python3/dist-packages/django/conf/global_settings.py>: # List of strings representing installed apps. INSTALLED_APPS = [] But I find: INSTALLED_APPS = ( ... #'django_mailman3.lib.auth.fedora', ... ) in </etc/mailman3# less mailman-web.py>. After commenting this line out I restarted the mailman3 application by restarting the apache2 web server. Unfortunately, the Fedora button is still visible on login site of mailman3 and a server error occurs when I click the button. Best regards, Markus On 27.03.23 19:22, Mark Sapiro wrote: > On 3/27/23 06:00, Markus Ludwig Grandpré wrote: >> >> Btw. how can I disable and remove the Fedora button from Maliman3's >> login page? > > > remove 'django_mailman3.lib.auth.fedora' from INSTALLED_APPS in your > Django settings. > -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

3 years

[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/

4 years, 5 months

[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 '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 2 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 '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years

Search results for query "sapiro"