Search results for "Postorius" - Mailman-users

Re: Mailman, etc. upgrade woes and persistent bugs

by Allan Hansen

They need to resubscribe to each list they want the new address to be used for. Subscriptions involves permissions from the moderators. It’s not a simple process, especially if you are on many lists. Yours, Allan Hansen hansen(a)rc.org > On Feb 12, 2021, at 8:47 , Andreas Barth <aba(a)ayous.org> wrote: > > * Stephen J. Turnbull (turnbull.stephen.fw(a)u.tsukuba.ac.jp) [210212 12:04]: >> hansen(a)rc.org writes: >>> b. The ability of members to change their addresses for all lists >>> they are subscribed to. >> >> What exactly do you want here? I can think of a number of ways to >> implement that, depending on whether the old address is to be >> deactivated from the lists, unsubscribed from the lists, or deleted >> from the Mailman and/or Postorius Users. There may be other >> variables to consider, as well; I haven't thought about this. AFAICS >> this is not a trivial feature, and I'd really like to hear from people >> who want "something like" this about exactly what they want and their >> use cases. Or we'll release an insufficiently designed feature that >> causes somebody hundreds of problems.... > > I thought user could do that if they have an web account, and multiple > mail addresses are associated with the account? Or does my memory > serve me wrong there? > > > Andi > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years, 8 months

Re: Mailman 'requests' API call timeout when there are a number of pending members

by Abhilash Raj

On Thu, Jan 14, 2021, at 6:52 PM, Alan So wrote: > We are currently testing latest mailman suite and notice that the > requests API call will timeout if there are a number of pending > requests. > > Since the latest Postorious allow unchecking Pre confirm and Pre > approved during mass subscribe, our support staff tried to add large > number of email addresses to the list. We then found that we cannot > click into the list from the web UI to administer it and an error > message showing that "Mailman REST API not available. Please start > Mailman core." Further checked that the requests API call failed to > complete when we click the list on the web interface. > > Looks like the UI should not try to load all the pending members just > for the sake of showing the number of pending requests. Of course in > normal situations, there should not be that many pending requests. This issue has been partially mitigated by [1] making the list's index page better. Also, subscriptions pending confirmation from User don't affect the speed of the page showing subscriptions pending user confirmation. However, there is more to be done by adding support for pagination, which is reported here [2]. [1]: https://gitlab.com/mailman/postorius/-/merge_requests/559 [2]: https://gitlab.com/mailman/postorius/-/issues/420 > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

5 years, 9 months

Re: New domain cannot set set host

by Mark Sapiro

On 11/28/24 10:19 AM, Alain D D Williams wrote: > On Wed, Nov 27, 2024 at 12:42:41PM -0800, Mark Sapiro wrote: >> On 11/27/24 12:18 PM, Alain D D Williams wrote: >>> >>> But it is not in table mailman3web.django_site >>> >>> Please how do I do this ? >> >> Add the domain as a site in the Django web admin UI. > > I did not see this y/day and created the entry in table django_site using SQL. > This might be the cause of the other problems that we have been talking about. It's not likely that this is the cause. > I must admit to finding django daunting -- something that I know nothing about; > I ran "mailman-web --help" and was non the wiser. > > I found the following which did not help either: > > https://docs.mailman3.org/en/latest/django-primer.html Yes, Django can be daunting. It is certainly possible to implement alternatives to Postorius and HyperKitty that use some lighter weight, non-Django framework, and it was always our hope that someone would do this and contribute it. A few years ago, EMWD did implement alternatives using PHP, but at least in part due to the untimely death of EMWD's principal, those remain proprietary. That said, if you follow the installation doc at https://docs.mailman3.org/en/latest/install/virtualenv.html you shouldn't need much Django knowledge beyond that and https://docs.mailman3.org/en/latest/django-primer.html -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 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, 10 months

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, 10 months

Re: Python 3.13 compatibility

by Washington Odhiambo

On Sun, Mar 29, 2026 at 6:11 PM Thomas Krichel <krichel(a)openlib.org> wrote: > Mark Sapiro writes > > > If you do that and it results in a working system, you can then patch > > mailman/utilities/i18n.py as follows > > Thank you. This works, and I can successfully import a first > list configuration. > > > However there are other incompatibilities between the released Mailman > > versions and Python 3.13. > > Hmm https://docs.mailman3.org/en/latest/install/virtualenv.html > states "3.13 is recommended as it is the latest version of Python > with which Mailman is tested." > > > At the moment, until updated packages are > > released, in a Python 3.13 environment it is best to install all of > mailman, > > django-mailman3, postorius, hyperkitty and mailman-web from the heads of > the > > gitlab branches. > > I would love to see a command line for that. When I go to the gitlab > page, https://gitlab.com/mailman/, I see a bunch of project that > don't immediately correspond to pip package names. > pip install git+https://gitlab.com/mailman/mailman@master pip install git+https://gitlab.com/mailman/mailmanclient@master pip install git+https://gitlab.com/mailman/mailman-hyperkitty@master pip install git+https://gitlab.com/mailman/hyperkitty@master pip install git+https://gitlab.com/mailman/django-mailman3@master pip install git+https://gitlab.com/mailman/postorius@master pip install git+https://gitlab.com/mailman/mailman-web@master -- 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]

7 months, 1 week

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, 8 months

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

7 years, 6 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, 10 months

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, 9 months

Mailman-users search results for query "Postorius"