- Mailman-users - lists.mailman3.org

(no subject)
by Lars Bjørndal June 14, 2020

June 14, 2020

I'm about to set up a new list, and want to try out Mailman3. The only component available in Fedora, is the Mailman core package. With the /usr/libexec/mailman3/mailman command, I was able to create a list, and add a member throug the sub commands create and members. How can I read out the list configuration from here, and change settings? Do I then need to install/use other components, or is there other possibilities, e.g. using the shell command? If I get a message that needs moderation, can I do the decision from cli, or how do I do that? Thanks Lars

2 2

Mailman3 on Fedora
by Lars Bjørndal June 14, 2020

June 14, 2020

Hi, list! I'm running Fedora 31. The only Mailman 3 package in the Fedora repo seems to be mailman3-3.2.0-2.fc30.noarch, which is only Mailman core. My goal was to start using Mailman 3 for a new list. It seems without the other packages, it's not trivial to configure the list, please correct me if I'm wrong. And of course I don't get the archive functionality which I don't need anyway. Does anyone know whats the plan for Fedora when it comes to implementing the other components of Mailman 3, and when they will ship a newer version of the core package? Thanks, Lars

3 3

max_message_size parameter not working in mailman 3.3.1
by Shashikanth Komandoor June 13, 2020

June 13, 2020

Team, I am currently working on Mailman 3.3.1 in production environment. Today I faced an issue related to the mail size limit. One of our users has sent a mail with nearly 27M to one of the lists running on Mailman 3.3.1. Though I have configured the parameter related to the Maximum message size as '0' which I meant as no limit to the size of mail, I observed the mail is not accepted and rejected with the message "Message size limit exceeds". So, could anyone please help in resolving the issue or at least a work around asap ? -- Thanks & Regards, Shashi Kanth.K 9052671936 <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

2 1

manage.py runjobs hourly
by Mark Dadgar June 11, 2020

June 11, 2020

I have started getting this emailed to root each hour from the cron job. > From: root(a)pdc-racing.net (Cron Daemon) > Subject: Cron <www-data@mail> [ -f /usr/bin/django-admin ] && flock -n /var/run/mailman3-web/cron.hourly /usr/share/mailman3-web/manage.py runjobs hourly > Date: June 11, 2020 at 11:00:06 AM PDT > To: www-data(a)pdc-racing.net > > 18:00:03 [Q] INFO Enqueued 1350 > 18:00:03 [Q] INFO Enqueued 1351 The Enqueued numbers do increment. Anyone know what this is? - Mark ----- mark(a)pdc-racing.net | 408-348-2878

2 2

Weird hourly indexing error
by Mark Dadgar June 11, 2020

June 11, 2020

I moved my mail server to a Digital Ocean droplet. I basically installed all the appropriate packages and then rsync’d everything that matters from my metal server up to the cloud instance. Everything more or less works fine. However, I am now getting this hourly error - see below. It is ENTIRELY possible that I was getting this error on the previous server as well, but I didn’t have www-data aliased to root so I would never have seen it. Anyone know what’s going on here? BTW, Digital Ocean is pretty awesome. If anyone wants to try it, ping me for a referral code good for $100 in credit to play with. - Mark ----- mark(a)pdc-racing.net | 408-348-2878 Begin forwarded message: From: root(a)pdc-racing.net (Cron Daemon) Subject: Cron <www-data@mail> [ -f /usr/bin/django-admin ] && flock -n /var/run/mailman3-web/cron.hourly /usr/share/mailman3-web/manage.py runjobs hourly Date: May 5, 2020 at 5:01:00 AM PDT To: www-data(a)pdc-racing.net [ERROR/MainProcess] Failed indexing 1 - 1000 (retry 5/5): Term too long (> 245): XSUBJECT95251413 (pid 36301): Term too long (> 245): XSUBJECT95251413 Traceback (most recent call last): File "/usr/lib/python3/dist-packages/haystack/management/commands/update_index.py", line 97, in do_update backend.update(index, current_qs, commit=commit) File "/usr/local/lib/python3.8/dist-packages/xapian_backend.py", line 488, in update database.replace_document(document_id, document) xapian.InvalidArgumentError: Term too long (> 245): XSUBJECT95251413

3 24

Postorius endless loading on Sign in / Register then "Internal Server Error"
by Jacob Bargery June 10, 2020

June 10, 2020

Pre-cursor, I am in a new position to learn on the go and new to Linux but have been tasked with setting up a List Serv and they wanted Mailman 3 with Postorius and HyperKitty. Running on Ubuntu 20.04 LTS using Postfix and MySQL. I can open up the initial pages. With no Lists created yet. I can open up Register, Login, and Forgot Password but when I submit anything it spins the loading icon for a long time then reads" "Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Apache/2.4.41 (Ubuntu) Server at groups.smccme.edu Port 80" If I try to re-navigate to the page, nothing loads. If I reboot the server, I can get to the same point again with the same problem. Performed a log tail on mailman-web.log and got this and then nothing happens after this no matter how long I wait: 15:18:31 [Q] INFO Q Cluster-1686 starting. 15:18:31 [Q] INFO Process-1:1 ready for work at 1932 15:18:31 [Q] INFO Process-1:3 monitoring at 1934 15:18:31 [Q] INFO Process-1 guarding cluster at 1931 15:18:31 [Q] INFO Q Cluster-1686 running. 15:18:31 [Q] INFO Process-1:2 ready for work at 1933 15:18:31 [Q] INFO Process-1:4 pushing tasks at 1935 [pid: 1683|app: 0|req: 1/1] 10.212.134.135 () {56 vars in 1124 bytes} [Tue Jun 9 15:20:48 2020] GET /mailman3 => generated 0 bytes in 545 msecs (HTTP/1.1 301) 6 headers in 213 bytes (1 switches on core 0) [pid: 1683|app: 0|req: 2/2] 10.212.134.135 () {56 vars in 1174 bytes} [Tue Jun 9 15:20:49 2020] GET /mailman3/postorius/lists/ => generated 3927 bytes in 378 msecs (HTTP/1.1 200) 5 headers in 163 bytes (1 switches on core 1) [pid: 1683|app: 0|req: 3/3] 10.212.134.135 () {58 vars in 1240 bytes} [Tue Jun 9 15:21:02 2020] GET /mailman3/postorius/lists/ => generated 3927 bytes in 63 msecs (HTTP/1.1 200) 5 headers in 163 bytes (1 switches on core 0) [pid: 1683|app: 0|req: 4/4] 10.212.134.135 () {58 vars in 1225 bytes} [Tue Jun 9 15:21:05 2020] GET /mailman3/hyperkitty/ => generated 11265 bytes in 120 msecs (HTTP/1.1 200) 5 headers in 164 bytes (2 switches on core 1) [pid: 1683|app: 0|req: 5/5] 10.212.134.135 () {58 vars in 1235 bytes} [Tue Jun 9 15:21:10 2020] GET /mailman3/postorius/lists/ => generated 3927 bytes in 77 msecs (HTTP/1.1 200) 5 headers in 163 bytes (2 switches on core 0) [pid: 1683|app: 0|req: 6/6] 10.212.134.135 () {58 vars in 1303 bytes} [Tue Jun 9 15:21:14 2020] GET /mailman3/accounts/signup/?next=/mailman3/postorius/lists/ => generated 8958 bytes in 74 msecs (HTTP/1.1 200) 6 headers in 331 bytes (2 switches on core 1) [pid: 1683|app: 0|req: 7/7] 10.212.134.135 () {68 vars in 1502 bytes} [Tue Jun 9 15:21:54 2020] POST /mailman3/accounts/signup/ => generated 9132 bytes in 96 msecs (HTTP/1.1 200) 6 headers in 331 bytes (1 switches on core 0) [pid: 1683|app: 0|req: 8/8] 10.212.134.135 () {60 vars in 1389 bytes} [Tue Jun 9 15:22:03 2020] GET /mailman3/accounts/login/?next=/mailman3/accounts/signup/ => generated 9128 bytes in 43 msecs (HTTP/1.1 200) 6 headers in 331 bytes (2 switches on core 1) [pid: 1683|app: 0|req: 9/9] 10.212.134.135 () {60 vars in 1384 bytes} [Tue Jun 9 15:22:04 2020] GET /mailman3/accounts/password/reset/ => generated 7749 bytes in 17 msecs (HTTP/1.1 200) 6 headers in 331 bytes (1 switches on core 0) This is a traceback I could find from another attempt: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/postorius/views/list.py", line 702, in list_index lists = paginate( File "/usr/lib/python3/dist-packages/django_mailman3/lib/paginator.py", line 71, in paginate objects = paginator.page(page_num) File "/usr/lib/python3/dist-packages/django_mailman3/lib/paginator.py", line 46, in page number = self.validate_number(number) File "/usr/lib/python3/dist-packages/django/core/paginator.py", line 48, in validate_number if number > self.num_pages: File "/usr/lib/python3/dist-packages/django/utils/functional.py", line 80, in __get__ res = instance.__dict__[self.name] = self.func(instance) File "/usr/lib/python3/dist-packages/django/core/paginator.py", line 97, in num_pages if self.count == 0 and not self.allow_empty_first_page: File "/usr/lib/python3/dist-packages/django/utils/functional.py", line 80, in __get__ res = instance.__dict__[self.name] = self.func(instance) File "/usr/lib/python3/dist-packages/django_mailman3/lib/paginator.py", line 56, in count return self.function(count=0, page=1).total_size File "/usr/lib/python3/dist-packages/postorius/views/list.py", line 699, in _get_list_page return client.get_list_page( File "/usr/lib/python3/dist-packages/mailmanclient/client.py", line 177, in get_list_page return Page(self._connection, url, MailingList, count, page) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/page.py", line 37, in __init__ self._create_page() File "/usr/lib/python3/dist-packages/mailmanclient/restbase/page.py", line 62, in _create_page response, content = self._connection.call(self._build_url()) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 109, in call raise MailmanConnectionError('Could not connect to Mailman API') mailmanclient.restbase.connection.MailmanConnectionError: Could not connect to Mailman API Any help would be greatly appreciated. Definitely in over my head on this one. Thanks.

2 3

Postorius with screen readers
by Andrew Hodgson June 10, 2020

June 10, 2020

Hi, Just wanting to let people know that since bumping to Postorius 1.3.3 I am seeing a real improvement in access to the Mailman settings and tabs using a screen reader with Chrome. When navigating through the tabs you are hearing two iterations of the tab, the first for example saying "Held Messages 0 tab" which is not a link, but then if you arrow down past that you hear "Held Messages 0" which is advertised as a link and if you hit enter on those it changes the page to the requested view. Thanks. Andrew.

3 3

New problem on new installation of Mailman
by Brian Carpenter June 9, 2020

June 9, 2020

I am just about done with installing Mailman 3 on a new Debian 10 server and when I go to run ./mailman-post-update, I am running into the following error: ./mailman-post-update + '[' False == False ']' + mkdir -p /opt/mailman/mm/static + /opt/mailman/mm/bin/django-admin collectstatic --clear --noinput --verbosity 0 Traceback (most recent call last): File "/opt/mailman/mm/venv/bin/django-admin", line 10, in <module> sys.exit(execute_from_command_line()) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/management/__init__.py", line 401, in execute_from_command_line utility.execute() File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/management/__init__.py", line 377, in execute django.setup() File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/__init__.py", line 24, in setup apps.populate(settings.INSTALLED_APPS) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/apps/registry.py", line 91, in populate app_config = AppConfig.create(entry) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/apps/config.py", line 90, in create module = import_module(entry) File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1006, in _gcd_import File "<frozen importlib._bootstrap>", line 983, in _find_and_load File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 677, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 728, in exec_module File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed File "/opt/mailman/mm/venv/lib/python3.7/site-packages/haystack/__init__.py", line 11, in <module> from haystack.utils import loading File "/opt/mailman/mm/venv/lib/python3.7/site-packages/haystack/utils/__init__.py", line 9, in <module> from django.utils import six ImportError: cannot import name 'six' from 'django.utils' (/opt/mailman/mm/venv/lib/python3.7/site-packages/django/utils/__init__.py) I assume it has something to do with Haystack. Suggestions for a fix? Thanks, Brian

2 2

Migrating from debian package to Virtualenv
by Ryan Morash June 9, 2020

June 9, 2020

We currently have our Mailman3 instance installed using the packages in Debian's repository. We want to migrate over to a virtualenv setup as described here: https://docs.mailman3.org/en/latest/install/virtualenv.html. Is there any thing we should be aware of for migrating data?

3 2

django-mailman3 1.3.4 bugfix release
by Abhilash Raj June 5, 2020

June 5, 2020

Hey everyone, There was a critical bug reported yesterday which would cause users to get 404 pages instead of their list options page. Upon investigation, it was found that the bug was related to bumping of Mailman Core's API version to 3.1 in django-mailman3 1.3.3 release. Because this bug can cause problems accessing several pages in web interface, we have a quick bugfix release for you. If you have already upgraded to 1.3.3 and don't wish to do another upgrade/restart, you have an option to run the command below to avoid the bug: $ python manage.py clear_cache -a This should invalidate the cache entries which cause the 404 bug. The new release is available through PyPI at: https://pypi.org/project/django-mailman3/1.3.4/ The changelog is available at: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst Finally, as usual, you can update to the new release using pip: $ pip install django-mailman3==1.3.4 -- thanks, Abhilash Raj (maxking)

1 0