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

[MM3-users] Re: DMARC Munging

by Allan Hansen

Mark, et al., I have entered a ticket at gitlab. Thanks. Is there a way for me to make this change to the From header munging until it is implemented in the production version? I made MM2 do the munging using such a change on your recommendation and it has worked. Our installation is from source, which might make it possible/easier? I have played a lot with the wrapping option and have come to the conclusion that it will not work. In some cases, the Apple Mail client for the desktop simply did not display the internal message, while iOS worked fine. The header munging is safer. Yours, Allan Hansen allan_hansen(a)icloud.com > On Jan 26, 2020, at 22:32 , Mark Sapiro <mark(a)msapiro.net> wrote: > > On 1/26/20 4:43 PM, Allan Hansen wrote: >> All, >> The munged From: header in MM3 still says >> 'name' via ‘listname’ <‘listaddress’> >> This caused me and my subscribers a lot of grief in MM2: >> Some mail clients use the first part up to the From for future key-ahead for new email to ’name’, hiding the address, so what they think is a personal message for ’name’, instead goes to the entire list. Red faces all around. >> Stephen Thurnbull earlier suggested further munging by replacing the list address in the From: header like this: >> 'name' via ‘listname’ <‘whoopsieaddress’> >> Which will return an automated reply explaining the issue. I like this option. How can I get that in? > > > You can file an issue at <https://gitlab.com/mailman/mailman/issues>. That will at least get it on the table, but there are no guarantees as to if/when it would be implemented. > > -- > 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/

5 years, 4 months

[MM3-users] Re: Importing config and archives only partially succeeded?

by Eric Broens

I just notice in the webserver logfile, the same request for the same mlist, msgid and key several times per second for about 3 hours now: "GET /archives/api/mailman/urls?mlist=....&msgid=...&key=... HTTP/1.1" 200 105 "-" "python-requests/2.25.0" The request seems to originate from the server where the mailman suite is installed Best Regards,Eric On Sunday, December 13, 2020, 01:54:54 AM GMT+1, Eric Broens via Mailman-users <mailman-users(a)mailman3.org> wrote: The settings - Archiving, are not different from the ones that do show the messages:"Private Archives" selected, and Active archivers "hyperkitty" also selected. I was trying to find out how the hyperkitty page gets the mails from the database, and if I can start from there.Or maybe something is not completely correct in the database tables. Best Regards,Eric On Sunday, December 13, 2020, 01:27:53 AM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 12/12/20 3:56 PM, Eric Broens via Mailman-users wrote: > After everything was imported, and I noticed that the mails were not shown in the archives for half of the mailinglists, I ran "manage.py update_index" to index the mails for all mailinglists.This command is still running for hours.Since it builds the search index, I don't expect that this would make the mails available on the webpage. I agree, that won't make the mails available on the webpage. If you're using the default Whoosh search engine, "hours" is not unexpected. Elasticsearch is much faster and Xapian faster still. What do you see in Postorius - Settings -> Archiving for the lists whose messages don't show? -- 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/ _______________________________________________ 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: How to fix: [Django] ERROR (EXTERNAL IP)

by Jigme Datse

On Fri, 1 Nov 2024 12:29:56 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/31/24 21:18, Jigme Datse wrote: > > On Thu, 31 Oct 2024 20:07:00 -0700 > > Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> What's in Django's logs? > >> > > > > Attached logs (I hope that works). A couple are currently empty? > > > I suspect the django_q error is because you need to run `django-admin > migrate`[1], but it isn't responsible for your inability to get list > pages. > > Again, what's in Django's logs? These are not the uwsgi logs. If you > don't know where they are, look in your Django settings in the > LOGGING definition for the filename setting for the file handler. > > [1] The actual name of the Django admin command may be > `django-admin`, `python manage.py` or something else depending on how > Mailman web is installed. > Thank you, A couple of things, running django-admin complains about: Note that only Django core commands are listed as settings are not properly configured (error: Requested setting INSTALLED_APPS, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings.). which *that* error gets replaced by: django.core.exceptions.ImproperlyConfigured: settings.DATABASES is improperly configured. Please supply the ENGINE value. Check settings documentation for more details. with the command: python venv/lib/python3.12/site-packages/mailman_web/manage.py migrate which *might* be the wrong manage.py but other than the change with the migrate command, without it looks to throw the same output. The Django log was at that time empty it's now attached (larger than I'd like). It does seem like some configuration isn't quite working. Maybe *badly* not working with some change that happened. It's not a huge deal, this is more a "fun project" for me. This part of it isn't so much fun.

7 months, 1 week

[MM3-users] Re: Upgrade

by Darren Smith

Nice...spoke too soon. Mailman info works, but when attempting to start mailman I'm now getting this: Traceback (most recent call last): File "/opt/mailman3/conda/bin/mailman", line 11, in <module> sys.exit(main()) File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 722, in __call__ return self.main(*args, **kwargs) File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 676, in main _verify_python3_env() File "/opt/mailman3/conda/lib/python3.6/site-packages/click/_unicodefun.py", line 118, in _verify_python3_env 'for mitigation steps.' + extra) RuntimeError: Click will abort further execution because Python 3 was configured to use ASCII as encoding for the environment. Consult http://click.pocoo.org/python3/for mitigation steps. This system lists a couple of UTF-8 supporting locales that you can pick from. The following suitable locales where discovered: aa_DJ.utf8, aa_ER.utf8, aa_ET.utf8, (followed by a bijillion others) -Darren On Mon, Apr 16, 2018 at 11:25 AM, Darren Smith <silas.crutherton(a)gmail.com> wrote: > Boy howdy did that work... > > Thanks! > > > On Mon, Apr 16, 2018 at 11:22 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 04/16/2018 10:12 AM, Darren Smith wrote: >> >> > "/opt/mailman3/conda/lib/python3.6/site-packages/sqlalchemy/ >> engine/strategies.py", >> > line 160, in create >> > engineclass.__name__)) >> > TypeError: Invalid argument(s) 'pool_pre_ping' sent to create_engine(), >> > using configuration PGDialect_psycopg2/QueuePool/Engine. Please check >> that >> > the keyword arguments are appropriate for this combination of >> components." >> > >> > Anyone able to point me where to go to look for a solution for this? >> >> >> You need to update SQLAlchemy to >= 1.2 for this, but there is another >> issue that requires at least 1.2.3 (current is 1.2.6) >> >> >> -- >> 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 >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> > >

7 years, 1 month

[MM3-users] Re: Messages attached to probe messages

by Mark Sapiro

On 7/12/22 12:36 AM, Bjoern Franke via Mailman-users wrote: > Hi, > > some time ago I started a discussion where I wrongly assumed that probe > messages were sent accidentally from example.com > > Some digging showed now that the sender of the probe messages are > correct, but the attached messages seem to be wrong. > > An attached example for bouncing messages was: > > From: Mailman <mailman(a)example.com> > To: Mailman Bounces <mailman-bounces(a)example.com> > Subject: SMTP Delivery Failure > Message-ID: <165577237837.35.8042057157021349872@mailman-core> > Date: Tue, 21 Jun 2022 00:46:18 +0000 > Message-ID-Hash: TOJ7WDT3TXWOEHZB4USRUOPZUW7BEATI > X-Message-ID-Hash: TOJ7WDT3TXWOEHZB4USRUOPZUW7BEATI > > Mail to bjo(a)schafweide.org failed at outgoing SMTP > > Error code: 554 > Error message: b'5.7.1 Spam message rejected' That's a fake DSN created by Mailman's outgoing runner. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/outgoi…. There will be nothing in Mailman's smtp.log regarding receipt of this message because this message is not received via SMTP, but see below. It is created when the outgoing runner gets a 5xx refusal and the runner calls the bounce processor directly with this fake DSN to process this refusal as a bounce. > I took a look into the logs and found no example.com, but: > > Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) handling connection > Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) >> b'LHLO mail.ffnw.de' > Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) >> b'MAIL > FROM:<yzvotmm(a)forestanes.mom> SIZE=293338' > Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) sender: > yzvotmm(a)forestanes.mom > Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) >> b'RCPT > TO:<vorstand(a)lists.ffnw.de>' > Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) recip: > vorstand(a)lists.ffnw.de > Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) >> b'DATA' > Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) >> b'QUIT' > Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) connection lost > Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) Connection lost during > _handle_client() The above is the receipt of the post whose delivery to some recipients failed. > Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> > response exception: (554, b'5.7.1 Spam message rejected') > Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> > response exception: (554, b'5.7.1 Spam message rejected') > Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> smtp to > vorstand(a)lists.ffnw.de for 6 recips, completed in 0.7157599925994873 > seconds > Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> post to > vorstand(a)lists.ffnw.de from vorstand(a)lists.ffnw.de, 294362 bytes, 6 > failures > Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> > delivery to foo(a)stadel.info failed with code 554, b'5.7.1 Spam message > rejected' > Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> > delivery to abc(a)ffnw.de failed with code 554, b'5.7.1 Spam message > rejected' > Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> > delivery to def(a)ffnw.de failed with code 554, b'5.7.1 Spam message > rejected' > Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> > delivery to xyz(a)ffnw.de failed with code 554, b'5.7.1 Spam message > rejected' > Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> > delivery to bjo(a)schafweide.org failed with code 554, b'5.7.1 Spam > message rejected' > Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> > delivery to blabla(a)osnabrueck.freifunk.net failed with code 554, b'5.7.1 > Spam message rejected' > Jun 21 00:46:49 2022 (35) > <165577240769.30.3077851374384466408@mailman-core> smtp to > vorstand(a)lists.ffnw.de for 1 recips, completed in 0.5507137775421143 > seconds The various messages like > Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> > delivery to bjo(a)schafweide.org failed with code 554, b'5.7.1 Spam > message rejected' are logged by the outgoing runner when it receives a 5xx reject and creates a bounce with a fake DSN. -- 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: To what extent can mailman 3 handle images and html?

by Mark Sapiro

On 10/20/19 2:11 AM, Paul Arenson wrote: > Hi > > The other day I attempted to send a message from my mail client (Apple computer, Mail program, html--well, what they call Rich Text). While a user was able to send a message previously that contained an image, I was unsuccessful. It should be the same as Mailman 2.1. What are your settings for content filtering. In Postorius the only thing exposed are Settings -> Alter Messages -> Filter content, Collapse alternatives and Convert html to plaintext. If this Filter content Yes, content is filtered according to the other two settings and MIME parts may be removed according to the list settings filter_types, pass_types, filter_extensions and pass_extensions. These settings exist in core, but aren't exposed in Postorius. For a new MM3 list these settings are empty, but for a list imported from Mailman 2.1, they are set according to the corresponding MM 2.1 settings. I suspect in your case the issue is Filter content and Collapse alternatives are both Yes. Or perhaps the issue is HyperKitty's rendering of the message > As well, links were weird. > > LINKS > ===== > Because My wordpress often has a Japanese URL and they can become very long, I tried both the URL as is and embedded (made a clickable html link). > > URL > === > So while I typed > https://www.tokyoprogressive.org/journalist-ito-shiori-sues-alleged-rapis.... > > It came out double as > > https://www.tokyoprogressive.org/journalist-ito-shiori-sues-alleged-rapis... > <https://www.tokyoprogressive.org/journalist-ito-shiori-sues-alleged-rapis... > (The full link was truncated with ... at the end, and the link appeared twice with the second instance preceded by "">") I think the doubling is due to your MUA. The truncation of the displayed link in HyperKitty is expected, but the link itself should reference the full URL. > The embedded one did not come out embedded buy showed the text like this: > Alternate link: 多摩川河川敷に男性の遺体、増水した川に流されたか > <https://www.tokyoprogressive.org/%e5%a4%9a%e6%91%a9%e5%b7%9d%e6%b2%b3%e5%... What do these look like in the message received from thge list as opposed to HyperKitty? > QUESTION 1: Is there a preferred way to write links, or will there always be problems with the mail clients? > (Even the web archive shows this problem though): > > https://list.tokyoprogressive.org/hyperkitty/list/discuss@list.tokyoprogres… See what this looks like at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> > See the top item Homeless man drowns in river during Typhoon and what I mean. The first of those 3 links actually works. The other two don't work because the Japanese characters have been encoded as hex values by your MUA (which may be HyperKitty if you are posting via HyperKitty. To answer your question, you can just type the URL as you did above in your thread link, or you can surround it with angle brackets as I did in my message link. If you don't use angle brackets, it should be surrounded by whitespace to avoid ambiguity. See <https://www.rfc-editor.org/rfc/rfc3986#appendix-C> > IMAGE > No image appears though one was added inline. > > And, as I said, a user was previously able to add one. I do not know how she did it. I also posted it to my web site instead of the newsletter for unrelated reasons. But there was an image (Originally got a warning the message was held because the attachment or something). > > So are there guidelines one whether/how to attach an image so that it makes it? Are you posting via email or HyperKitty? If by email, I suspect the issue is Filter content and Collapse alternatives are both Yes. If by HyperKitty you can only post plain text. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

DEBUG var True: [02/Aug/2017 16:43:42] "GET /postorius/lists/ HTTP/1.1" 200 3645 [02/Aug/2017 16:43:48] "GET /accounts/login/?next=/postorius/lists/ HTTP/1.1" 200 10950 [02/Aug/2017 16:43:49] "GET /static/CACHE/css/hyperkitty.2f591b4e31fe.css HTTP/1.1" 200 156657 DEBUG var False: [02/Aug/2017 16:46:46] "GET /accounts/login/?next=/postorius/lists/ HTTP/1.1" 200 10001 [02/Aug/2017 16:46:46] "GET /static/CACHE/css/b3547a2ab51b.css HTTP/1.1" 404 107 [02/Aug/2017 16:46:46] "GET /static/CACHE/css/4c17bb8058aa.css HTTP/1.1" 404 107 [02/Aug/2017 16:46:46] "GET /static/CACHE/css/d6cbfc945441.css HTTP/1.1" 404 107 [02/Aug/2017 16:46:46] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" 404 105 [02/Aug/2017 16:46:46] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" 404 105 El mié., 2 ago. 2017 a las 10:56, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/02/2017 07:55 AM, Rafael Mora wrote: > > HyperKitty is looking for some files in /static/CACHE/... but it doesn't > > find them: > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/b3547a2ab51b.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/4c17bb8058aa.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/2fa1cba00450.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > 404 > > 105 > > [02/Aug/2017 14:53:39] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > 404 > > 105 > > > > > > Should I run any command to activate the CACHE dir? > > > You need to ensure you have a working sass compiler. As I said at > < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > >, > See the third bullet under > <http://docs.list.org/en/latest/prodsetup.html#dependencies>. > > Then you need to run commands like > > django-admin collectstatic --clear > django-admin compress > > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 10 months

[MM3-users] Re: Bulk delivery status change?

by Stephen Daniel

OK. Ran the script. No errors while running it, but when I look at the users through Postorius GUI, they still show as 'Disabled by Bounces' ?? On Sun, Nov 10, 2024 at 11:42 AM Stephen Daniel <swd(a)pobox.com> wrote: > Thanks all! I will use these pronto. > > On Sun, Nov 10, 2024 at 11:42 AM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 11/10/24 08:34, Odhiambo Washington via Mailman-users wrote: >> > On Sun, Nov 10, 2024 at 7:16 PM Stephen Daniel <swd(a)pobox.com> wrote: >> > >> >> Mistakes were made, and for while every single outbound email bounced. >> >> I've fixed the mistakes, but now in my largest and most active email >> list, >> >> every single user's delivery status is "Disabled by Bounces". >> >> >> >> Is there a way to bulk fix this? Or do I have to go into each user, >> one at >> >> a time, and fix them? >> > >> > Please see this thread: >> > >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >> >> The script in that post does all lists. For a single list see >> >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >> but note that the command line >> ``` >> $ shell -l list(a)example.com >> ``` >> should be >> ``` >> $ mailman shell -l list(a)example.com >> ``` >> >> -- >> 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/ >> Archived at: >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >> >> This message sent to swd(a)pobox.com >> >

6 months, 4 weeks

[MM3-users] Re: where to configure max_days_to_hold on MM3 GUI interface?

by Shashikanth Komandoor

Hello Mark, Thanks for helping me for moving ahead in my project. Troubling you again, I would like to put another request at you. As per your suggestion, I am trying to configure my list configuration through REST API for specially the parameter like max_days_to_hold as it is not available through interface and I am following the official links of mailman 3 i.e https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/listconf.html But I am getting "name is not defined" sort of errors as below: *>>> dump_json('http://localhost:9001/3.0/lists/ <http://localhost:9001/3.0/lists/>','ant(a)example.com/config <http://ant@example.com/config>',dict(display_name='My List'),'PATCH')Traceback (most recent call last): File "<stdin>", line 1, in <module>NameError: name 'dump_json' is not defined>>>* Actually I am new to REST API but hope this is the only issue that is preventing me to go ahead. Could you please help me by saying how should I handle this so that I should be able to configure *max_days_to_hold* of a list or multiple ? On Wed, Jan 29, 2020 at 11:20 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/28/20 8:42 PM, Shashikanth Komandoor wrote: > > > > But I could see that parameter value configurable on MM2 GUI > > interface in General Options but I don't see the same on the MM3 GUI > > interface. > > > There are many core settings not (yet) exposed in Postorius. > max_days_to_hold. is one of them. It can be set via `mailman shell` or > via the REST API > < > https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/rest.html#re… > >. > > -- > 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/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

5 years, 4 months

[MM3-users] Re: Problem creating list members using REST API

by Stephen Daniel

I can give you a program written in Go. Would that be helpful? On Tue, Jan 18, 2022 at 6:49 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/18/22 2:11 PM, Stephen Daniel wrote: > > The REST API documentation is a bit informal. As someone who is not > > familiar with mailman, and who doesn't know python, they are a bit of a > > slog. > > > Agreed. I guess we sort of assume that people dealing directly with the > REST API are familiar with both. > > > > It might be worth seeing if the code can be enhanced to allow the boolean > > values to be sent in using JSON booleans as well as JSON strings. > > > I think here we only have to deal with the REST API because other uses > of as_boolean are all on strings that come from config files. We can't > modify as_boolean directly, as it is part of a third party dependency > and is intended to be used with config files, not JSON objects, but I > think something like this will do it. > ``` > --- a/src/mailman/rest/helpers.py > +++ b/src/mailman/rest/helpers.py > @@ -249,6 +249,8 @@ class GetterSetter: > """ > if self.decoder is None: > return value > + if self.decoder is as_boolean and isinstance(value, bool): > + return value > return self.decoder(value) > > > > ``` > Perhaps you could try to test that. > > I just created https://gitlab.com/mailman/mailman/-/issues/970 for this. > It would help me in fixing this if you could provide a small piece of > your code that throws the error. > > -- > 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/ >

3 years, 4 months

Search results for query "sapiro"