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

[MM3-users] Re: Mass change Digest delivery mode

by Stephen J. Turnbull

Mark Sapiro writes: > It looks like your line breaks are not correct. Indeed. "Modern" MUAs are often not useful for copy and pasting code. > It appears the 'from' is missing That was me. Thanks for fixing! -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

2 months, 2 weeks

[MM3-users] Re: New attack in progress

by Jeremy Stanley

On 2026-08-04 21:24:25 -0700 (-0700), Mark Sapiro wrote: [...] > However it precludes accessing Mailman from a non-javascript > enabled browser. Not entirely, it only forces certain clients to calculate and return hashes, mainly based on user agent strings. For example, I have Anubis in front of all my Postorius/Hyperkitty sites and have no problem accessing them with console-based browsers like lynx. In fact, it's the Javascript in Hyperkitty that makes it so I can't browse list archives that way, Anubis isn't stopping me at all. -- Jeremy Stanley

2 months, 1 week

[MM3-users] Re: Restrict the visible mailing lists to the current domain? – SOLVED

by Mihai Moldovan

* On 9/20/26 19:43, H.-Dirk Schmitt wrote: > Am Sonntag, dem 20.09.2026 um 09:01 -0700 schrieb Mark Sapiro: >> Set `FILTER_VHOST = True` in your `settings` file. >> > > Thanks – this setting fixed my problem. > IMHO it is undocumented in https://docs.mailman3.org/en/latest/ Documented in the web frontend documentation at https://docs.mailman3.org/en/latest/config-web.html :) Mihai

4 weeks

[MM3-users] Re: lmtp runner not starting

by Guillermo Hernandez (Oldno7)

El 1/4/23 a las 21:38, Mark Sapiro escribió: > On 4/1/23 12:22, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> >> El 1/4/23 a las 21:14, Mark Sapiro escribió: >>> >>> If you had completely stopped Mailman core and then started it, lmtp >>> runner should have started. What are the complete log messages from >>> mailman.log following the start? >>> >> I sent them before > > > And there is no `lmtp runner started` message in the log, so it isn't > being started at all. > > >>> What does `mailman conf -s runner.lmtp` show? >>> >> Here it is: >> >> root@www:/usr/local/mailman3 # /usr/bin/su -m mailman3 -c >> "/usr/local/bin/mailman -C /usr/local/mailman3/var/etc/mailman.cfg >> conf -s runner.lmtp" >> [runner.lmtp] class: mailman.runners.lmtp.LMTPRunner >> [runner.lmtp] instances: 1 >> [runner.lmtp] max_restarts: 10 >> [runner.lmtp] path: >> [runner.lmtp] sleep_time: 1s >> [runner.lmtp] start: yes > > > This says the runner should be started. That is the command that > starts Mailman? is it Yes, indeed. > > /usr/bin/su -m mailman3 -c "/usr/local/bin/mailman -C > /usr/local/mailman3/var/etc/mailman.cfg start" > > or is it something that perhaps uses a different config. > > What happens if you do > > /usr/bin/su -m mailman3 -c "/usr/local/bin/runner -C > /usr/local/mailman3/var/etc/mailman.cfg -v -r lmtp" > I get the same error as before: root@www:/usr/local/mailman3 # /usr/bin/su -m mailman3 -c "/usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailman.cfg -v -r lmtp" Apr 01 21:40:36 2023 (12396) Using selector: KqueueSelector Apr 01 21:40:36 2023 (12396) Using selector: KqueueSelector Traceback (most recent call last): File "/usr/local/bin/runner", line 33, in <module> sys.exit(load_entry_point('mailman==3.3.8', 'console_scripts', 'runner')()) File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1128, in __call__ return self.main(*args, **kwargs) File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1053, in main rv = self.invoke(ctx) File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1395, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/local/lib/python3.9/site-packages/click/core.py", line 754, in invoke return __callback(*args, **kwargs) File "/usr/local/lib/python3.9/site-packages/click/decorators.py", line 26, in new_func return f(get_current_context(), *args, **kwargs) File "/usr/local/lib/python3.9/site-packages/mailman/bin/runner.py", line 184, in main runner = make_runner(*runner_spec, once=once) File "/usr/local/lib/python3.9/site-packages/mailman/bin/runner.py", line 70, in make_runner return runner_class(name, slice) File "/usr/local/lib/python3.9/site-packages/mailman/runners/lmtp.py", line 295, in __init__ self.lmtp = LMTPController(LMTPHandler(), hostname=hostname, port=port) File "/usr/local/lib/python3.9/site-packages/aiosmtpd/controller.py", line 417, in __init__ self._localhost = get_localhost() File "/usr/local/lib/python3.9/site-packages/aiosmtpd/controller.py", line 66, in get_localhost with makesock(AF_INET6, SOCK_STREAM) as sock: File "/usr/local/lib/python3.9/socket.py", line 232, in __init__ _socket.socket.__init__(self, family, type, proto, fileno) OSError: [Errno 43] Protocol not supported -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

3 years, 6 months

[MM3-users] Re: lists.mailman3.org web site.

by Barry Warsaw

On Aug 30, 2016, at 10:13 AM, Mark Sapiro wrote: >I don't see much point in adding a large number as it would just create >clutter without much benefit, but other than not wanting to add OpenID/Yahoo >at least until we get DMARC mitigations, if anyone has a strong interest in >one of the others, I can add it. I think we have a good default list. GitHub and GitLab for the nerds, Facebook and Google for the humans. :) *Possibly* Bitbucket would be a good addition but I think we can use bug-driven development here. If enough people request an alternate, supported provider, we can add it then. Cheers, -Barry

10 years, 1 month

[MM3-users] Re: hyperkitty base_url

by Thomas Stein

On Friday, 4 January 2019 21:27:41 CET Mark Sapiro wrote: > On 1/4/19 12:07 PM, Thomas Stein wrote: > > Hi all. > > > > Now I'm struggeling with configuring hyperkitty. It's not clear to me which base_url to set. Currently it's > > base_url: http://localhost:8001/hyperkitty/ but that leads to > > That's wrong. base_url is set to the URL used to access Hyperkitty > externally. It is used for things like the Archived-At: and > List-Archive: headers in distributed posts. For example, for this > installation it is It's working with base_url: http://localhost:8000/hyperkitty/. Is that ok? thanks and cheers t. > base_url: https://lists.mailman3.org/archives > >

7 years, 9 months

[MM3-users] Re: export/import list?

by Mark

On 2024-03-01 10:56, Peter Adebahr via Mailman-users wrote: > On 3/1/24 00:11, Mark Sapiro wrote: >> On 2/29/24 14:44, imark(a)posteo.net wrote: >>> This appears to be practical for exporting/importing ALL the lists >>> from one MM3 server to another MM3 server. >>> >>> Is there a similar straightforward way of exporting/importing just >>> ONE list? >> > > Why not export ALL list as indicated, then delete all unwanted lists > on source resp. destination server ... > > That's definitely Plan B. And thank you Mark for the pointer to the Gitlab thread. Greater minds have clearly been giving this some thought for a while. Cheers.

2 years, 7 months

[MM3-users] Re: Heads up: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated

by Andreas Vetter

On Freitag, 7. Februar 2025 18:40:32 CET Mark Sapiro wrote: > On 2/7/25 03:19, Andreas Vetter wrote: > > Changing ACCOUNT_AUTHENTICATION_METHOD to ACCOUNT_LOGIN_METHODS in > > /etc/mailman3/settings.py is not enough. One has to edit > > venv/lib/python3.11/site-packages/mailman_web/settings/mailman.py > > You can do this in /etc/mailman3/settings.py only without editing > venv/lib/python3.11/site-packages/mailman_web/settings/mailman.py by adding > ``` > del ACCOUNT_AUTHENTICATION_METHOD > ACCOUNT_LOGIN_METHODS = {'email', 'username'} That is unfortunately not enough to get rid of the Warning, because venv/lib/ python3.11/site-packages/mailman_web/settings/mailman.py contains the old ACCOUNT_AUTHENTICATION_METHOD and allauth is complains about it. -- Mit freundlichen Gruessen, Andreas Vetter

1 year, 8 months

[MM3-users] Re: user self registration

by Stephen J. Turnbull

Washington Odhiambo via Mailman-users writes: > On Sun, Dec 7, 2025 at 8:26 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > ACCOUNT_ADAPTER = ‘django_mailman3.views.user_adapter.DisableSignupAdapter’ > Can this be done on a per-site or per-list basis? > SITE_ID = 0 Not effectively. The point is to prevent people from registering Users. If you did it (somehow) for List A but not List B, once somebody signed up for List B, they'd have a User, and then they could log in and sign up for List A. Same logic for multiple domains. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

10 months

[MM3-users] Re: Auth question

by David Krantz

On Fri, Mar 31, 2017 at 1:09 AM, David Krantz <david(a)krantz.dk> wrote: > On Fri, Mar 31, 2017 at 12:01 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > Very good! Thank you very much, I got a bit further. > > The database contained a couple of test lists that I can recreate, so > nothing of value. The strange thing was that drop database followed by > create database did not yield an empty database in Postgres. I > probably forgot a commit somewhere. > Never mind, now I got it to work. Some kind of intermittent server error (500) left but I guess that's solvable too. Thanks for all your help on this list! cheers // David

9 years, 6 months

Search results for query "sapiro"