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

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

by Jered Floyd

You're welcome. Thank you for all your hard work making Mailman 3 happen at all! I think django_allauth integration is again stable, but for now I'm pinning 0.58.2 + this patch. I'll test again once there is another release notification, but since I rebuild by container image every 2-3 weeks I am getting exhausted by surprises... --Jered ----- On Dec 7, 2023, at 7:44 PM, Mark Sapiro mark(a)msapiro.net wrote: > On 12/7/23 14:33, Jered Floyd wrote: >> >> FYI, The django-allauth author has proposed fixing both of these with an even >> simpler change, which is now upstream and queued for a future release. >> >> --Jered > > > Thank you again for your work on this. I can confirm that the patch > below fixes my issue with > https://msapiro.net/accounts/social/connections/ and SITE_ID = 0. > > >> --- a/allauth/socialaccount/adapter.py >> +++ b/allauth/socialaccount/adapter.py >> @@ -228,7 +228,10 @@ class DefaultSocialAccountAdapter(object): >> provider_to_apps = {} >> >> # First, populate it with the DB backed apps. >> - db_apps = SocialApp.objects.on_site(request) >> + if request: >> + db_apps = SocialApp.objects.on_site(request) >> + else: >> + db_apps = SocialApp.objects.all() >> if provider: >> db_apps = db_apps.filter(Q(provider=provider) | Q(provider_id=provider)) >> if client_id: > > -- > 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 jered(a)convivian.com

2 years

[MM3-users] Re: Mailman 3 - docker container - sync_members

by Abhilash Raj

On Tue, Oct 20, 2020, at 12:27 PM, Mark Sapiro wrote: > On 10/20/20 9:45 AM, holman(a)uw.edu wrote: > > I would like to populate list members via the Mailman 3 sync_members script. > > > > However, I am using Mailman 3 in docker containers and it doesn't appear to have this command. How are others completing this synchronization? > > > I'm not sure what version of Mailman core is in the Docker containers. > According to https://asynchronous.in/docker-mailman/NEWS.html, Mailman > core is docker version 1.1.1 released Aug 9 2017 which is about the time > of MM Core 3.1.0 which is quite old and has neither a `mailman > syncmembers` (introduced in core 3.3.2) command nor the older `mailman > members --sync` option (introduced in core 3.3.1). There are `rolling > releases` <https://asynchronous.in/docker-mailman/#rolling-releases> > which should have these. NEWS file is very outdated, I should remove it. The containers have latest released version if you are using the 0.3 tags and as Mark mentioned, `mailman members --sync` option should work. > > > > Searching this list I found a reasonable approach: > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > > Is there a different/preferred solution? > > > The script at > <https://gitlab.med.stanford.edu/irt-public/mailman-tools/-/blob/master/sync…> > seems fine. The alternative is to update your Docker container to one > including the appropriate `mailman` sub-command. > > -- > 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, Abhilash Raj (maxking)

5 years, 1 month

[MM3-users] Re: Weird hourly indexing error

by Mark Dadgar

On Jun 9, 2020, at 1:23 PM, Mark Sapiro <mark(a)msapiro.net> wrote: >> On Jun 9, 2020, at 11:34 AM, Mark Sapiro <mark(a)msapiro.net> wrote: >>>> ./mm3-admin: line 6: 702058 Killed django-admin $@ >>>> >>>> Now what? >>> >>> >>> Run it as user `list`. >> >> >> Same. > > > It appears that the reference to line 6 is line 6 of your mm3-admin file > which is the `django-admin $@` command. So that command is being killed > by the OS for some reason, probably out of memory. > > Try this instead. > > import pytz > import datetime > start = datetime.datetime(2020, 1, 1).replace(tzinfo=pytz.UTC) > end = datetime.datetime(2020, 2, 1).replace(tzinfo=pytz.UTC) > # These are examples. The args are year, month, day. > # Pick dates for start and end that overlap the start of this issue. > from hyperkitty.models import Email > emails = Email.objects.filter(date__range=(start,end)) > for email in emails: > if email.content.find('\u200b'*5) >= 0: > print('Found in ml {}, hash {}'.format( > email.mailinglist.name, > email.message_id_hash)) > > This will make a much smaller query set than all the emails and should work. I was just writing another email - I had a suspicion on this and I was right: this is the Linux OOM killer in action. Jun 9 13:15:32 mail kernel: [1051406.859205] Out of memory: Killed process 712833 (python3) total-vm:2351156kB, anon-rss:2274112kB, file-rss:2236kB, shmem-rss:4kB, UID:38 pgtables:4616kB oom_score_adj:0 Jun 9 13:15:32 mail kernel: [1051407.042975] oom_reaper: reaped process 712833 (python3), now anon-rss:0kB, file-rss:0kB, shmem-rss:4kB I set up a quick swapfile (there are 581,000 emails in this archive) and it came back with some hashes. I am tracking them down now. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 6 months

[MM3-users] Re: Adding Mass Subscribe custom template error

by Arte Chambers

Ok I did install using the https://docs.mailman3.org/en/latest/install/virtualenv.html I added ``` POSTORIUS_TEMPLATE_BASE_URL='https://www.example.com/' ``` to /etc/mailman3/settings.py and restarted mailman services However I'm still getting the same error from mailman.log ``` requests.exceptions.ReadTimeout: HTTPConnectionPool(host='localhost', port=8000): Read timed out. (read timeout=5) [29/Jan/2025:19:18:08 +0000] "POST /3.1/members HTTP/1.1" 400 128 "-" "GNU Mailman REST client v3.3.5" [29/Jan/2025:19:18:08 +0000] "GET /3.1/lists/ testing@list.louisvillecommunitygrocery.com/requests/count?token_owner=moderator HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.5" [29/Jan/2025:19:18:08 +0000] "GET /3.1/lists/ testing(a)list.louisvillecommunitygrocery.com/held/count HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.5" ``` Not sure if I'm editing the correct config file. Thank you, Paul 'Arte Chambers' Robey 502-408-6922 On Wed, Jan 29, 2025 at 1:27 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/29/25 09:41, Arte Chambers via Mailman-users wrote: > > Where can I find the setting > > ``` > > POSTORIUS_TEMPLATE_BASE_URL > > ``` > > It is in your Django settings. Where these are depends on your > installation, but these are usually in files named settings.py and > settings_local.py. > > If you installed following > https://docs.mailman3.org/en/latest/install/virtualenv.html the default > is in mailman_web/settings/mailman.py but you would override the default > in /etc/mailman3/settings.py > > -- > 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 paul.m.robey(a)gmail.com >

10 months, 2 weeks

[MM3-users] Re: Bounces address spammed

by Enrique Terrazas

Thank you Mark! The requests are coming in via email. We were able to filter these out with the recommendation below. Blocking an entire domain is a bit extreme but I wanted to stop the bleeding. Can you, or someone on the list, point me in the the right direction as far as configuring postfix to protect against Spam campaigns? I’ve started reading through this document: http://www.postfix.org/BACKSCATTER_README.html But am not sure if this is where I should direct my efforts. Enrique On Feb 28, 2019, at 12:44 PM, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: On 2/28/19 9:15 AM, Enrique Terrazas wrote: Greetings, I hope everyone is having a good day. We have a highly visible list that is being spammed with join requests from spoofed addresses. Web or email? When the confirmation email is sent a bounce is received by the list owner. The count is in the 100’s of bounced emails/hour. We noticed they are all coming from one particular domain, this may help if we are able to filter/block the domain. What would be the best way to handle this? Is there a way to handle this granularly at the list level? If the requests are coming by email, you can block the domain in your MTA., E.g. with postfix in main.cf: header_checks = pcre:/etc/postfix/header_checks.pcre in /etc/postfix/header_checks.pcre: /^From:.*[@.]bad.domain\w/ DISCARD or /^From:.*[@.]bad.domain\w/ REJECT We don't accept mail from bad.domain. For web requests, adding a pattern like '^.*[@.]bad.domain$' to the lists "Banned addresses" might help. -- Mark Sapiro <mark(a)msapiro.net<mailto:mark@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<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

6 years, 9 months

[MM3-users] Re: My Server is unable to connect to Mailman REST API few times

by Shashikanth Komandoor

Thank you Mark a lot. It worked awesome. You don't know how much you helped me. Thank you once again. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Sat, Sep 19, 2020 at 8:56 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 9/19/20 4:32 AM, Shashikanth Komandoor wrote: > > > > But I am trying to delete a list on an urgent basis. Because of which I > am > > getting the above said errors. I tried to delete > > through the interface, through curl command and through "mailman shell" > but > > nothing led me to a > > positive result. Is there any work around to delete the list ? > > What have you tried in Mailman shell? This should do it. > > $ mailman shell -l list.example.com > Welcome to the GNU Mailman shell > Use commit() to commit changes. > Use abort() to discard changes since the last commit. > Exit with ctrl+D does an implicit commit() but exit() does not. > The variable 'm' is the list.example.com mailing list > >>> getUtility(IListManager).delete(m) > >>> commit() > > So should just > > $ mailman remove list.example.com > > What happens if you do those? > > -- > 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, 2 months

[MM3-users] Re: Pck files stuck in out queue

by Mark Sapiro

On 2/10/25 13:45, Lieuallen, Thomas Otis via Mailman-users wrote: > Mark, > > Actually, this is saying cache_life under mailman: > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/config/doc… > > There is a cache_lifetime under ‘dmarc’. You are correct. I was confused by the dmarc one. > I used your clue about the database to concoct my own solution… 😊. I edited the ‘expires_on’ values in the file_cache table in the database so the files were expired. > > It looks like the times in that table are UTC. > > I’m going to ratchet down my cache_life so anyone that is playing with templates doesn’t go bonkers (like me) with why their changes aren’t honored. I have a small site, so not much performance impact. That really shouldn't be necessary, but I think there is an issue in the code at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/model/template… which is intended to evict the cache entry for the previous template when a new one is set. If the previous template has a different uri from the one being set, e.g., a mailman:// uri is being replaced by a http(s):// Postorius uri the code will attempt to evict the Postorius uri which is not the cached value. This should not be an issue when just updating a template already in Postorius and should not be an issue when setting a Postorius template to replace one previously the default or in Mailman's var/templates directory as these normally don't have template table entries, but prior to Mailman 3.3.6, the `mailman import21` command would create template table entries for imported lists. This was https://gitlab.com/mailman/mailman/-/issues/988 fixed by https://gitlab.com/mailman/mailman/-/merge_requests/989 > Thank you for your help. You're welcome. I'm glad you solved it.

10 months

[MM3-users] Re: cannot import name 'parse_header' from 'django.http.multipartparser

by Stefan Bauer

Thank you Mark for your swift reply :) Am Do., 27. Feb. 2025 um 20:32 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > On 2/26/25 07:40, Stefan Bauer via Mailman-users wrote: > > Dear Users, > > > > i recently tried to upgrade to latest MM3 and followed this[1] steps. > > > > However > > > > (venv) $ mailman-web migrate > > > > fails with: > > > > from rest_framework import mixins, views > > File > "/opt/mailman/venv/lib/python3.10/site-packages/rest_framework/views.py", > > line 15, in <module> > > from rest_framework.request import Request > > File > "/opt/mailman/venv/lib/python3.10/site-packages/rest_framework/request.py", > > line 17, in <module> > > from django.http.multipartparser import parse_header > > ImportError: cannot import name 'parse_header' from > > 'django.http.multipartparser' > > > (/opt/mailman/venv/lib/python3.10/site-packages/django/http/multipartparser.py) > > (venv) mailman@edmmal03$ vi > > > /opt/mailman/venv/lib/python3.10/site-packages/django/http/multipartparser.py > > > > Could this be a broken dependency? > > > You have an incompatible configuration. > django.http.multipartparser.parse_header was removed in Django 4.2. See > https://docs.djangoproject.com/en/5.1/releases/4.2/#miscellaneous > > Your version of djangorestframework is incompatible with Django>=4.2. > Try in your venv > ``` > pip install --upgrade djangorestframework > ``` > > -- > 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 cubewerk(a)gmail.com >

9 months, 1 week

[MM3-users] Re: Installing mailman 3

by Rafael Mora

For testing purpose I turned back to false the DEBUG var and everything started working fine with HyperKitty I don't understand... this is the trace when I click Login from Postorius to HyperKitty [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 What should I check? 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

8 years, 4 months

[MM3-users] Re: Migrating archives from Mailman21 to Mailman3

by Odhiambo Washington

On Tue, Sep 24, 2024 at 11:33 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 9/24/24 12:03, Odhiambo Washington via Mailman-users wrote: > > On Tue, Sep 24, 2024 at 7:38 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> > >> Yes. There is no requirement that archives have a matching list in > >> Mailman core. > > > > > > So the documentation at > https://docs.mailman3.org/en/latest/migration.html > > needs revision as it creates the impression that a matching list needs to > > be there: > > ``` > > $ python manage.py hyperkitty_import -l foo-list(a)example.com > > $var_prefix/archives/private/foo-list.mbox/foo-list.mbox > > ``` > > > Are you saying that the above quoted command is what gives that > impression? I don't see that `foo-list(a)example.com` is the name of the > list for the HyperKitty archive only and > `$var_prefix/archives/private/foo-list.mbox/foo-list.mbox` is the MM 2.1 > mbox. > > If you are saying something else gives that impression, what in > particular is that? > My thinking around the above was that `foo-list(a)example.com` refers to a Mailman list. But now I am beginning to think that it's only a listname for HyperKitty and the list doesn't necessarily have to exist in Mailman Core. Is that right? The fact that the command was referenced during the migration of an ACTUAL list is what created the impression (in my mind) that the list must also be a valid list for the Core. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 2 months

Search results for query "sapiro"