Search results for "Postorius" - Mailman-users

Re: Turn off social logins?

by Nick Wynja

On 02/10/19 at 08:57, brian(a)emwd.com <brian(a)emwd.com> wrote: > "In your `settings_local.py` copy the whole INSTALLED_APPS section from [default settings](https://github.com/maxking/docker-mailman/blob/master/web/mailman… and add/remove the auth providers you want/don't want. Notice the `allauth.socialaccount.providers.<provider>` in the list below." Another option, which seems more future-proof, is to strictly remove the account providers you don't want from INSTALLED_APPS rather than defining INSTALLED_APPS locally. First, you have to access INSTALLED_APPS by importing settings into settings_local.py: ``` from settings import * ``` Then, you can set INSTALLED_APPS to everything it already is minus the social providers: ``` INSTALLED_APPS = [a for a in INSTALLED_APPS if not a.startswith('allauth.socialaccount.providers') and not a.startswith('django_mailman3.lib.auth.fedora')] ``` This way if Postorius ever adds any apps you won't need to update your local settings. Anyone see any downsides to doing it this way? -- Nick Wynja https://nickwynja.com

6 years, 11 months

Re: How to promote non-members to members?

by Mark Sapiro

On 3/15/22 11:16, Quanah Gibson-Mount wrote: > Hello, > > We have a constant issue with confirmation emails for subscribers > getting lost and then the subscriber contacting us because their posts > to the list never show up. Is there a way I can, as an administrator, > do the confirmation on their behalf or in some other way promote them to > being a member from non-member? See this thread https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… If they don't have an outstanding subscription waiting user confirmation, you can just mass subscribe them. If they do and your Postorius and Mailman core is reasonably up to date, you can find the pending request at Subscription requests -> Pending Confirmation, delete it and then mass subscribe them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

Messages not going to held queue

by Stephen J. Turnbull

Mail Person writes: > Not sure why, but messages set to be held for moderation There are quite a few settings that can result in moderation holds. Which are you talking about, and exactly what is the setting? > appearing to be discarded. Have you checked the other logs? A discard should show up in the 'vette' log. If there's no notice there, the message should be stuck in some queue, my first guess is shunt, but it could be anywhere. > smtp.log shows the message is going through but it doesn't get to > the moderation queue. How do you know? Do you mean moderators don't get email that the message is held, or have you checked in Postorius and it tells you no messages are available for moderation? I believe that if the message is waiting for moderation it should be in the 'pipeline' queue. Steve

3 years, 4 months

Re: "Private archives" aren't private

by Mark Sapiro

On 06/04/2017 07:47 AM, Simon Liebold via Mailman-users wrote: > OK, no problem there: > > <QuerySet [(u'simsimmer(a)lists.simonliebold.de', 2L)]> >> >> It's possible that you changed the archive_policy of a list and the >> change wasn't reflected in Hyperkitty. > Postorius is showing the list's settings as "Private archives" (see > screenshot). But apparently this setting doesn't do anything when > switching it to "public" and back to "private". It always returns '2L'. > Don't know if this is expected. Just to be sure, if you are just repeating the MailingList.objects.all().values_list('name', 'archive_policy') command, you won't be seeing the current value. You have to do either abort() or commit() to flush the previously retrieved data. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 7 months

Re: Member Issue Discovered

by Brian Carpenter

On 10/28/20 4:29 PM, Mark Sapiro wrote: > On 10/28/20 11:11 AM, Apollinaris Schöll wrote: >> Most important is to offer an UI to completely delete users for subscribers and list admins. Currently delete account shows this message "Are you sure you want to delete your account? This will remove your account along with all your subscriptions.” >> This is not true and needs to be done. > > Why do you think it's not true? With current Mailman from the HEADs of > the GitLab branches, the only thing not removed is posts from the > archives. The Django account and the Mailman core user and address > records are all removed. This is a bug with Affinity which I have scheduled to be fixed. However I am confused. Data is completely removed from Mailman 3 core when you delete the account via Postorius but not when you unsubscribe from a list? -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 3 months

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/ > >

8 years, 3 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

5 years, 2 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.

6 years, 3 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

3 years, 3 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

3 years

Mailman-users search results for query "Postorius"