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

[MM3-users] Re: Auth question

by Simon Hanna

On March 31, 2017 6:34:18 PM GMT+02:00, Mark Sapiro <mark(a)msapiro.net> wrote: >On 03/31/2017 01:06 AM, David Krantz wrote: >> On Fri, Mar 31, 2017 at 9:29 AM, Simon Hanna ><simon.hanna(a)serve-me.info> wrote: >>> On 03/31/2017 08:10 AM, David Krantz wrote: >>>> I think that would correspond to this line in urls.py >>>> >>>> url(r'^$', >RedirectView.as_view(url=reverse_lazy('hyperkitty.views.index.index'))), >>> Yes, that's the culprit. Replace it with the following: >>> >>> url(r'^$', RedirectView.as_view(url=reverse_lazy('hk_root'))), >>> You can also update whatever guide you were using... >> >> Great, will try that! I don't know whether I can update the guide. >> It's the one referenced earlier in this thread named something like >> setup experience of mailman 3 in production. > > >Yes, that comes from >"https://wiki.list.org/DOC/Mailman%203%20installation%20experience", >specifically the attachment urls.py. > >The interesting thing is that works for me both at ><https://lists.mailman3.org/> and <https://mail.python.org/mm3/>. Are you using the latest version of django? -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

9 years, 6 months

[MM3-users] Re: lmtp runner not starting

by Guillermo Hernandez (Oldno7)

El 1/4/23 a las 20:44, Mark Sapiro escribió: > ... > lmtp runner did not start because at some point it had died and > restarting Mailman won't restart a runner that died and was marked to > not restart. > > You need to stop Mailman and make sure when mailman is stopped that > there are no files in mailman's var/locks/ directory (remove any that > are there) and then start Mailman and lmtp runner should start. > I stopped mailman and removed all that was in there (there were many locked registers). Restarted mailman, and it shows the same error that in my previous mail. Now there is two new locked files, one (master.lck) which its content is the name of the other file. And the second one has the same content: master.lck|www.proteccion-civil.eu|9389|7022761192045613065 will try deleting the content of var/locks and restarting the server > As to why it died in the first place, there should be something in > mailman.log from the time it died. > -- ___________________________________________ 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: Welcome message template errors

by Mark

On 2024-04-23 11:33, Mark Sapiro wrote: > On 4/22/24 17:06, Mark wrote: >> >> There was no line POSTORIUS_TEMPLATE_BASE_URL in >> /etc/mailman3/settings.py > So presumably you were getting the default > > POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000' > > from mailman-web/settings/mailman.py because of > from mailman_web.settings.mailman import * > in your settings.py. Yes. # Mailman Web configuration file. # /etc/mailman3/settings.py # Get the default settings. from mailman_web.settings.base import * from mailman_web.settings.mailman import * ... > >> Then, as site-owner, creating a new custom Welcome template (again via >> the WebUI) I can see it correctly added to the database in >> mailman.template.uri >> >> - >> https://lists.mydomain.com/mailman3/api/templates/list/lists.mydomain.com/l… That URI should have been; https://lists.mydomain.com/mailman3/api/templates/list/mytestlist.lists.myd… If I go to the above URL, the text of the list's Custom welcome message displays on an otherwise empty webpage. > > > And what happens if you go to that URL in a web browser? Also what do > you get when going to https://lists.mydomain.com/mailman3? I get the Postorius page "Mailing Lists" that displays the table of lists.

2 years, 5 months

[MM3-users] Re: MM3 Docker

by Odhiambo Washington

On Wed, 9 Jan 2019 at 00:16, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/8/19 10:03 AM, Odhiambo Washington wrote: > > > > Thank you for clarifying. > > So once I have a venv created, the services will just run as long as the > > startup scripts are running even when I'm logged out of the system? > > > As long as the startup scripts actually reference things in the venv. > > If you look at the samples in the Recommended Configuration section at > <https://wiki.list.org/x/17891998> for > > /opt/mailman/mm/bin/django-admin (sample) Script to run Django > management commands. > > /opt/mailman/mm/bin/mailman (sample) Script to run mailman commands. > > and > > /opt/mailman/mm/bin/gunicorn (sample) Script to start Gunicorn. > > You will see they all do things like activate the venv or run a command > from venv/bin. > > > Now that has clarified the matter for me. That even when I am logged out, the scripts do the neccessary to activate the venv to run things. I hadn't looked at the scripts at all. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

7 years, 9 months

[MM3-users] Re: LTMP to Postfix problem

by Brian Carpenter

On 6/18/20 4:09 PM, Mark Sapiro wrote: > Do you have > > lmtp_host: 127.0.0.1 > lmtp_port: 8024 > > in the [mta] section of mailman.cfg? (these are the defaults) > > $ /opt/mailman/mm/bin/mailman conf|grep lmtp > [mta] lmtp_host: 127.0.0.1 > [mta] lmtp_port: 8024 I do > Is Mailman's lmtp runner listening on port 8024? > > $ sudo netstat -lntp|grep python > tcp 0 0 127.0.0.1:8024 0.0.0.0:* > LISTEN 1867/python > tcp 0 0 127.0.0.1:8000 0.0.0.0:* > LISTEN 1199/python > tcp 0 0 127.0.0.1:8001 0.0.0.0:* > LISTEN 1871/python It is. > > Is there some firewall issue blocking access to the port even from > localhost? Let me describe the problem a little better. Mail delivery from postfix to mailman works most of the time. However in the past week or so, lmtp starts refusing connections via postfix about once a day. I have port 8024 open in the firewall (UFW). There are no errors in the smtp.log file. I think restarting Mailman core seems to get things running again. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

6 years, 3 months

[MM3-users] Re: How to remove global ban using API?

by Nathan Dixon

For those who are interested. To be able to use global_bans = IBanManager(None) and not get the following error: Traceback (most recent call last): File "<stdin>", line 1, in <module>TypeError: ('Could not adapt', None, <InterfaceClass mailman.interfaces.bans.IBanManager>) You need to use: mailman shell Not a standard python3 session. To actually update the global bans not via the API, which has some limitations at the moment (see the issue on Gitlab), I have done the following workaround (later I will put in checks for an existing ban to do an update instead, or a delete then create of the new ban): 1) I create a python script within the docker container within the existing PYTHONPATH that will be the module that runs when I want to create or update my ban (in this case under /usr/bin/) #!/bin/env python def create_valid_domains_ban(valid_domains_regex): from mailman.interfaces.bans import IBanManager global_bans = IBanManager(None) global_bans.ban(valid_domains_regex) print(list(global_bans.bans)[0].email) 2) I can then invoke this as a mailman module from the server using docker exec mailman-core mailman shell -r create_valid_domains_ban $valid_domains_regex On Wed, 15 May 2019 at 21:21, Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/15/19 9:46 AM, Nathan Dixon wrote: > > > > I can create the ban fine by the following: > > > > from mailmanclient import Client > > client = Client(URI,apiuser,apipass) > > > client.bans.add("^(?!.*[(a)\.](validdomain1\.com|validdomain2\.org|validdomain3\.co\.uk)") > > > This is apparently a typo - missing ')' - in the re as you have it > correct below. > > > > However, I cannot seem to be able to remove it using the api: > >>>> client.bans[0].delete() > ... > >>>> client.bans.remove(str(client.bans[0])) > ... > >>>> > > > client.bans.remove("^(?!.*[(a)\.](validdomain1\.com|validdomain2\.org|validdomain3\.co\.uk))") > > > All of the above work for me with both API 3.0 and 3.1 in a non-docker > install of the current GitLab HEADs > > > > And also, when I now try and go into the mailman-core docker image to use > > the mailman.interfaces.bans, it will not let me see the global bans: > > > >>>> from mailman.interfaces.bans import IBanManager > >>>> global_bans = IBanManager(None) > > Traceback (most recent call last): > > File "<stdin>", line 1, in <module> > > TypeError: ('Could not adapt', None, <InterfaceClass > > mailman.interfaces.bans.IBanManager>) > > > I don't see this either. > > > > I have opened an issue in Gitlab for this as I feel it may be a bug > related > > to regex and global bans (there was a similar one for list banned > > addresses): https://gitlab.com/mailman/mailman/issues/598 > > > I also commented on the GitLab issue. I think this must be an issue with > the docker images. > > -- > 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/ > -- *Nathan Dixon* MEng Senior Software Architect m: +44 (0)7402 690311 t: +44 (0)20 81231252 e: nathan.dixon(a)evadon.com w: www.evadon.com This e-mail and any attachments are confidential and may be protected by legal, professional or other privilege. If you are not the intended recipient you should not store it, copy it, re-transmit it, use it or disclose its contents, but should return it to the sender immediately and delete your copy from your system. The views expressed are those of the sender and not necessarily those of Evadon. Please note that whilst we scan all e-mails for viruses we cannot guarantee that any e-mail is virus-free. Please be advised that we expressly reserve the right to monitor email content for the purposes of ensuring compliance with legal requirements and company policies and your sending to, or receiving from, us of any email constitutes your agreement to these terms. Evadon Dynamics Limited, registered in England No. 09494097. Registered Office: Electric Works, Sheffield Digital Campus, 3 Concourse Way, Sheffield, S1 2BJ

7 years, 4 months

[MM3-users] Re: Django-allauth compatibility (ACCOUNT_AUTHENTICATION_METHOD and ACCOUNT_EMAIL_REQUIRED)

by Jan Eden

On 2025-06-16 17:29, Mark Sapiro wrote: > On 6/16/25 15:26, Eggert Ehmke via Mailman-users wrote: > > I have django-allauth 65.9.0 and still the same problem. mailman-web runjobs minutely throws it each minute, which is annoying. > > Do you have > ``` > ACCOUNT_LOGIN_METHODS = {'email', 'username'} > ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*'] > ``` > in your django settings? > > What releases of HyperKitty, Postorius and Django-Mailman3 are you running? > Current releases do not have any minutely jobs. I did have the same issue about a month ago[1] with the current versions of the above components, and these are the cronjobs I installed according to the docs[2]: @daily /opt/mailman/venv/bin/mailman digests --periodic @daily /opt/mailman/venv/bin/mailman notify * * * * * /opt/mailman/venv/bin/mailman-web runjobs minutely 0,15,30,45 * * * * /opt/mailman/venv/bin/mailman-web runjobs quarter_hourly @hourly /opt/mailman/venv/bin/mailman-web runjobs hourly @daily /opt/mailman/venv/bin/mailman-web runjobs daily @weekly /opt/mailman/venv/bin/mailman-web runjobs weekly @monthly /opt/mailman/venv/bin/mailman-web runjobs monthly @yearly /opt/mailman/venv/bin/mailman-web runjobs yearly - Jan [1] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… [2] https://docs.mailman3.org/en/latest/install/virtualenv.html#cron-jobs-for-m…

1 year, 4 months

[MM3-users] Re: django-allauth failures, but only for some users (independent of browser?)

by Mark Sapiro

On 12/6/23 14:49, Jered Floyd wrote: > > The difference in behavior was using social login buttons for an existing account vs. creating a new account. > > This is another damn django-allauth regression, starting in 0.57.0. It seem to be this commit that is to blame: > https://github.com/pennersr/django-allauth/commit/be779dfee5a328a3a42edc2c9… > > In allauth/socialaccount/models.py:lookup(self):285 there is an attempt to look up the social account as one that already exists. If that fails, this commit calls self.account.get_provider() without passing the request object, which leads to the eventual error. > > I believe this is a django-allauth bug, and have submitted a pull request to fix it here: > https://github.com/pennersr/django-allauth/pull/3548 Thanks for all your work on this. It is much appreciated. However, your patch doesn't fix my issue with the URL https://example.com/accounts/social/connections/ which still produces the following: ``` ERROR 2023-12-07 00:05:55,032 169452 django.request Internal Server Error: /accounts/social/connections/ Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/handlers/exception.py", line 55, in inner response = get_response(request) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/handlers/base.py", line 220, in _get_response response = response.render() File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/response.py", line 114, in render self.content = self.rendered_content File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/response.py", line 92, in rendered_content return template.render(context, self._request) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/backends/django.py", line 61, in render return self.template.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 175, in render return self._render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 167, in _render return self.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/loader_tags.py", line 157, in render return compiled_parent._render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 167, in _render return self.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/loader_tags.py", line 157, in render return compiled_parent._render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 167, in _render return self.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/loader_tags.py", line 157, in render return compiled_parent._render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 167, in _render return self.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/loader_tags.py", line 63, in render result = block.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/loader_tags.py", line 63, in render result = block.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/defaulttags.py", line 321, in render return nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/defaulttags.py", line 238, in render nodelist.append(node.render_annotated(context)) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/defaulttags.py", line 539, in render values = {key: val.resolve(context) for key, val in self.extra_context.items()} File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/defaulttags.py", line 539, in <dictcomp> values = {key: val.resolve(context) for key, val in self.extra_context.items()} File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 715, in resolve obj = self.var.resolve(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 847, in resolve value = self._resolve_lookup(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 914, in _resolve_lookup current = current() File "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/models.py", line 147, in get_provider_account return self.get_provider().wrap_account(self) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/models.py", line 141, in get_provider provider = self._provider = adapter.get_provider( File "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/adapter.py", line 204, in get_provider app = self.get_app(request, provider=provider) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/adapter.py", line 284, in get_app apps = self.list_apps(request, provider=provider, client_id=client_id) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/adapter.py", line 231, in list_apps db_apps = SocialApp.objects.on_site(request) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/models.py", line 27, in on_site site = get_current_site(request) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/contrib/sites/shortcuts.py", line 16, in get_current_site return Site.objects.get_current(request) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/contrib/sites/models.py", line 63, in get_current raise ImproperlyConfigured( django.core.exceptions.ImproperlyConfigured: You're using the Django "sites framework" without having set the SITE_ID setting. Create a site in your database and set the SITE_ID setting or pass a request to Site.objects.get_current() to fix this error. ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: Hyperkitty messages stuck in spool

by Stephen J. Turnbull

Mark Sapiro writes: > On 11/18/21 6:38 AM, Andrew Hodgson wrote: > > > > Ok thanks for this. Its happening because the Gunicorn process > > running the Django server is being killed due to OOM > > conditions. Is there any settings I can change to > > troubleshoot/throttle this in Gunicorn or Django? > > I don't think there's anything that can be done in gunicorn or django > about this. This is an OS issue. You need to give the server more memory > or allocate a (bigger) swap file. If those things are difficult, depending on OS and the hardware, it may also be possible to tell the OS that gunicorn is an import process that should not be killed. But in the long run, the server needs more memory. In theory there could be a memory leak in Python or one of the Mailman apps, but I haven't heard of it. And at least the Linux kernel seems to be perfectly happy to kill random processes that are well-behaved. So the fact gunicorn is getting killed is not strong evidence that it's causing the memory pressure, we'd really need to see the stats. Steve

4 years, 10 months

[MM3-users]Re: mailman 2 vs. mailman 3: what happened to multipart/digest?

by John Hein

Mark Sapiro wrote at 19:18 -0700 on May 12, 2016: > On 5/12/16 3:46 PM, John wrote: > > But mm 2 had: > > > > multipart/mixed > > text/plain (the digest heading) > > text/plain (the TOC) > > multipart/digest <--- this is the part that's gone in mm3 > > message/rfc822 > > message-1 > > message/rfc822 > > message-2 > > ... > > text/plain (footer) > > > > So was that removal intentional, a bug or ?? > > > I'm sorry. I missed the point of your OP. I think it's a bug. > > The doctest at > <http://mailman.readthedocs.io/en/release-3.0/src/mailman/runners/docs/diges…>, > the part just after "The MIME digest has lots of good stuff, all > contained in the multipart." is clearly missing the multipart/digest part. > > It appears that this got lost in the refactoring of the MM2 code for > MM3. Please file an issue at > <https://gitlab.com/mailman/mailman/issues/new>. You can assign it to me > (msapiro), but it any case, I'll work on fixing it. https://gitlab.com/mailman/mailman/issues/234 Thanks.

10 years, 5 months

Search results for query "sapiro"