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

[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, 6 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

4 years, 9 months

[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, 7 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, 7 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, 7 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, 8 months

[MM3-users] Re: Help request, almost got it going, but ....

by Claus-Justus Heine

Oh well. Am 01.09.2017 um 23:44 schrieb Mark Sapiro: > On 09/01/2017 02:33 PM, Claus-Justus Heine via Mailman-users wrote: >> >> Seemingly, at some point in the deep dungeons of the source code the >> "Acceptable aliases" Text-Box is not interpreted correctly. >> >> Specifically, at the start it contains the string >> >> [] > > > See <https://gitlab.com/mailman/postorius/issues/58>. there they talk about fancy "uni-code thinks" (email addresses?) where the task is to convert a new-line separated text-field into an array. Oops. Kind thanks anyway. > > In order to set things on this page, you need to clear the Acceptable > aliases box before submitting changes. You can't actually set Acceptable > aliases via Postorius until this is fixed. The issue seems not to be overly active. I thought -- coming from Mailman v2 -- that the configuration of acceptable submitters to an email list (e.g. keep everyone moderated?) would be a central and prominent and important configuration issue. Seems not to be a central point. Mmmh. Thanks Claus -- Claus-Justus Heine himself(a)claus-justus-heine.de http://www.claus-justus-heine.de/ Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de

7 years, 10 months

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Odhiambo Washington

On Mon, Jan 30, 2023 at 12:39 PM Onyeibo Oku <onyeibo(a)schemefusion.com> wrote: > > On Tue, 3 Jan 2023 09:46:00 -0800 > > Mark Sapiro <mark(a)msapiro.net> wrote: > > > This is all configured in your web server. It needs to proxy requests > > for lists.website.tld to gunicorn and depending on the web server, > > may need more. E.g. see > > > https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura… > > for nginx. > > I have fixed this. > > > > > > Set SITE_ID = 0 in your Django settings. Also see > > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > > Actually "SITE_ID = 1" solved that instead. I also had to go into the > database and update the values (django provided 'example.com' by > default and that was problematic). > The common practice I have see is that one creates their domain on the web interface, which then displays the SITE_ID = N. You then take the value into settings.py to replace the one that's there. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 5 months

[MM3-users] Re: Exception with processing subscription confirmation email

by Eric Broens

Thanks Mark, We are indeed running mailman core 3.3.2 and using mysql. The data appears indeed to be truncated judging from the missing closing curly bracket (see below). Would it be OK to already extend the data column to VARCHAR(510) before upgrading to mailman core 3.3.3, or will this cause problems with upgrading to a newer version? +--------------------------------------------------------------------------- ---------------------------------------------------------------------------- ---------------------------------------------------------------------------- ------------------------------+ | data | +--------------------------------------------------------------------------- ---------------------------------------------------------------------------- ---------------------------------------------------------------------------- ------------------------------+ | {"pre_approved": false, "pre_confirmed": false, "pre_verified": false, "invitation": false, "address_key": "******************@************", "subscriber_key": 1, "user_key": "a44e8b9a34c64775b712f383d438ce1d", "token_owner_key": 1, "send_welcome_message" | +--------------------------------------------------------------------------- ---------------------------------------------------------------------------- ---------------------------------------------------------------------------- ------------------------------+ Best Regards, Eric -----Original Message----- From: Mark Sapiro [mailto:mark@msapiro.net] Sent: donderdag 29 april 2021 18:43 To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Exception with processing subscription confirmation email On 4/29/21 7:56 AM, Eric Broens wrote: > Hi, > > A new user tried to subscribe to a mailinglist, received the confirmation > mail, and replied to it. > > The subscriber is however not subscribed and remains listed in the "pending > confirmation" list. > > The following exception appears in the error.log. > > Does anyone knows how to resolve this? In the past we didn't experience any > issues and no changes but security updates have been installed. > > Apr 29 16:15:55 2021 (1581) deque: do_confirm_verify > > Traceback (most recent call last): > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/workflow.py", > line 69, in __next__ > > return step() > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/subscriptions.p > y", line 356, in _step_send_confirmation > > raise StopIteration > > StopIteration Tracebacks like the above are normal and probably shouldn't be logged at all. > Apr 29 16:16:28 2021 (1490) Uncaught runner exception: Expecting ':' > delimiter: line 1 column 256 (char 255) > > Apr 29 16:16:28 2021 (1490) Traceback (most recent call last): > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > line 173, in _one_iteration > > self._process_one_file(msg, msgdata) > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > line 266, in _process_one_file > > keepqueued = self._dispose(mlist, msg, msgdata) > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/runners/command.py" > , line 208, in _dispose > > mlist, msg, msgdata, parts, results) > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/commands/eml_confir > m.py", line 54, in process > > mlist).confirm(token) > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/subscriptions.p > y", line 578, in confirm > > workflow.restore() > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/workflow.py", > line 146, in restore > > data = json.loads(state.data) > > File "/usr/lib64/python3.6/json/__init__.py", line 354, in loads > > return _default_decoder.decode(s) > > File "/usr/lib64/python3.6/json/decoder.py", line 339, in decode > > obj, end = self.raw_decode(s, idx=_w(s, 0).end()) > > File "/usr/lib64/python3.6/json/decoder.py", line 355, in raw_decode > > obj, end = self.scan_once(s, idx) > > json.decoder.JSONDecodeError: Expecting ':' delimiter: line 1 column 256 > (char 255) > > Apr 29 16:16:28 2021 (1490) SHUNTING: > 1619705788.5856323+57a1a759275c59b732cfa8e2985f76cfcc27dda5 This one is the issue. There was some problem with the user's confirmation reply. View the shunted message with the command ``` mailman qfile path/to/var/queue/shunt/1619705788.5856323+57a1a759275c59b732cfa8e2985f76cfc c27dda5.pck ``` although that probably won't show anything wrong as it appears that the issue is with the saved workflow. You can get the token from the shunted message and then look at the database with something like ``` SELECT data FROM workflowstate WHERE token = '<the token>' ``` but I suspect the issue is because the database is MySQL or MariaDB, your Mailman core is older than 3.3.3 and your database server mode is such that data too long for column results in truncation, and the data in this case is truncated to 255 bytes. In Mailman 3.3.3, this column was changed from VARCHAR(255) to VARCHAR(510) for MySQL. As far as subscribing the user is concerned, you can in Postorius view the subscriptions waiting user confirmation and delete this one and then `mass subscribe` the user. -- 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, 2 months

[MM3-users] Re: Mailman messages are getting a TAG in some email clients.....how????

by Guillermo Hernandez (Oldno7)

El 12/9/23 a las 19:43, Mark Sapiro escribió: > On 9/12/23 8:51 AM, bob B via Mailman-users wrote: >> So I know about the setting "Anonymous list" but regardless of that >> setting some email clients put the list name in [] when it displays >> messages in your inbox. Does anyone know how email clients are doing >> this? I have users who email clients do not do this, and was >> wondering if it is a setting in their client or just not possible. > > > This looks like Mailman adding 'Subject prefix', so all list mail will > have this prefix added to the Subject:. So the question isn't how mail > clients are adding it, but rather why do some mail clients suppress it. I think the simple answer is that some mobile mail clients don't show the subject line by default, you have to click to show it explicitely. That users just don't see that. -- ___________________________________________ 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.

1 year, 9 months

Search results for query "sapiro"