Search results for "Postorius" - Mailman-users

Re: how do I bulk-remove users from ML in MM3?

by Andrew Hodder

I assume you mean from the command line, since mass remove can be done from the postorius interface for the list. Checking the 'mailman members -h', I don't see any options for mass removal (strange since add has a function). This might be a consequence of the way members are now tied to ownership in lists (changed from MM2>MM3). Sincerely, Andrew Hodder Systems Administrator Support Operations, Afilias E-mail: drew(a)afilias.info Phone: +1 416.673.4164 Fax: +1 416.646.1541 On Wed, Oct 25, 2017 at 3:08 AM, Dmitry Makovey <dmakovey(a)stanford.edu> wrote: > > I just realized that "mailman members" only offers to "add members" via > "-a filename" but I see no remove option. > > -- > Sr System and DevOps Engineer SoM IRT > > > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > >

7 years, 7 months

Re: mailman-suite: Error 500 on Lists /setting/ pages

by Brian Carpenter

On 11/18/20 11:43 AM, ljsbw-it(a)riseup.net wrote: > I just installed Mailman3 (mailman-suite) on my Server following these instructions:https://lab.uberspace.de/guide_mailman-3.html and everything works fine so far. I can create lists, subscribe people and send mails through lists but when I click the settings button and get redirected to/postorius/lists/listname/settings/ i get an Error 500 message. I couldn't find anything in the logs except the uwsgi log: > [pid: 20568|app: 0|req: 62/62] 100.64.115.1 () {48 vars in 1052 bytes} [Wed Nov 18 16:27:59 2020] GET/postorius/lists/listname/settings/ => generated 1102 bytes in 1438 msecs (HTTP/1.1 500) 6 headers in 209 bytes (1 switches on core 0) > _______________________________________________ > Mailman-users mailing list --mailman-users(a)mailman3.org > To unsubscribe send an email tomailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ What web server are you running and have checked its logs? -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 7 months

Re: Converting discussion list to read-only list (settings)

by Paul Arenson

Mark Sapiro wrote: > Issue is HyperKittyb-when replying to a message in an existing thread instead of >using the 'reply' action on that message, they use the Start a new thread button. So then >If by "read only" you mean the "Announce only mailing list style" as >opposed to the "Ordinary discussion mailing list style" the only >difference is that for the Announce only style the list attribute >allow_list_posts is False and for the Discussion style, it's True. > >This is the setting in Postorius -> Settings -> Alter Messages -> >Include the list post header an all it does is include or not include >the List-Post: header in mail from the list. Ok...there is no specific setting I see "allow_list_posts" but you wrote "Include the list post header " later on. So i set THAT one to NO? Thank you.

5 years, 8 months

Re: Sanity check of upgrade procedure

by Mark Sapiro

On 10/26/22 17:30, David Newman wrote: > > OK, thanks. Before getting to mistune, this command, run as mailman in a > venv: > > pip install -U mailman postorius django-mailman3 hyperkitty mailman-web > uwsgi Mailmanclient > > produced this error: > > .. > > Attempting uninstall: mailman-web > Found existing installation: mailman-web 0.0.6.dev9+gc606169 > Uninstalling mailman-web-0.0.6.dev9+gc606169: > Successfully uninstalled mailman-web-0.0.6.dev9+gc606169 > ERROR: Could not install packages due to an OSError: [Errno 13] > Permission denied: 'WHEEL' > Check the permissions. > > The command also said I needed to upgrade pip. Doing that produced a > similar error. > > How to resolve this error? Thanks again. Was the venv initially created as the `mailman` user? Maybe sudo chown mailman:mailman /path/to/venv will fix it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

Re: MM2 -> MM3 Migration

by Mark Sapiro

On 12/29/22 23:17, Odhiambo Washington wrote: > On Thu, Dec 29, 2022 at 10:39 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> The default without the since= option is to import only those messages >> from the mbox which are newer than the newest message in the existing >> archive which is exactly what you want. >> > > So I ended up using this and I can see the list metrics indicating that the > last post was on 29Dec22, but > I don't seem to be able to see those posts in the archives. If Postorius list metrics show the last post was 29 Dec, that was a post to the MM3 list and if it was archived, then running hyperkitty_import without a since= option will not import any messages older than that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

Re: Template Ignored?

by Mark Sapiro

On 2/17/22 08:04, Stephen Daniel wrote: > Mailman3 people -- > > I created a new list, and used postorius to create a template for " > list:user:notice:welcome". I then used the mass subscription feature to > add myself to the list, having checked "pre-confirmed", "pre-approved", and > "pre-verified". > > I received a welcome message that appears to be the default welcome > message. It certainly wasn't what I put into my template. > > Any suggestions on how I get mailman to use my template? Things I might be > doing wrong? What is your setting for POSTORIUS_TEMPLATE_BASE_URL? If you create a full URL by appending `/api/templates/list/list.example.com/list:user:notice:welcome` to that where `list.example.com` is the actual list_id of your list, and go to that URL, what do you get? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

Re: Held messages: Long time waiating for response of the Mailman API

by Mark Sapiro

On 1/27/22 05:22, Stephan Krinetzki wrote: > > I think there is a communication problem in the chain: > > apache -> uwsgi -> mailmancore/API ->database > > but i can't dig deeper there. Let me know if i should provide more details or logs It seems that this part of the chain apache -> uwsgi -> mailmancore/API is not experiencing delay. It is involved with every Postorius request, most of which seem to have no issues. It is only this one piece mailmancore/API ->database that seems to have an issue and only with this one DELETE FROM pendedkeyvalue WHERE pendedkeyvalue.id = XXX query. However, like you, I have no idea as to what you could do further to debug this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

Re: Emergency moderation and clearing out a lot of held messages

by Mark Sapiro

On 11/11/22 10:23, Stephen J. Turnbull wrote: > > The two database configuration is not really a recommendation. I > suppose the practice derives from an abundance of caution, as there > are concepts like "User" that must be implemented in somewhat > different ways across components (core doesn't authenticate users, > while Postorius's primary function is authentication of users). I > myself would worry that there might be name collisions among tables, > which would cause mayhem, but that's probably excessive. FWIW, the Mailman3 installations at both mail.python.org and lists.mailman3.org use a single database and with the exception of Mailman core's tables and Postorius' `template` table, tables are prefixed with application names like `auth`, `django_` and `hyperkitty_`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

Re: Docker mailman3 delete social logins, did something change?

by bob B

Got, Per someones advice I waiting and the bad gateway error cleared. I was being impatient. But I looked at the variables using (docker exec -it mailman-web python3 manage.py print_settings) and INSTALLED_APPS = ['hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', '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'] so in /opt/mailman/web/settings_local.py. I added a modified version INSTALLED_APPS = ['hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', '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'] And the social are gone!!!!!!!

3 years, 9 months

Re: Digest Formatting

by mailman＠manygoodideas.com

mailman＠manygoodideas.com wrote: > I have 2 more digest questions, which I'm hoping to get insight on: > 1) Is there a way to trigger a digest for a user (for testing purposes)? Specifically, > is there a function that can be revealed via the REST api to an interface like Postorius > and Affinity? > 2) I have customized list:member:digest:header, but am not seeing the custom text where > I thought it should be. The documentation seems to imply that both > list:member:digest:header and list:member:digest:footer surround each message in the > digest, with the digest starting with list:member:digest:masthead. What I'm seeing is > list:member:digest:masthead, which is followed by list:member:digest:header, then the TOC, > then all the digest entries. I also have a feature request (I didn't see it in the docs), consider creating list:member:digest:mastfoot – a chunk of text that could be at the end of the digest. Thanks.

4 years, 7 months

Mailman-users search results for query "Postorius"