- Mailman-users - lists.mailman3.org

Membership list changes
by Vako Nicolian Feb. 18, 2021

Feb. 18, 2021

Using MM 2.1.33 When I send an email to /{list}-request(a){domain.com} /with /who <password> /on the subject line, I get a list of the members of the list. Here are my questions: A) Is there a way to export the list to cvs or txt format? B) Can we format the list to have it come in name 1st and then email C) display number of members D) Sort the list Thank you, Vako

2 1

spanish localization
by Guillermo Hernandez (Oldno7) Feb. 18, 2021

Feb. 18, 2021

I contributed in january to translate to spanish all the items left in Mailman Core, Django-mailman, HyperKitty and Postorius via Weblate. I thought they will be used in the next upgrade, but I cannot see any improvement and there are many words untranslated. Is there any way to upgrade the .po files in order to get the last translation? P.S.: I will follow translating the Weblate updates, by the way.

5 44

Mailman, etc. upgrade woes and persistent bugs
by hansen＠rc.org Feb. 18, 2021

Feb. 18, 2021

I just had my Mailman suite upgraded. When it got started, I starting receiving messages that hundreds of subscribers to the lists had been disables, including several of the list moderators. This version started supporting bounce processing, but how in the world was this upgrade allowed to act on bounces that were being collected PRIOR to enabling bounce processing?? I got many angry emails, messages and phone calls asking what was going on, as they were bona fide list members. I was very surprised myself. I then looked at several of the disabled accounts, but the subscription info page in Postorius had no information about whether an account was enabled or disabled. Why is this not displayed???. The members can't see if their account is enabled. Is this another example of the disconnect between Mailman and Postorius? Further, even after the upgrade, the moderators still cannot access the list memberships even though all the lists are set to allow that. I would have asked the moderators to do this if this access bug had been fixed, but they can't get there. As a result of these bugs, after consulting with Brian, who helped with the upgrade, I spent many hours re-enabling the several hundred accounts that had been disabled. I had to go through each email notification to find the address of a disabled account, then find the list, then the member, in Postorius, and finally enable the account (at which time Postorius DID show the enabled status). Please, can the next upgrade include these very basic fixes/enhancements, which I requested a long time ago: a. The ability of moderators to see the list membership (a bug). b. The ability of members to change their addresses for all lists they are subscribed to. and further, now: c. That when members go to look at their subscription info, they can actually see the settings. Thank you, Allan

8 36

Mailman3 crashes on restart
by Gelpi Andrea Feb. 18, 2021

Feb. 18, 2021

After restarting my mail server mailman3 does not start any more. Mailman3 in on a debian 10. I upgraded the django packets but no result. This the syslog output. Feb 17 17:00:24 posta mailman3[21303]: Traceback (most recent call last): Feb 17 17:00:24 posta mailman3[21303]: File "/usr/bin/mailman", line 11, in <module> Feb 17 17:00:24 posta mailman3[21303]: load_entry_point('mailman==3.2.1', 'console_scripts', 'mailman')() Feb 17 17:00:24 posta mailman3[21303]: File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__ Feb 17 17:00:24 posta mailman3[21303]: return self.main(*args, **kwargs) Feb 17 17:00:24 posta mailman3[21303]: File "/usr/lib/python3/dist-packages/click/core.py", line 717, in main Feb 17 17:00:24 posta mailman3[21303]: rv = self.invoke(ctx) Feb 17 17:00:24 posta mailman3[21303]: File "/usr/lib/python3/dist-packages/mailman/bin/mailman.py", line 69, in invoke Feb 17 17:00:24 posta mailman3[21303]: return super().invoke(ctx) Feb 17 17:00:24 posta mailman3[21303]: File "/usr/lib/python3/dist-packages/click/core.py", line 1137, in invoke Feb 17 17:00:24 posta mailman3[21303]: return _process_result(sub_ctx.command.invoke(sub_ctx)) Feb 17 17:00:24 posta mailman3[21303]: File "/usr/lib/python3/dist-packages/click/core.py", line 956, in invoke Feb 17 17:00:24 posta mailman3[21303]: return ctx.invoke(self.callback, **ctx.params) Feb 17 17:00:24 posta mailman3[21303]: File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke Feb 17 17:00:24 posta mailman3[21303]: return callback(*args, **kwargs) Feb 17 17:00:24 posta mailman3[21303]: File "/usr/lib/python3/dist-packages/click/decorators.py", line 17, in new_func Feb 17 17:00:24 posta mailman3[21303]: return f(get_current_context(), *args, **kwargs) Feb 17 17:00:24 posta mailman3[21303]: File "/usr/lib/python3/dist-packages/mailman/commands/cli_control.py", line 81, in start Feb 17 17:00:24 posta mailman3[21303]: status, lock = master_state() Feb 17 17:00:24 posta mailman3[21303]: File "/usr/lib/python3/dist-packages/mailman/bin/master.py", line 104, in master_state Feb 17 17:00:24 posta mailman3[21303]: os.kill(pid, 0) Feb 17 17:00:24 posta mailman3[21303]: PermissionError: [Errno 1] Operation not permitted Feb 17 17:00:24 posta systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE Feb 17 17:00:24 posta systemd[1]: mailman3.service: Failed with result 'exit-code'. Any idea? What have I to check? Thanks -- Gelpi ing. Andrea ************************************************** I documenti vitali dimostreranno la loro vitalitˆ spostandosi spontaneamente da dove li avevate lasciati a dove non riuscirete a trovarli. **************************************************

4 5

Re: Mailman, etc. upgrade woes and persistent bugs
by Ruth Ivimey-Cook Feb. 18, 2021

Feb. 18, 2021

Steve, What I mean by per-user permissions is that some transitions, for example bounce-disabled to enabled, should be only possible by someone with appropriate permission to do so -- perhaps the list admin, perhaps someone else, but not just anyone. Another example _could_ be if a user disables themselves then only that user can re-enable them again (though I can see that might not be good). Of course, you can to some extent group users by role, so 'admin' role is always ok, 'list-owner' role is ok for any action on that list, etc. If you had a 'role' which was 'account-owner' then you can probably code the rule for re-enabling an account disabled by the account owner as "role = admin or role = list-owner or role = account-owner". Whether this needs to be extended to "role=admin or user = guy" (where 'guy' is a named account holder) I don't know... I suspect it would be better if that wasn't done unless it was shown to be necessary, as "here be dragons". Do you see where I'm at? In writing this up it occurs to me that being able to see/edit rules such as these, stored in per-list config, would probably be a good thing. Don't know how practical that is though. Regards, Ruth On 16/02/2021 15:29, Stephen J. Turnbull wrote: > Hi, Ruth, > > Thanks for the comments. I'll have to think about most of it, but I > have one immediate question. > > Ruth Ivimey-Cook writes: > > > > On 13/02/2021 16:34, Stephen J. Turnbull wrote: > > > > I don't think separate booleans is a good idea, since they're > > > basically mutually exclusive states[.] > > > > While using one variable makes some sense as you say, it does > > complicate the allowed state transitions especially when per-user > > permissions as well as logic are applied to the situation. > > I don't understand how "per-user permissions" apply here. > > Regards, > Steve -- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

4 4

Rebuilding a list index fails
by Mark Dadgar Feb. 18, 2021

Feb. 18, 2021

Now that I’ve got my instance back up and running on the latest released code, I am trying to rebuild a list index. I am using Xapian via haystack, which worked beautifully before my recent list meltdown. Error messages below. rebuild_index fails with the same error. This is with django version 3.0.12. I am sure I missed reinstalling something or there’s a version mismatch. Thoughts? - Mark ----- mark(a)pdc-racing.net | 408-348-2878 —— (venv) mailman@mail:/opt/mailman/mm/bin$ ./django-admin update_index_one_list xxxxxxs(a)pdc-racing.net Traceback (most recent call last): File "/opt/mailman/mm/venv/bin/django-admin", line 8, in <module> sys.exit(execute_from_command_line()) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 401, in execute_from_command_line utility.execute() File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 395, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/base.py", line 328, in run_from_argv self.execute(*args, **cmd_options) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/base.py", line 369, in execute output = self.handle(*args, **options) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/hyperkitty/management/commands/update_index_one_list.py", line 41, in handle update_index(listname=options.get("listname")[0], File "/opt/mailman/mm/venv/lib/python3.8/site-packages/hyperkitty/search_indexes.py", line 117, in update_index update_cmd.update_backend("hyperkitty", "default") File "/opt/mailman/mm/venv/lib/python3.8/site-packages/haystack/management/commands/update_index.py", line 280, in update_backend backend = haystack_connections[using].get_backend() File "/opt/mailman/mm/venv/lib/python3.8/site-packages/haystack/utils/loading.py", line 115, in __getitem__ self.thread_local.connections[key] = load_backend( File "/opt/mailman/mm/venv/lib/python3.8/site-packages/haystack/utils/loading.py", line 61, in load_backend return import_class(full_backend_path) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/haystack/utils/loading.py", line 23, in import_class module_itself = importlib.import_module(module_path) File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1014, in _gcd_import File "<frozen importlib._bootstrap>", line 991, in _find_and_load File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 671, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 783, in exec_module File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed File "/opt/mailman/mm/venv/lib/python3.8/site-packages/xapian_backend.py", line 10, in <module> from django.utils import six ImportError: cannot import name 'six' from 'django.utils' (/opt/mailman/mm/venv/lib/python3.8/site-packages/django/utils/__init__.py)

3 5

3rd Party Account is not working
by kwp.klein＠gmail.com Feb. 17, 2021

Feb. 17, 2021

I installed Mailman 3 with Postfix. I try to login with the 3rd Party Account. It is not possible, because I get this error message: Server error An error occurred while processing your request.

7 13

ham-confirm+3ee85b006eeb5897ca6f53b093cb063672f6a784@example.com
by Jörg Klein Feb. 17, 2021

Feb. 17, 2021

I want add some subscribers. When the I get this error message: I have no address ham-request(a)example.com. Do I need for every mailing list more as the mailing list email address? Final-Recipient: rfc822; ham-request(a)example.com Action: failed Status: 5.0.0 Remote-MTA: dns; mx0.example.com. (80.237.138.5, the server for the domain example.com.) Diagnostic-Code: smtp; 550 Address invalid (ID:550:1:1 (mi015.mc1.hosteurope.de)) Last-Attempt-Date: Wed, 17 Feb 2021 01:13:18 -0800 (PST)

2 3

List is down - RemovedInDjango30Warning
by Mark Dadgar Feb. 17, 2021

Feb. 17, 2021

So I did the latest mailman upgrades within my venv (per the instructions got from Brian Carpenter when he installed it for me) to the latest version. I had a strange CPU pegging issue that turned out to be mailman struggling with a malformed message but in the process of debugging that I downgraded to the previous mailman release. The resulted in a broken web interface. Today, while debugging, I did a pip install --upgrade of all the components as listed in a previous thread. Now none of the mailman3 processes will start. Doing a bin/mailman-post-update results in the error message below, which are consistent with the issues I saw earlier when trying to access the web interface. Anyone got a solution to this? I suspect it’s something simple, but django is just not my area of expertise. Thanks! - Mark ----- mark(a)pdc-racing.net | 408-348-2878 ——— (venv) mailman@mail:/opt/mailman/mm/bin$ ./mailman-post-update + '[' False == False ']' + mkdir -p /opt/mailman/mm/static + /opt/mailman/mm/bin/django-admin collectstatic --clear --noinput --verbosity 0 + /opt/mailman/mm/bin/django-admin compress Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/utils.py", line 66, in __getitem__ return self._engines[alias] KeyError: 'django' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/backends/django.py", line 121, in get_package_libraries module = import_module(entry[1]) File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1014, in _gcd_import File "<frozen importlib._bootstrap>", line 991, in _find_and_load File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 671, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 783, in exec_module File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/contrib/admin/templatetags/admin_static.py", line 5, in <module> from django.utils.deprecation import RemovedInDjango30Warning ImportError: cannot import name 'RemovedInDjango30Warning' from 'django.utils.deprecation' (/opt/mailman/mm/venv/lib/python3.8/site-packages/django/utils/deprecation.py) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailman/mm/venv/bin/django-admin", line 8, in <module> sys.exit(execute_from_command_line()) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 401, in execute_from_command_line utility.execute() File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 395, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/base.py", line 328, in run_from_argv self.execute(*args, **cmd_options) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/base.py", line 369, in execute output = self.handle(*args, **options) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/compressor/management/commands/compress.py", line 277, in handle self.handle_inner(**options) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/compressor/management/commands/compress.py", line 300, in handle_inner offline_manifest, block_count, results = self.compress(engine, extensions, verbosity, follow_links, log) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/compressor/management/commands/compress.py", line 100, in compress if not self.get_loaders(): File "/opt/mailman/mm/venv/lib/python3.8/site-packages/compressor/management/commands/compress.py", line 50, in get_loaders for e in engines.all(): File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/utils.py", line 90, in all return [self[alias] for alias in self] File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/utils.py", line 90, in <listcomp> return [self[alias] for alias in self] File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/utils.py", line 81, in __getitem__ engine = engine_cls(params) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/backends/django.py", line 25, in __init__ options['libraries'] = self.get_templatetag_libraries(libraries) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/backends/django.py", line 43, in get_templatetag_libraries libraries = get_installed_libraries() File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/backends/django.py", line 108, in get_installed_libraries for name in get_package_libraries(pkg): File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/backends/django.py", line 123, in get_package_libraries raise InvalidTemplateLibrary( django.template.library.InvalidTemplateLibrary: Invalid template library specified. ImportError raised when trying to load 'django.contrib.admin.templatetags.admin_static': cannot import name 'RemovedInDjango30Warning' from 'django.utils.deprecation' (/opt/mailman/mm/venv/lib/python3.8/site-packages/django/utils/deprecation.py)

2 2

Imported Digest Settings
by Brian Carpenter Feb. 17, 2021

Feb. 17, 2021

I am still seeing digest formatting issues with the import of Mailman 2 lists into Mailman 3. I am running the latest stable version of Mailman 3 core which is 3.3.3. This is what my client reported: > For the last three REDACTED digests I have been getting unusual and > unreadable characters? See example below. > >> Begin forwarded message: >> >> *From: *REDACTED >> *Subject: *REDACTED*Digest, Vol 2453, Issue 2* >> *Date: *February 13, 2021 at 12:30:24 AM PST >> *To: *REDACTED@REDACTED >> *Reply-To: *REDACTED@REDACTED >> >> �P*+]4�LaG@��[� S� XZ[ [�� \� �X�Z\��[ۜ� ‚] [� [�ܙ‚� � �X��ܚX�H ܈ >> [��X��ܚX�H �XH [XZ[ �[� H Y\��Y�H �] �X�X� ܂�� H� [ � ‚] [�\�\]Y\� >> [�ܙ‚�[�H �[� �XX� H \��ۈ X[�Y�[�� H \� ] �] [�[#<^_NSEDR_^#<ۙ\� >> [�ܙ‚�� [� �\ Z[�� X\�H Y ] [�\� �X�X� [�H �� ] \� [ܙH � X�Y�X [� �N� >> �۝ [� � و S� Y�\� �� ^I�� X�΂� K� �N� [� \� � [\ � >> �� ] >> \�B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKB�Y\��Y�N�B� >> ] N� �K L� �X��HL ��N�� L ��N� �� ] \� �� ] >> \�]\�X˘��O��X�X� � � S�H �N� [� \� � [\ • Έ �� [�Y[ �� [�Y[ >> ]ܙ[��K�Y O��Έ � S� H �[\ ] ^Y\�� [� \�] [ۘ[ �] �ܚˈ� [� >> [�ܙς�Y\��Y�KRQ � Q� >> � >> KM�� M� N Q �P��PL �P �] \�]\�X˘��O��۝ [� U \ N� ][ \ \� �[ \�] >> ]�N‚X��[� \�OP\ KSXZ[ M ь P�KL�L�KM ��KP�KM��̌#<^_NSEDR_^#<͌ >> L �Y\� H [�� YX�� H \� Y �[[^H [� � X� \� [�� Y] [�� Y�ܙH H Y� >> \� [� ] �Y[\� �\� Y [� �� \�H ��\ ] H ] [ � H �\� ۙH و \� � Y [� ˈ [ >> [�� ]�\�] [�� H �]�H YK �\� [� ]�Y X[ \ \�� [� �\�[ [�� X� [ۜˈ H >> �\�[ [�� X� [ۋ �H �\� �\� H [�� [\ ܝ [� [� �[ XX� H \� � H ۸�&] [�� >> H �]�H [ و \� � Y [� � H �[YH X] \�X[ ˈ ] �\� H ]X� [ܙH >> \�#<^_NSEDR_^#<ۘ[ ^�Y \ ��X� �܈ XX� � Y [� � H ��Y� \� �� ] H [� >> ܚ] [� � Y� H �]�H YH H \�� Y [� ]�[� ] � �� Y\� >> [�H ]�H � �H � � ۛ�� Y� ] \�JK ��\� �܈ �^[ۙ ] � [�� ] \��[� >> ��H ^H T ۙB� ۈ �X�L So the questions I have are: 1. Why does the formatting of digests change for some members when coming from MM2 to MM3? 2. What proble does the above example reveal? 3. What is the best approach to mitigate these issues? What I did: I had the client change the list member's digest setting from plain-text to mime. Was that the right instruction to do? -- Brian Carpenter Harmonylists.com Emwd.com

2 6