Search results for "Postorius" - Mailman-users

Re: "Unsubscribe all" failed with large lists

by Abhilash Raj

thanks, Abhilash Raj On Wed, Jan 20, 2021 at 10:34, Alan So <ktso(a)cuhk.edu.hk> wrote: > We are currently testing latest mailman suite (w/Postorius 1.3.3) and > notice that that the the API call > /3.1/lists/listname.domain/roster/member failed when using > "Unsubscribe all" on Postorius for a large list (~15000 members). > Not sure whether the issue has been already reported or not. It has been reported before for sure, but I couldn't find an issue tracking it in Postorius' tracker so I created one[1]. The Core and Mailmanclient already have a mass-unsubscribe API that doesn't require looping over all address and unsubscribing them one by one, it just needs to be plumbed through in P, in case someone wants to take a stab at it. [1]:https://gitlab.com/mailman/postorius/-/issues/464 > _______________________________________________ > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>

4 years, 4 months

Re: postorius configuration of the from-part

by Wolfgang Bock

Hello, thanks for your information. After creating the dmarc-entries in the DNS-databases everthing works as wanted! Regards Wolfgang Am 13.11.2019 um 06:02 schrieb Mark Sapiro: > On 11/12/19 2:27 PM, Wolfgang Bock via Mailman-users wrote: >> Hello, >> >> can someone give me an advice how I can configure in the >> postorius-menues the view of the from-part of my list-member like in >> this mailinglist: >> >> Wolfgang Bock_via Mailman-users_ <mailman-users(a)mailman3.org> > > The above is the result of Settings -> DMARC Mitigatations -> DMARC > mitigation action = "Replace From: with list address" > > You can apply that to only messages From: a domain the publishes a DMARC > policy of reject or quarantine or to all messages depending on DMARC > Mitigate unconditionally. > > >> case 1 reply goes to the list or to the member >> case 2 reply goes only to the list > > The DMARC Mitigatations settings are independent of the various reply > settings on the Alter Messages tab. >

5 years, 6 months

Re: [EXT] - moving lists to another server

by Stephen J. Turnbull

Bryan Kartzman writes: > Wow, thanks for the very thorough response, Steve. > > I should have started by saying that when we built the current > production server, we cloned it off the test server and we were > thinking now to move the data onto another clone of the old test > server. So, yes we would have to apply all the changes we made > since we cloned the current production server, but everything else > as far as the OS is concerned should be comparable (webserver, MTA, > Mailman core, Django, Hyperkitty, Postorius). That's why I was just > asking about the "data" aspects of > mailman/hyperkitty/postorius. What would I have to move to > replicate all the lists on the current production server to a new > clone of the original test server once we've applied any changes we > made to production server since the clone. If you're using the same instance of the database, and the transient queues are clean, then once you've applied those changes you just point Mailman core, HyperKitty, and Postorius at the database. If you need to copy the database into a different instance that's already running, *pro-ba-bly* you can just dump the 'mailman' database (and if you have a separate 'mailmanweb' database for Postorius and HyperKitty, that one too) as SQL code. Then load them into that database (make sure there's nothing in the SQL that messes with any existing databases in the RDBMS). If you have a fresh new instance of the database it's the same but no worries. Steve

1 year, 7 months

Re: Mailman, etc. upgrade woes and persistent bugs

by Brian Carpenter

On 2/13/21 10:53 AM, Jim Popovitch via Mailman-users wrote: > But how do you display a "Membership List page" for admins in MM3 > (choice of wording is specific to other emails you've posted today) > without third-party application(s), and isn't that too a shortcoming in > MM3 due to that functionality being present in MM2? Look, without a > doubt the REST API of MM3 Core is cool, but let's be honest, all the 3rd > party wrapping and baggage is, well, not so cool. But, again being > honest, you can't have a MM3 system without all of those things. With > MM2 we have all those things, and we are happy with them.:) Affinity is just a UI that sits on top of Mailman 3 core. Most of its functions and displays come from Mailman 3 core. Everything I mentioned about how Affinity displays List Member Management to List Owners uses MM3's REST api to do so. In my opinion, Postorius is nowhere near in taking advantage of all that Mailman 3 core offers along with free tools such as Bootstrap 4. The only thing that is holding Postorius back is time to improve it and that is not the fault of MM3 or the developers. The thing to take away from this however is Postorius still has the potential (because the foundation is there) to be a great modern UI for Mailman 3 core. MM2 does not have that potential and never will. Sure it works until it doesn't. I am pretty sure Pipermail is a wrapper and not an inherit part of MM2. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 3 months

Moderation action "None" is misleading

by Stephen J. Turnbull

Markus Grandpré writes: > I find the use of the term 'None' (or 'Kein' in the German > translation; see attachments) This list does not allow attachments. Please be more explicit in your explanations (see comments below), or (preferred, because it's unlikely that action will take place soon, and mailing list conversations are forgotten in a few weeks at most) create an issue (probably at https://gitlab.com/mailman/postorius/-/issues/) and attach the files there. > in the 'Moderation action' column of the member list misleading, as > the term suggests that no moderation action is applied to the > respective member. > > However, this is not necessarily the case. If you check a member’s > "Administration options / Moderation" setting, a moderation action, > such as "Moderation" or "List default", may be in effect. I don't understand. My users are pretty innocuous so "List default" and "Default processing" are in fact what is displayed in my installation (Mailman 3.3.10 and Postorius 1.3.13). If I change one subscriber to "Hold", that is what is displayed after refreshing the user list screen. What versions of Mailman and Postorius are you using? If you are using current Mailman, perhap the German translation is inaccurate. > I suggest that the 'Moderation action' column should display the > currently set value of the 'Administration options / Moderation' > setting for each member. See also https://gitlab.com/mailman/postorius/-/issues/188 for a related issue in a different context (the user's preferences page). The issue there is wanting the effective setting in cases where a list or user setting is in effect but the user's list of subscriptions shows "----".

4 months

Re: Moderated unsub requests are not provided by mailman3 service

by Mark Sapiro

On 11/29/24 4:47 PM, Joachim Schrod wrote: > > The unsubscriptions requests are not shown in the web interface. I > suppose they should appear in the UI section "Subscription requests", > either as "Pending Approval" or "Pending Confirmation". (Frankly, I > don't understand the difference between these two options at all.) Subscriptions pending confirmation are those waiting for the user to confirm. Those pending approval are waiting for moderator approval. Unsubscription requests not being shown is https://gitlab.com/mailman/postorius/-/issues/332 which was fixed in Postorius 1,3.6 released over 3 years ago. Current release is 1.3.13. > System information: mailman3 3.3.3; Postorius (mailman3-web) 1.3.4; > both on Debian 11 (bullseye). > > I know that this is out of date; thus a definitive info "this is fixed > by now" is quite OK for me. (Debian upgrade is planned as the next > action after getting Mailman3 to work for that use case.) Yes, this is fixed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 1 week

Re: MM3 on debian - redirect problem

by Mark Sapiro

On 4/27/20 8:17 AM, Gelpi Andrea wrote: > Hi, > on a debian10 I have mm3 installed via apt-get > > apt-get install mailman3-full > dpkg-reconfigure mailman3 > dpkg-reconfigure mailman3-web > > I have this minor issue > > https://webserver/mailman3 redirects to > http://webserver/mailman/postorius/lists/ > > that doesn't exist. > > The same problem form django admin page to return to lists > > https://website/mailman3/admin/sites/site > > In the upper right corner I have a link to https://webserver/mailman3 > that redirects to https://mailman/postorius/lists/ > > I searched for a redirect but without success. The redirection must be a web server issue. There is a urls.py file probably in the same directory as your django settings - probably /usr/share/mailman3-web/urls.py in your case. You can make a URL like http://webserver/mailman/postorius/lists/ work by adding url(r'^mailman/postorius/', include('postorius.urls')), to the urlpatterns list in the urls.py file. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

Re: Mailman backend maintenance task

by Abhilash Raj

> On Aug 24, 2021, at 8:33 AM, Stephen J. Turnbull <stephenjturnbull(a)gmail.com> wrote: > > Hi, Eugenio, > > I wrote this earlier but am in the middle of moving my office so my > mail has been intermittent. I have been following your discussion > with Abhilash, and he's definitely the expert, especially if you are > using the containers he creates and distributes. But there's some > information here he hasn't mentioned yet. > > Please consider the following discussion to be background that allows > you to understand some of the considerations. I've only run the > Mailman 3 suite with all three running constantly on the same host, so > I have no experience with this kind of issue. > > eugenio.jordan(a)esa.int writes: > >> Our customer is currently using PostGRESQL as backend, and we would >> like to perform some maintenance tasks, namely running vacuum full, >> or at least trying to rebuild hyperkitty_email primary key related >> index. We have been asked on the real impact of putting in place >> such initiative. Though the latter is related to archiving, I >> haven't found a way to stop just Hyperkitty or Django related >> processes other than stopping Mailman's core, hence preventing >> mails addressed to distribution lists from being delivered, could >> you please confirm if I am correct? > > Mailman core can certainly run without either Postorius or HyperKitty. > Controlling Mailman core (moderation, helping users) without Postorius > is annoying, but it can be done. If you stop the HyperKitty process, > what should happen, I believe, is that posts for archiving will > accumulate in the 'archive' queue until HyperKitty is available again. > > It's been a while since I studied this so I could be completely wrong, > but as I understand it HyperKitty and Postorius are not daemon > processes. Rather, they are WSGI applications, which means they are > subprocesses spawned by your webserver, and controlled by it. In > order to keep them from running, you would reconfigure the webserver > to not call those WSGI applications. How that is done is specific to > the webserver and the WSGI module. If you are running from Docker > containers, most likely, you can just stop their containers. Yeah, Postorius and Hyperkitty themselves aren’t daemons, but they run inside WSGI servers like uwsgi/gunicorn which are typically separate daemons than webserver like Nginx which sits in the front. However there are common webserver modules like mod_wsgi (for apache2) which will let you run without managing a separate WSGI server. So, it depends on the setup, you can either just stop the WSGI server or stop the web server. For, containers, the WSGI server (uwsgi) runs in the container and you can just stop the mailman-web container. -- thanks, Abhilash Raj (maxking)

3 years, 9 months

Re: Patch/kludge suggestion and a question on adding accepted addresses

by Mark Sapiro

On 04/24/2017 07:07 AM, David Krantz wrote: > On Sun, Apr 23, 2017 at 11:04 PM, Barry Warsaw <barry(a)list.org> wrote: >> On Apr 23, 2017, at 10:33 PM, David Krantz wrote: > >>> I have another question: In the old mailman you could add accepted >>> senders without adding them to the list. Is that possible in Mailman >>> 3/Postorius? >> >> You do this by creating a "nonmember" subscription for the sender, and then >> setting that member's moderation_action to Action.accept. > > Okay. I see no way of doing that in my instance of Postorius but in > this case it is okay to do it in the command prompt. Yes. There are still quite a few things that aren't yet exposed in Postorius and probably some not yet exposed in the rest API. In these cases you have to resort to mailman shell (aka mailman withlist). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 1 month

Re: Core, Hyperkitty and Postorius releases

by Mark Sapiro

On 5/13/21 2:27 PM, Odhiambo Washington wrote: > On Wed, Feb 3, 2021 at 5:00 AM Abhilash Raj <maxking(a)asynchronous.in> wrote: > >> Hey Everyone, >> >> I am pleased to announce new stable releases for Mailman Core, Postorius, >> Hyperkitty. >> >> These include both new features and bug fixes. Complete change log for >> each components: >> >> Mailman Core 3.3.3: >> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… > > > May I ask if this is a typo? > I am asking because Mailman Core 3.3.4 was announced on Marc 22nd. > So is this new one version 3.3.3 or 3.3.5? The text you are quoting is from the Feb 2 announcement <https://mail.python.org/archives/list/mailman-announce@python.org/message/N…> of the release of Mailman core 3.3.3. Mailman 3.3.4 was released and announced at https://mail.python.org/archives/list/mailman-announce@python.org/message/H… on March 21 and is the current release. There is no "new one". -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

Mailman-users search results for query "Postorius"