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

[MM3-users] Re: hyperkitty won't list more than 5 posts and shows empty grey Activity Summary box

by Barry Warsaw

On Aug 9, 2017, at 15:45, Mark Sapiro <mark(a)msapiro.net> wrote: > However, the sending of periodic digests depends on cron running > something periodically to actually trigger the sending. Right. There will eventually be additional recurring tasks for Core too though, such as processing the bounce database for disables and unsubs, pulling messages from NNTP, and possibly others as time goes on. I’ve always thought about handling these as commands that cron would run, much as in Mailman 2, but it would also be possible to implement a runner, or runners, to do those jobs. I can see advantages and disadvantages with either approach. > Note: I've just looked at the code and there seems to be an issue with > using 'mailman digests --send' to send the periodic digests. It appears > that if a list's digest mbox has any messages, 'mailman digests --send' > will send a digest even if digest_send_periodic is false. I've just > reported <https://gitlab.com/mailman/mailman/issues/384> for this issue. Yep, thanks for the bug report. `mailman digests —periodic` seems like the right approach. Cheers, -Barry

8 years, 2 months

[MM3-users] Re: Hyperkitty Error Curiosity

by Brian Carpenter

On 11/11/20 7:40 PM, Mark Sapiro wrote: > On 11/11/20 4:18 PM, Brian Carpenter wrote: >> Some sort of auto-discard procedure after a number of retries? Is it >> possible to detect a message with a null characters and automatically >> discard them? Do such messages make it into the thread table? > > The message has been delivered to the list, but it is not archived. The > list post has an Archived-At: header with a URL, but the message isn't > there at all. The only way to get it archived is to correct the message > defect. Does the problematic message (null character) make it to the hyperkitty_thread table? > Thus, I don't think it's good to just discard the message at that point. > I'm fine with moving out of or not queueing it in the first place in > var/archives/hyperkitty/spool, but I think it should be preserved > somewhere, say in var/archives/hyperkitty/bad, and along with that, some > kind of notice sent to the site admin so bad messages don't just > accumulate without being seen. > Can a message with a null character be repaired with an automatic process? -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 11 months

[MM3-users] Re: Issues encountered while upgrading to 3.3.7

by Odhiambo Washington

On Mon, Dec 5, 2022 at 8:54 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/5/22 02:37, Odhiambo Washington wrote: > > > > Here again, Google-fu came to the rescue. I added the following line to > > settings_local.py and the warnings were suppressed. > > DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' > > I need to understand how this affects everything and how this is likely > to > > impact the functionality of MM3. What is the proper solution for this? > > And should it be django.db.models.BigAutoField or > > django.db.models.AutoField? Which is which? > > > Prior to Django 3.2 Django set default primary keys to 32 bit integers. > In 3.2 Django introduced the possibility to set default primary keys to > 64 bit integers by setting the type to django.db.models.BigAutoField. > > Thus, putting > ``` > DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' > ``` > in your settings will maintain compatibility with pre 3.2 versions and > existing tables and this is the correct thing to do. > Thank you very much for the clarification. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 10 months

[MM3-users] Re: Hyperkitty fulltext search performances

by Mark Dadgar

On Oct 4, 2020, at 8:13 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/4/20 8:07 AM, Brian Carpenter wrote: >> >> On 10/4/20 8:59 AM, Loïc Dachary wrote: >>> After a little digging it turns out the mailman3-web Debian GNU/Linux >>> package I'm using is configured to use Woosh as a haystack backend. >>> And it is not fit for volumes greater than a few hundred mega bytes. I >>> should switch to something else from the list of supported >>> backendshttps://django-haystack.readthedocs.io/en/master/backend_support.html >>> >> For our servers running Postorius/Hyperkitty, we use Xapian. I believe >> the mailman-users (MM3) list also uses Xapian. It is a lot quicker. For >> our Affinity/Empathy servers, we use Elasticsearch which we are very >> happy with. Elasticsearch does have a higher memory requirement I >> believe than Xapian. > > > Brian is correct about this list. We started with Whoosh, then went to > Elasticsearch and ultimately to Xapian. Each step gave better > performance and a smaller footprint than the one before. +1 I have ~700K posts in my archive and Xapian is FAST. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years

[MM3-users] Re: If you delete a list but not the HyperKitty archive

by Philip Colmer

On Tue, 4 Jan 2022 at 18:34, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/4/22 6:45 AM, Philip Colmer wrote: > > > > So ... should the archive be deleted when the list is deleted and it is a > > bug that it isn't? Or is it expected that access to the archive is > "frozen" > > once a list is deleted? > > > It is often desired to have a public archive available after the > corresponding list has been deleted. Even for a private archive, it may > be desirable for site admins to have access. Furthermore, a list might > not even have a HyperKitty archive in the first place. Thus, what to do > about a HyperKitty archive (or prototype archive or ...) when a list is > deleted is an administrative decision and is best left up to the site > admins to do it or not. > > As you note with a private archive, former members no longer have access > when the list is gone, but unless an attempt throws some uncaught > exception, that is not a bug. > Thanks, Mark, for the clarification. Regards Philip

3 years, 9 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

1 year, 10 months

[MM3-users] Re: API timeout for one list

by Seth Seeger

> On Sep 22, 2020, at 4:30 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 9/22/20 12:45 PM, Seth Seeger wrote: >> I apologize, because I think this was talked about before, but I could not find it in the archives. >> >> For one list, the REST API times out. Doesn’t seem to matter which page I try to go to. The uwsgi-error.log entry: >> > ... >> The other lists work fine. > > This can happen on lists with lots of members. > > Try increasing the timeout. See <https://wiki.list.org/x/17892072> Thank you - that did solve my timeout problem. However, each page for this list takes between 40 and 80 seconds to load. The list has 465 members, and it’s running (via Docker) on a 2 core, 4 GB RAM Linode VM. I’ve watch htop during the load - one CPU is around 20%, and the other hovers around 80%, mostly with the process “runner”. Is there a way to optimize this list? There are no held messages, no subscription requests, no templates. The next biggest list has 438 members, and all those pages load very quickly (0-2 seconds). I can’t figure out what the difference between the two lists. Thanks, Seth

5 years

[MM3-users] Re: Mailman3 not able to deliver emails sent through list, but moderation notifications

by Ruth Ivimey-Cook

See after: On 26/11/2022 18:18, Mark Sapiro wrote: > I found this article stating the the SMTP error message >> might be misleading: >> https://blog.tfiu.de/mailman3-cannot-connect-to-smtp-server-localhost-on-po… >> >> >> How to further debug this? >> What could be wrong with my Mailman3 instance and how to fix it? > > The article is relevant and mentions the most likely issue which is > lack of permission on one or more message templates. > > Everything in Mailman's var/ directory should be owned by Mailman's > user:group - normally `list:list` in Debian packages. While this is always true for mailman-core, in some configurations the mailman-web files are also inside the ./var/ tree, and they need to be readable (and, for some, writable) by the process acting as webserver, which may or may not be list:list. In my case (a bit off-piste) I have set mailman-web it up to run as owner=www-data, for example (I forget quite why this was needed now!!). Regards Ruth -- Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

2 years, 10 months

[MM3-users] Re: Where are the subject templates hidden?

by Simon Hanna

On 11/29/2017 09:25 AM, Thor Atle Rustad wrote: > 2017-11-29 7:40 GMT+01:00 Mark Sapiro <mark(a)msapiro.net>: > >> On 11/28/2017 02:56 AM, Thor Atle Rustad wrote: >>> Using Docker. Suppose I've overcome >>> https://gitlab.com/mailman/mailman/issues/359 and I can make Mailman use >>> the templates/site/no directory for my customized templates. Yes, it >> seems >>> to be working, no hickups when national characters are used in the >>> templates. >>> >>> but... >>> >>> the welcome message still says "Welcome to the "listname" mailing list" >> in >>> English. Is it possible to change that? >> >> Have you put the desired template in >> templates/site/no/list:user:notice:welcome.txt ? >> >> -- >> > Yes, I put it there, and the text in that file is what is shown in the > welcome mail. However, the subject does not change (still English) > Thor > The subjects are currently not part of the templates. The translation of these is done in the Python code, so you would need to export a list of strings Mailman Core uses and translate these...

7 years, 10 months

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

by Franklin Weng

Hi Mark, Mark Sapiro <mark(a)msapiro.net> 於 2019年10月24日週四上午8:42寫道： > > Actually, there is no 1.2.5. The next release after 1.2.4 is 1.3.0, but > you can still set preferred_language for the list using the REST API or > mailman shell. > > For example in mailman shell > > $ mailman shell -l zh-l10n.lists.linux.org.tw > Welcome to the GNU Mailman shell > The variable 'm' is the zh-l10n.lists.linux.org.tw mailing list > >>> m.preferred_language > <Language [en] English (USA)> > >>> m.preferred_language = 'zh_TW' > >>> m.preferred_language > <Language [zh_TW] Chinese (Taiwan)> > >>> commit() > Thanks for your help. I did what you said above, but then I still got the same result even after restarting mailman3 services. ~# mailman shell -l zh-l10n.lists.linux.org.tw Welcome to the GNU Mailman shell The variable 'm' is the zh-l10n.lists.linux.org.tw mailing list >>> m.preferred_language <Language [zh_TW] Chinese (Taiwan)> >>> quit() I created a new list with Chinese display name, set the preferred_language and then subscribed to it. Also got question marks. Is there anything else to try? Thanks, Franklin

5 years, 11 months

Search results for query "sapiro"