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

[MM3-users] Re: Twitter OAuth2

by Odhiambo Washington

On Thu, Dec 29, 2022 at 3:44 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/28/22 11:37, Odhiambo Washington wrote: > > On Wed, Dec 28, 2022 at 8:23 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> On 12/27/22 21:46, Odhiambo Washington wrote: > >>> On Tue, Dec 27, 2022 at 8:08 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >>>> > >>>> I see from another post that you've decided against using Twitter, but > >>>> to answer the question, Twitter does not require adding anything to > >>>> SOCIALACCOUNT_PROVIDERS. > >>>> > >>> > >>> I tried it and ended up with: > >>> > >>> ERROR 2022-12-28 08:40:18,895 97440 django.request Internal Server > Error: > >>> /accounts/twitter/login/ > >>> Traceback (most recent call last): > >> ... > >>> allauth.socialaccount.models.SocialApp.DoesNotExist: SocialApp matching > >>> query does not exist. > >> > >> > >> Do you have > >> > >> 'allauth.socialaccount.providers.twitter', > >> > >> in INSTALLED_APPS? > >> > > > > Here is what I have in settings_local.py: > > > > INSTALLED_APPS = ( > > 'hyperkitty', > > 'postorius', > > 'django_mailman3', > > # Uncomment the next line to enable the admin: > > 'django.contrib.admin', > > # Uncomment the next line to enable admin documentation: > > 'django.contrib.admindocs', > > 'django.contrib.auth', > > 'django.contrib.contenttypes', > > 'django.contrib.sessions', > > 'django.contrib.sites', > > 'django.contrib.messages', > > 'django.contrib.staticfiles', > > 'rest_framework', > > 'django_gravatar', > > 'compressor', > > 'haystack', > > 'django_extensions', > > 'django_q', > > 'allauth', > > 'allauth.account', > > 'allauth.socialaccount', > > #'django_mailman3.lib.auth.fedora', > > #'allauth.socialaccount.providers.openid', > > 'allauth.socialaccount.providers.github', > > #'allauth.socialaccount.providers.gitlab', > > 'allauth.socialaccount.providers.google', > > 'allauth.socialaccount.providers.facebook', > > 'allauth.socialaccount.providers.twitter', > > #'allauth.socialaccount.providers.stackexchange', > > ) > > > Did you add an app at https://site.name/admin/socialaccount/socialapp/ > with twitter as a provider? See > > https://django-allauth.readthedocs.io/en/latest/providers.html#twitter-oaut… Exactly, and I have entered all the credentials from the "OAuth 2.0 Client ID and Client Secret" of the twitter developer portal. https://webmail.kictanet.or.ke/~wash/twitter-oauth.png I have checked my settings_local.py several times trying to find out why the entry is ignored. -- 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: django-mailman3 update causing errors

by Darren Smith

So we have pulled all fresh versions of these projects from gitlab as of last Friday: postorius hyperkitty django-mailman3 mailmanclient Django is version 1.11 When we installed, each of these were placed in a conda virtual environment. Postorius, Hyperkitty, and django-mailman3 are all still under a python 2.7 environment. Is that our problem here? Do they need to be in python 3 now? -Darren On Tue, May 1, 2018 at 3:47 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 05/01/2018 01:35 PM, Darren Smith wrote: > > Hello, > > > > In attempting to update our mailman3/postorius/hyperkitty installation, I > > have run into an error after upgrading the django-mailman3 project. > ... > > Any thoughts on why updating django-mailman3 would cause this? > > > To what version did you update? any 1.2 version is part of the migration > of Postorius/HyperKitty to Python 3 and requires > > postorius>=1.2.0b1 > hyperkitty>=1.2.0a1 > Django>=1.11 > django-mailman3>=1.2.0a2 > mailmanclient>=3.2.0b1 > > and is all Python 3 > > > -- > 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: Apple Mail encoding again

by David Newman

On 4/14/22 10:45 AM, Mark Sapiro wrote: > On 4/14/22 10:18, David Newman wrote: >> On 4/14/22 9:50 AM, Mark Sapiro wrote: >>> >>> It could accept a defective message or one with specific defects, but >>> this is problematic for further processing. For example, at least one >>> MUA, Thunderbird, renders such a message with an empty body. >> >> That's not my experience. Mailman 3 accepted without complaint a >> PGP-signed message I sent from Thunderbird 91.8.0 and forwarded it to >> list subscribers with the message body intact. > > > Yes, and that's what we expect, but MM 3 does not accept the defective > message, and T-bird does not render the body of such a message. I.e., if > such a message composed by Apple Mail 15 is sent via a non-Mailman > channel to a T-bird user, the user can't read it. Sorry, I misspoke. The Apple Mail sender used S/MIME signing, not PGP signing. In Thunderbird, I was able to read an S/MIME-signed message the user sent directly to me complaining about the 501 bounce. Thunderbird said the signature was invalid due to the use of an untrusted CA, but I could read the message body. dn

3 years, 2 months

[MM3-users] Re: Permission denied for /list:member:digest:header.txt

by Eric Broens

Thanks again Mark, from the bash_history that seems to be the case, while I intended to run it as mailman user.It looks like only the ownership of the subdirectories and files in /var/lib/mailman3/templates are incorrect.Those in /var/lib/mailman3/lists and other directories are correct. I can't find back if I have changed the ownership of these manually. Is it sufficient to change the ownership manually, or is there another change required too? Best Regards,Eric On Monday, December 14, 2020, 01:59:06 PM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 12/14/20 3:19 AM, Eric Broens via Mailman-users wrote: > Thanks Andi, > I understand that it is a Unix permissions issue.The question is, what process created these files and directories? Mailman runs with its own user. Since these files and directories were created automatically, I expected that these would have been created with the correct permissions. You ran the hyperkitty_import job for these lists as root. It needs to be run as the Mailman 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, 6 months

[MM3-users] Re: Migration from 2.1 to 3

by Ryan Morash

I figured it out. It was a stupid mistake on my part, running the ‘mailman create’ commands as root… chown’ing the /var/lib/mailman3/lists directories to lists:lists solved the issues. From: Mark Sapiro <mark(a)msapiro.net> Date: Wednesday, January 8, 2020 at 1:20 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Migration from 2.1 to 3 On 1/8/20 6:38 AM, Ryan Morash wrote: > I'm running into the same issue, but after some troubleshooting I think the issue isn't with the import21 command. I'm running into the same issue when I create a list using 'mailman create' without importing anything. New lists created through Postorius work fine. Can you please post the `mailman create` command options you are using to create the list. -- 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://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.mailman3.org%2fma… Confidential Transmission This correspondence is confidential and may contain privileged materials or information. It is intended for the use of the addressee only and all others are prohibited from copying or disseminating this message or its contents. If you have received this transmission in error, delete it immediately and notify the sender.

5 years, 5 months

[MM3-users] Re: messages stuck in the bad queue

by Mark Sapiro

On 6/25/23 1:31 PM, Ken Alker wrote: > > I moved the .psv file from the bad queue into the shunt queue. I then > ran "mailman unshunt" (as user 'mailman' while in the virtual > environment). I tailed mailman.log during this process and no logs were > spit out. The date stamp on the .psv file never changed (maybe it does > not when being moved between queues?) and, AFAICT, the file never moved > from the shunt queue. I waited maybe five minutes, tops. I forgot that the extension in the `bad` queue is `.psv` (for preserve). You have to rename it to `.pck`. >>> Is there a way to reprocess the bad queue? >> >> You could just move the messages to the 'in' queue. Changing .psv to .pck in the process. this can be done, e.g., by ``` for file in `ls var/queue/bad/*.psv;do mv /var/queue/bad/$file /var/queue/in/${file/psv/pck};done ``` > I just now tried moving the same message into the 'in' queue but, again, > nothing happened. I left it in there for five minutes. Do I have to > run a program to get it to act on the 'in' queue (I presume that there > is a "runner" that is always looking and taking care of this already as > I presume this is the queue where all 'normal' traffic is handled). Again, you need to change the extension to .pck. > Here are the (obfusacted) results of "mailman qfile > /opt/mailman/mm/var/queue/shunt/1675389793.6945386+2aeaf0015558c9d8380c96142c3fa9d03a8142bc.psv" (the message I was experimenting with): > > [----- start pickle -----] > <----- start object 1 -----> > MIME-Version: 1.0 > Content-Type: text/plain; charset="us-ascii" > Content-Transfer-Encoding: 7bit > Subject: THE-list subscription notification > From: email(a)obfuscated.com > To: the-list-owner(a)lists.obfuscated.com > Message-ID: <167538979369.2390432.521344217673230839(a)obfuscated.net> > Date: Thu, 02 Feb 2023 18:03:13 -0800 > Precedence: bulk > > user(a)domain.tld has been successfully subscribed to THE-list. > > <----- start object 2 -----> > { '_parsemsg': False, > 'envsender': 'email(a)obfuscated.com', > 'listid': 'the-list.obfusacted.com', > 'nodecorate': True, > 'recipients': {'person(a)domain.tld'}, > 'reduced_list_headers': True, > 'version': 3} > [----- end pickle -----] I was assuming these were list welcome messages which they aren't. They are owner notifications, so they were sent to the -owner address and processed through the owner-pipeline, but unless the Debian package changed the default-owner-pipeline, it doesn't contain mime-delete so how they ended up in the `bad` queue is still a mystery. However, what would be the point of resending these at this time? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: Mailman 3 Keeps Forgettings Imported Lists

by Ryan McClung

That explains a lot. Is there any documentation you can provide to show me where I can set a static config/db? On Tue, Jul 31, 2018, 4:22 PM Mark Sapiro, <mark(a)msapiro.net> wrote: > On 07/31/2018 12:39 PM, Ryan McClung wrote: > > I do see the output of the script and it shows the mailing lists being > > created. If you put "${VARIABLE}"@domain.com it outputs correctly. > > > > Also, to that end, the output of lists changes depending on which > directory > > I am in which makes 0 sense. > > > That is the problem. Either your mailman.cfg does not specify a fixed > directory for var_dir or the mailman command(s) you run do not specify a > fixed mailman.cfg. > > If you look, you will probably see a var/ directory is every directory > in which you ran a 'mailman' command and they will all have different > databases, etc. > > -- > 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/ >

6 years, 10 months

[MM3-users] Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Shashikanth Komandoor

Thank you Mark for your response. All the mentioned versions of all the components are taken from my currently running system only in which I am facing the issue. <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 Wed, Oct 28, 2020 at 10:54 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/27/20 12:46 AM, Shashikanth Komandoor wrote: > > > > *### Mailmanclient Version ###* > > > > *commit aaa529808e2d61899f90509da4ea802a70d2c8ff* > > *Merge: ff39dd8 8670751* > > *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in > >>* > > *Date: Thu Oct 15 01:09:32 2020 +0000* > > > This mailmanclient is up to date and does define the get_requests_count > mailing list attribute, so this version must not be whats running in > your mailman installation. Did you install it? > > -- > 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

4 years, 7 months

[MM3-users] Re: Join a Mailman 3 list?

by Mark Sapiro

On 6/8/25 20:18, Cathryn McGuire wrote: > Hi Mark, Stephen & Thomas, > > We've successfully merged our Mailman 2 list into Mailman 3. EMWD worked over the weekend to get it done for our members. We're pretty grateful. > > There are a few things we're trying to get our heads around, specifically to do with the Affinity Web UI. Most of it is pretty self explanatory, and I can see where it will be more aesthetically pleasing to manage, but a few things that aren't so intuitive. Affinity is a proprietary product of EMWD. At one point during the development of Affinity, when Brian C was still alive, I had access to a demo version, but no more. I don't know if there are any EMWD Mailman 3 users on this list, but I suspect your best resource for Affinity questions is EMWD. > Is anyone working with Mailman 3 and Affinity that could help us through the set up? For instance, when I log in as owner and go to change my password, it won't take a new one and asks me (with a pull down menu box) which account I want to change the password for, and it gives me a list of my emails, and also the other owner's email address. When I choose the email I'm logged in under, it says it's not the correct "credentials." > > Has anyone had this issue? Have you actually created an Affinity login? I believe initially, you have to sign up before you can sign in, even if you are the listowner. > Another thing is, and Stephen J. Turnbull prepared us for this, that the transferred membership are all "enabled" but not "registered." I understand we have to send a membership wide notification with a link to the Affinity log in page, and instructions going to the top right hand and clicking on the login icon, putting in their email address (the one in the system) and adding a password OR do they have to "create" a new sign in? If it works like our web UI, they have to create a new sign in. You do too. The process that imports a Mailman 2.1 list to a Mailman 3 list does not create web UI logins. > Thanks for any info you can give us about Affinity. (I see Brian Carpenter was beta testing it 4 years ago.) Cheers, Cathryn I was one of the people working with Brian back then to try out and give feedback on Affinity, but I've probably forgotten all I knew at that time. There may be current EMWD/Affinity users on this list, but as I said, your best support resource is probably EMWD. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 week

[MM3-users] Re: Postorius fails to show list because of a large message being held

by Mark Sapiro

On 7/14/20 3:54 AM, Brian Carpenter wrote: > On 7/14/20 6:49 AM, Gilles Filippini wrote: >> Mailman Core logs: >> [2020-07-14 10:41:21 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:49) >> [2020-07-14 10:41:21 +0000] [49] [INFO] Worker exiting (pid: 49) >> [2020-07-14 10:41:22 +0000] [50] [INFO] Booting worker with pid: 50 > > I am pretty sure that timeout is related to gunicorn. If it is, then > increasing the worker out timeout setting for gunicorn should work. You > tend to get such errors when doing an export of a large membership > roster. This is the first time I have seen it related to a held message. It seems weird that a gunicorn worker would run for more that the default 30 seconds because of a 23MB message, but I think Brian is correct. > I have this in my setup: > > mailman.cfg: > > [webservice] > configuration: /opt/mailman/mm/gunicorn.cfg > > gunicorn.cfg: > > [gunicorn] > workers = 4 > timeout = 900 > > You will need to restart gunicorn after adjusting the timeout setting. It's confusing, but after adjusting that setting, you need to restart Mailman core, not gunicorn. If you are running a gunicorn service, that is what is providing WSGI support for Django (Postorius and/or HyperKitty). You may be using gunicorn for this or uWSGI or Apache mod_wsgi, but is any case, that is not the gunicorn we are considering here. Regardless of what you use to provide WSGI support for Django, Mailman core uses gunicorn to support the REST API, and that is the gunicorn affected by the settings in the gunicorn.cfg pointed to by [webservice] configuration: /opt/mailman/mm/gunicorn.cfg If, with the above configuration, you do `ps -fwwA|grep runner=rest` you will see something like: mailman 20582 20561 0 01:21 ? 00:00:16 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 mailman 20722 20582 0 01:21 ? 00:01:19 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 mailman 20725 20582 0 01:21 ? 00:01:18 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 mailman 20726 20582 0 01:21 ? 00:01:18 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 mailman 20727 20582 0 01:21 ? 00:01:50 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 The first of these, pid 20582, is Mailman's actual REST runner. The other 4 with parent pid 20582 are the 4 gunicorn worker processes forked from the REST runner. It's the REST runner or Mailman core that needs to be restarted to pick up that change. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

Search results for query "sapiro"