Search results for "Postorius" - Mailman-users

Re: [Mailman-Developers] Rolling releases for Container Images and Funding Campaign for Mailman

by Abhilash Raj

On Wed, Nov 8, 2017, at 04:38 AM, Simon Hanna wrote: > On 11/08/2017 12:03 AM, Abhilash Raj wrote: > > New images are available on quay.io and, moving forward, the rest of > > the image builds will also be moved to Quay[4][5]. > Since docker deployment is currently the recommended install, with > manual installs using the master branches for "experts" I wonder why you > are using Quay. For those who don't know about it, Quay is a container registry offering from CoreOS. The main reason why I chose to move to Quay, from DockerHub that we are currently using, is security. Some parts of both Dockerhub and Quay are open source and some aren't. There isn't a very clear boundary/transparency in what technologies they use. Both are free to use for open source projects. However, Quay provides an improved security model with RBAC to push images from build server, without having to put my account password on the build server. It also includes a (open source) security scanner for images, which looks for vulnerabilities in packages included in the image so that I can re-build them if one is found. There are open source registries available, most popular of which I know is provided by Gitlab. However, I feel Quay is better for my current workflow, which involves lots of bash scripts for building and testing images on public CI system for rolling releases. Given more free cycles, I do intend to have a better build pipeline and possibly use Gitlab's own registry to distribute images. > It looks like it's a non-free system. Why use Quay but refuse to use a > non-free translation system like transifex? > > These images are built using git-heads *only* if they are passing our > > test suite and are re-generated weekly. You should be aware that while > > all these components are tested with their individual test suites, their > > combination might sometimes not be stable. This will get you > > updates/bug-fixes much faster :) > This contradicts what you said in my merge request for Postorius > https://gitlab.com/mailman/postorius/merge_requests/232#note_43388756 > > You either use released versions, or make sure that the master branches > are always compatible. You can't have both with the current development > model. Not exactly, I still believe all our git-heads should be compatible with released (i.e. stable) versions of dependencies, regardless of the fact that we maintain those dependencies. Also, there is at least one test per-project which tests with git-heads of dependencies we maintain, so that we know if we make any incompatible changes. I am not sure what in the current development model prevents us to do both? The story for container images is different than testing with git-heads. We need better integration testing for the entire suite to be stable in conjunction, rather than independently. In fact, containers might be the perfect way to actually do the integration testing. > > If this campaign succeeds, here is a road map of what I intend to get > > done: > Sounds great, what is the limit where the campaign succeeds? What will > happen to the funds if it doesn't? > > - Add Admin Dashboard project from GSoC 2014 (maybe?) > Didn't find anything using google. What is that project about? https://www.google-melange.com/archive/gsoc/2015/orgs/gnu_mailman/projects/… > > - Add better testing of container images and provide deployment > > instructions for Kubernetes & Docker Swarm > To be honest, I don't think we should all in on containers. > Yes they are nice, but I guess most people would prefer distro packages. > Even if people want containers, I for instance would prefer plain > systemd-nspawn Like Barry mentioned, it doesn't have to be all-or-nothing. There is work being done on distro packaging for Debian and I am ready to help others trying to do the same for other distros! Systemd-nspawn isn't really a production grade tool to use containers. I am not sure about how much it adheres to the OCI specs, but if it does, it should not matter which deployment tool you are using with images. I wouldn't mind adding configurations for systemd-nspawn in the documentation, contributions are most welcome. > > - Improve the container images to work with new micro-services > > architecture, > > to achieve scaling and redundancy in services. > The current bottleneck is the rest api from core. IMO bulk actions, > filtering and sorting should be added there before trying to have > multiple postorius/hyperkitty instances serving the same core... I didn't say they will be served from the same core ;-) Yes, the Core's API can be further improved to be more efficient. But that doesn't prevent us from scaling. I understand there are issues around multiple instances of containers, but I have ideas to get around most of them. -- Abhilash Raj maxking(a)asynchronous.in

8 years, 3 months

Re: Can "Pre Verified" set to yes by default?

by Alan So

Stephen J. Turnbull wrote: > Hi Alan, > It occurred to me that Django template widgets are very flexible. It > may be possible to customize the template to accomplish this task. In > that case, the customized template would be kept in a place that > doesn't get overwritten in an upgrade, reducing the maintenance cost > (unless either Postorius or Django changes the template in a way that > seems unlikely to me). I'll try to take a look at that over the > holiday break -- that has the advantage that I just document how we > did it for you, and tell any future requests to RTFM and DIY. ;-) Many thanks for your effort especially during the long holiday. Really appreciate. > I agree, you need to be disciplined about what changes you are willing > to develop and maintain. This one seemed to me to be over that bar, > especially since you can put it in and not suffer too greatly if it > gets reverted in a upgrade and the maintainers don't notice. We do not always have full control of what we are willing to do. It is kind of a Pandora's box. Opening it up may lead to other requests which may no longer be patches but changes potentially conflicting with future upgrade. It is ok if people here recognize that we should have our own developers to participate in this kind of changes and also the maintenance but it is not the culture here. Particularly developers here are much more experienced in Win, C#, .NET than Linux, Python.

3 years, 1 month

Can "Pre Verified" set to yes by default?

by Alan So

We are a university with many departments & colleges owning their own mailing lists and they manage their members lists by themselves. The current (ours is 1.3.6) Postorius have a default of "Pre Verified" as "No" when doing mass subscription by the list admin. It sounds sensible if most people subscribe to the lists by themselves normally. But in our case, our departmental staff normally maintain their list of members and do not want their members need to do anything before they can be reachable from lists. However, some of our departmental staff sometimes forget to check the box "Pre Verified" when they refresh (actually delete all and subscribe all) list of members during term's start. This often lead to issue especially if the list they maintained have thousands of members. Our normal way to help them is to remove the list and create the list again so that the departmental staff do not need to discard the pending members one by one. This is already the best scenario if they know that it is the root cause. Since subscribing thousands of members normally will not have the normal UI page coming back (due to timeout), they often do not know that it is the cause of issue. If they repeat the steps to subscribe the members again, they will just not be able to get the job done but also make the system busier and they never know that it's already in the pending list. Is this possible to add default setting of Pre Verified during mass-subscription (for example settings.py) such that we can help them a bit? Thanks.

3 years, 1 month

Re: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by gordon＠dickens.com

Hello Mark and everyone else, I made significant progress in that I got the web interface working. The file permissions were wrong for the /var/log/mailman3/web directory in that the web directory needs to be writable by www-data (the apache user), Also, the aliases in the Apache configuration needed to be changed to the following: Alias /favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico Alias /static/ /var/lib/mailman3/web/static/ Once I fixed these issues then I was able to successfully access the web interface and login. Now, I am able to access the web interface and I am able to navigate to all of the main links on the top of the main page including: Postorius. Lists, Domains, Bans, System Information, Users and Archives. My only remaining problem is that I cannot access the individual mailing lists. That is, when I navigate a list and click on the list name then my browser displays: "Server error An error occurred while processing your request." Concurrent with the above browser display, mailman3 sends an email to the system admin with the subject: "[Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/lists/list_local_name.domain.tld" This email and my logs now complain about: "Internal Server Error: /mailman3/lists/list_local_name.domain.tld/ MultipleObjectsReturned at /mailman3/lists/list_local_name.domain.tld/ get() returned more than one EmailAddress -- it returned 3!" Also, I get the same errors after I create a new mailing list as well. I hope that Mark and/or somebody here can offer up suggestions on what I need to do to fix this. Any suggestions would be very much appreciated! Thanks, Gordon

4 years

Archive Policy not reflecting in Hyperkitty

by Nathan Dixon

So the issue I am seeing is that when I set a lists archive policy to prviate, it isn't reflecting that in Hyperkitty. I am running the docker installation of Mailman, postorius and hyperkitty. So I go into the docker instance of mailman-core and run this: python3 manage.py shell from hyperkitty.models.mailinglist import MailingList MailingList.objects.all().values_list('name', 'archive_policy') And all my lists are showing '2', regardless of how I set the mailing list archive policy. This might be a duplicate of https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… Am I missing something in my install? Or is this a bug? Many thanks for your attention, -- *Nathan Dixon* MEng Senior Software Architect m: +44 (0)7402 690311 t: +44 (0)20 81231252 e: nathan.dixon(a)evadon.com w: www.evadon.com This e-mail and any attachments are confidential and may be protected by legal, professional or other privilege. If you are not the intended recipient you should not store it, copy it, re-transmit it, use it or disclose its contents, but should return it to the sender immediately and delete your copy from your system. The views expressed are those of the sender and not necessarily those of Evadon. Please note that whilst we scan all e-mails for viruses we cannot guarantee that any e-mail is virus-free. Please be advised that we expressly reserve the right to monitor email content for the purposes of ensuring compliance with legal requirements and company policies and your sending to, or receiving from, us of any email constitutes your agreement to these terms. Evadon Dynamics Limited, registered in England No. 09494097. Registered Office: Electric Works, Sheffield Digital Campus, 3 Concourse Way, Sheffield, S1 2BJ

6 years, 9 months

Re: List creation error

by Odhiambo Washington

On Wed, 6 Jan 2021 at 15:36, Andreas Barth <aba(a)ayous.org> wrote: > * Odhiambo Washington (odhiambo(a)gmail.com) [210106 12:12]: > > PS: I could probably have caused the error with some weird operation I > did: > > Initially when postorius comes up, it has the domain - *example.com > > <http://example.com>*. I am not sure where it gets this. > > example.com is the default domain from django. Renaming that via the > django (e.g. mailman3/admin/sites/site/1/change/ ) worked for me quite > well (without touching anything in the database by hand). > Hi Andi, I could be missing something still... 1. At what juncture during the installation do you do this renaming? 2. Where is this directory? On my setup, I have no such directory - but I could be missing something in the install process, maybe.. root@debian10:/opt/mailman# pwd /opt/mailmanroot@debian10:/opt/mailman# *find . -type d -name sites* ./mm/venv/lib/python3.7/site-packages/jedi/third_party/django-stubs/django-stubs/contrib/sites ./mm/venv/lib/python3.7/site-packages/django/contrib/sites Do you find anything amiss with this HOWTO - https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 ?? I find the guide rather straight and clear. It's the one I am following - almost to the letter - except for the fact that I am using Apache+mod_wsgi+MySQL+Exim instead. I have configs in place by the time I run 'mailman info' portion. But then again, when I run this command, I don't like what it prints because I see some reference to sqlite. As it is, I believe my problem lies elsewhere, not possible to solve with your rename option. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

5 years, 1 month

Re: changing the main template for subscriptions and more

by Mark Sapiro

On 2/1/22 12:40, Paul Paulchen wrote: > Hi Mark, > > thanks for your advice. Unfortunately we need some more clues. > First of all, we are using mailman docker by maxking - https://github.com/maxking/docker-mailman I do not know what the file layout is in the Docker container, so I can't verify paths. > Our version: > Mailman Core Version - GNU Mailman 3.3.5 (Tom Sawyer) > Mailman Core API Version 3.1 > Mailman Core Python Version 3.8.10 (default, May 6 2021, 06:30:44) [GCC 9.3.0] > > We put an example footer.txt into the templates folder as you mentioned: > mailman3_core => var/templates/sites/de/list:member:regular:footer.txt > Mailman user can read them As I said, I can't give you an absolute path. If you can run `mailman info` in the container, that will show the location of mailman.cfg which may help Installing the template as you have should work if it's the correct path. > Created a new list, restarted the docker-container, but it always showed the default footer.txt and not our example footer.txt from the templates folder. Any guesses or clues? Where is this default footer.txt hiding anyway? Changing languages in postorius works fine and it alters between english, german etc... just won't use our custom footer.txt The default templates are in the mailman/templates/ directory where the mailman/ directory is where all the Mailman core software is. Hopefully someone familiar with Docker and the Mailman Docker container can provide better information. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

Problems configuring hyperkitty

by Alain D D Williams

I am having another go at installing mailman3 - I seem to have mailman3 & postorius working - although basic testing, much more needed to confirm that I understand it. I want to get hyperkitty working before I start full testing. I am running Debian 12 - Bookworm and have installed the Debian packages. The database is Mysql. This is not a virtualenv setup. There is no documentation in the hyperkitty package so I am following: https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html I read the following: "The database can be created with the following command: django-admin migrate --pythonpath example_project --settings settings " I assume that that will create some database tables. Hopefully this will have been done by installing package python3-mailman-hyperkitty. • What database & tables will that be ? It would be really useful to be told so that I can check. • The config file is: /etc/mailman3/mailman-hyperkitty.cfg This does not contain any comment about databases. Where does hyperkitty get its database parameters from ? • I have several different maildomains each with several lists. Some lists in different domains have the same name. Do I need a different example_project/settings.py for each domain, if so what changes ? One of the next things that I will need to do is to import archives from mailman2. How does the command below change for the different domains ? django-admin hyperkitty_import --pythonpath example_project --settings settings -l ADDRESS mbox_file [mbox_file ...] Is there some better documentation that I have failed to find ? Regards -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

1 year, 3 months

Re: Mailman 3 localization

by Alexander Klotz

> I wanted to set it up, but the requirement is to use a free hosted > solution. (So transifex and crowdin are a no-go, they would be great to > get translations, especially crowdin looks very active in that regard) > I tried out zanata.org but it's extremely slow... > The other option at the time was pootle > (http://pootle.translatehouse.org) which doesn't offer hosting but some > folks at gnu had a customized instance set up, but they discontinued the > service. > > I searched for a translation service for a private project and found > weblate.org . They offer hosting (hosted.weblate.org) for open source > projects and it looks like a couple of people are using it. You need to > contact them if you want to set it up for an open-source project though > and I didn't want to invest in it without knowing what the end-result > would be... > > Since I'm also mainly interested in German translations for my own > installation, I opted to just use plain .po files and filed merge > requests against the repositories. Postorius has translations (not > perfect, but a start for the moderators that use my instance) included > by now but my merge request for core is still outstanding > https://gitlab.com/mailman/mailman/merge_requests/400/ > Since I don't use Hyperkitty, I didn't translate that. > Thanks for the reply, Simon! We were thinking of using plain .po-files too, however, we couldn't find the matching "src" folder in our installation, do you have any more details where it or the .po-files may also be located? Regards, Alex

7 years, 7 months

Proper permissions for mailman installation under home directory, with layout: local

by Eric Abrahamsen

I recently upgraded my server from Ubuntu 16.04 to 18.04, and have hit some snags in the process. I've had my mailman3 installation under my home directory, running as my own user, without too many problems. var_dir was set to something in my home directory. Recently, while tracking down some weird behavior, I realized that with this sort of setup I'm supposed to use "layout: local", and that previously I'd had a sort of weird half-way installation where some things were kept in my /home/<me>/sites/mailman directory, and other bits (pids and whatnot) were scattered around the filesystem. Now that I'm using "layout: local", mailman really is trying to keep everything under that main directory, and now everything's breaking. The hyperkitty search indexer is saying it has no permissions to write into that directory, postfix won't deliver mail, saying the mailbox is unavailable, and in the web UI postorius shows no configured list domains (though hyperkitty still displays the archives correctly). So obviously I've got quite a big problem with permissions, but I don't know how to resolve it. My webserver is nginx, running as www-data. I'm starting mailman in a systemd script, with User and Group set to my user -- though maybe that should be set to root? I guess postfix runs as root, I'm not sure, but obviously it's not able to read the files in var/data/*, which appear all correct to me. What's the recommended solution here? I'd still like to keep this whole directory under my home directory, if possible... Thanks, Eric

7 years, 4 months

Mailman-users search results for query "Postorius"