Search results for "Postorius" - Mailman-users

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

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

3 years, 9 months

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

4 years, 6 months

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

7 years, 7 months

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

3 years, 6 months

Re: Splitting hosts: mta&core vs postorius

by Stephen J. Turnbull

Ruth Ivimey-Cook writes: > On 6/22/20 6:23 PM, Stephen J. Turnbull wrote: > > By design, Mailman core doesn't need to talk to the Internet or to the > > secure internal network -- Internet functions are delegated to the MTA > > and the webapps, and local configuration is via shell access which in > > principle could be console. > > Sorry, I missed this earlier. I was more or less trying to describe what I thought you were trying to do, and noting that Mailman is designed for it. Thank you for the confirmation. > I am using exim and there is a big benefit when exim can see the > list directory names. Indeed. (I wrote the proof of concept Exim config for Mailman 3 on Debian.) But that's *all* it needs to see. It should be possible to get that information to Exim in some other way, perhaps through a small app that talks to the REST API. If that's generalizable to other MTAs (especially Postfix, but also Sendmail and maybe qmail) it's worth us looking into (and if it's Exim-specific, at this stage I'd say "patches welcome"). This is also the kind of thing that an NFS read-only mount does fine (of course you may not want NFS on a system in the DMZ :-/ ). > However, I find the mailman shell program not very intuitive, and so > would prefer to have the web app for admin purposes. By "local configuration" I mean anything that requires access to the .cfg files or installing code. Anything you can do via Postorius (or soon, via Affinity, hi Brian!) is not local configuration in this sense.

4 years, 5 months

Re: template head/footer questions.

by Mark Sapiro

On 4/8/22 11:04, bob B via Mailman-users wrote: > I migrated from mailman 2 to mailman3 and had head/footer questions. > > In the mailman 3 GUI see the templates section, so where do those files get edited/stored? in the postorius_emailtemplate table in the database. > I added a footer to a list via the GUI, but I do not see it in: > /var/templates/lists/[listNAME]/en Because when you set a template in Postorius it makes an entry in the template table in the database with a URI pointing to its own API to retrieve the template. > I see some directories corresponding to list names in /var/templates/lists/ But I do not have a directory for all my lists and for the footer one I just added. > > Bottom line, > > I assume I should not edit or create any files in /var/templates/lists/ and just use the GUI? That's up to you. The default search path for templates in the absence of a template table entry (or even with one with a mailman:/// URI) includes the var/templates/lists/list_id directory. is this directory leftover from migrating from mailman 2 to 3? No I have a list admin who has made some head and footer files and wants me to put them in /var/templates/lists/[listNAME]/en/.... but I think that may not be the best option. Again, it's up to you. If you have Postorius and want list admins to be able to create, modify, break, etc. templates without involving you, then Postorius is a good option, but it isn't in all cases. -- 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: customized welcome message

by Nils

Forget the previous message. Thank you very much for your help, Mark. I looked at the configuration files once more, and changing POSTORIUS_TEMPLATE_BASE_URL in mailman-web.py fixed the issue for me. Kind regards On 12/7/23 23:09, Nils wrote: > On 12/7/23 22:40, Mark Sapiro wrote: >> How and to what did you set the URL for the template? What does the >> database query >> >> SELECT uri FROM template WHERE name = 'list:user:notice:welcome'; >> >> show? > http://localhost/postorius/api/templates/list/testliste.lists.DOMAIN.TLD > > This value can't work. Now it makes sense that it gets redirected and > the use of localhost also explains why it didn't show in any of the > virtual hosts log files that I was checking until it was redirected. > > However, I didn't set that value. I edited the template at > postorius/lists/testliste.lists.DOMAIN.TLD/templates and there I can > just select a template type and then I get one textarea input field > for the content. > The value in the database is set automatically, when I create a > template in postorius (and is also automatically removed when I delete > a template there). I can't edit this value without manually changing > it in the database. > >> This is very old. Current Postorius is 1.3.10. 1.2.4 is from February >> 2019. The Debian/Ubuntu packages are out of date. We recommend >> installing via the doc at >> https://docs.mailman3.org/en/latest/install/virtualenv.html > > The server will be updated from Ubuntu 20.04 (focal) to 22.04 (jammy) > very soon. The Debian/Ubuntu packages sure have their downsides but > once they work, they update automatically and require very little > maintenance.

11 months, 2 weeks

Re: mm3 installation question

by Odhiambo Washington

On Wed, Mar 6, 2024 at 3:13 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/5/24 1:52 PM, advorkin(a)cs.princeton.edu wrote: > > > > I went with the apache/uswgi configuration. The site is up and running, > but if I click Postorius, it gets redirected to > https://mysite.com/postorius/lists and I get not found error message. > > > > The same goes for Lists and Archives. > > Compare your urls.py to > < > https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/urls.py?re…>. > > Some of the `path` settings are probably not in the same order as in > that file. The > > ``` > path('mailman3/', include('postorius.urls')), > path('archives/', include('hyperkitty.urls')), > ``` > settings should come after the > ``` > path('postorius/', include('postorius.urls')), > path('hyperkitty/', include('hyperkitty.urls')), > ``` > settings (unfortunately, mailman-web 0.0.8 has these in the wrong > order). Or you can just delete the 'postorius/' and 'hyperkitty/' ones > or you can add > ``` > ProxyPass "/postorius" "http://127.0.0.1:8000/postorius" > ProxyPass "/hyperkitty" "http://127.0.0.1:8000/hyperkitty" > ``` > to your Apache config. > The odd thing is that the HOWTO that he followed never involves the manipulation of any urls.py at all - it's not even mentioned at any point. So obviously the issue is caused by something else and I suspect something within Apache needs to be re-evaluated in the guide. -- 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]

8 months, 2 weeks

Mailman-users search results for query "Postorius"