February 2020 - Mailman-users - lists.mailman3.org

Mass unverified subscriptions end up as pending user confirmation instead.
by hansen＠rc.org 26 Feb '20

26 Feb '20

After mass subscribing with these settings: Pre confirm: Yes, Pre approved: Yes, Pre Verified (sic): No the addresses appeared in the list's 'Pending user confirmation' list. They were pre-confirmed. The addresses did not appear in the Django Admin's non-verified addresses list. They were not verified. Also why does Postorius lists just 'Pending Approval' and 'Pending Confirmation' but not 'Pending Verification'? Yours, Allan

2 1

Tags in Hyperkitty
by Gila Halpern 21 Feb '20

21 Feb '20

Are tags still under development? They don't appear to do anything at the moment, they are not searchable, and clicking on existing tags does nothing.

2 1

leaving Sympa for MM3
by rance.hall＠esu10.org 21 Feb '20

21 Feb '20

Our shop is an educational shop and left mailman many years ago for Sympa because of features in Sympa not in mailman. Currently Sympa is showing its age, and is relying on perl modules that have been EOL's and the Sympa community has not discussed (within in ear-shot of me at least) what to do about it. We found that we are not using the extra features Sympa provides anymore and with MM3 already dockerized it seems that MM3 is a much better fit for our organization for the foreseeable future. So I got a dockerized setup up and running in a test environment and am pleased with the results except for now I have to start thinking about migration from Sympa to MM3. The API is useful in this effort as there are python wrappers already done and I didn't have any trouble scripting list creation with the API tools to migrate list owners, moderators and users. Now for the question/hard part. Migrating list archives. In Sympa the list archive is just a maildir format directory structure reflecting month/year. In MM3 the Archive is stored in the db with attributes that are likely only available as the message is processed. I'd really rather not loose the archive data if I can help it. Does anyone have any thoughts on how I could perhaps import this?

2 1

Advice on migrating to Mailman 3
by Christoph Groth 20 Feb '20

20 Feb '20

Dear Mailman 3 users, Currently we are hosting the website [1] and mailing list [2] of our free software project with a shared hosting plan of a webhosting company. As such there is no dedicated server, but we do have SSH access (as a regular user) to the shared server. The mailing list software (Mailman 2) is administrated separately by our hoster on a dedicated machine. We are rather happy with this setup: we pay about 10 USD per month and have only little administration work to do. The only problem is that our list runs on Mailman 2. We would like to move to Mailman 3, but this does not seem to be that simple. Perhaps someone here would be so kind to give us advice? The number of (shared) hosters who offer Mailman 3 seems to be very limited [3]. Would it be a good idea to book a virtual private server (VPS) somewhere, that runs, say, Debian, and simply install Mailman 3 through the distribution’s package system? I’m already running a small personal box with nginx on it, and this is very little work, but running Mailman would require sending out up to a few thousand email messages per day (our list has a few hundred subscribers). Is this something that one is commonly allowed to do on a VPS system? Most VPS offers that I see are silent about mail. If we setup such a system, can we assume that it will silently operate without causing much administration work most of the time (like my nginx server)? Or is maintaining a Mailman 3 server a significant burden ([2] seems to imply that)? If yes, are you aware of organizations that propose Mailman 3 hosting for open source projects? Python.org seems to host some lists for third party projects, but otherwise I haven’t seen much. Thanks Christoph [1] https://kwant-project.org/ [2] https://mailman-mail5.webfaction.com/listinfo/kwant-discuss [3] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…

6 6

Email verification
by Allan Hansen 19 Feb '20

19 Feb '20

Some members cannot get past the email verification when they create their accounts. They insist that they have looked in their spam folders. Their email addresses they entered are correct - the are able to log into their accounts with the right email address. But they get the message saying that a confirmation message was sent and if they don’s see it to contact us. 1. Who is ‘us’? My members are asking... 2. How do I help them? I tried subscribing them to a bogus list with pre-verified email, but that did not work, so both they and I are stuck. Tried finding help in archive, but did not see anything. Yours, Allan Hansen hansen(a)rc.org

4 9

Installing MM3 via pip fails…
by Patrick Ben Koetter 18 Feb '20

18 Feb '20

Has anyone managed to install MM3 recently using pip on Ubuntu 18? I followed the instructions at https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…. As soon as I get to the Django part things get hairy. It seems Django requires something that was removed from it. Any ideas or experience how I can get around that? p@rick -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG,80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief Aufsichtsratsvorsitzender: Florian Kirstein

2 4

No module named 'hyperkitty.urls' after upgrading python3
by jean-christophe manciot 18 Feb '20

18 Feb '20

Ubuntu 20.04 python3 3.8.0-3 python3-django-hyperkitty: 1.3.2 ``` Traceback (most recent call last): File "/usr/share/mailman3-web/manage.py", line 10, in <module> execute_from_command_line(sys.argv) File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 381, in execute_from_command_line utility.execute() File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 375, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 323, in run_from_argv self.execute(*args, **cmd_options) File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 361, in execute self.check() File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 387, in check all_issues = self._run_checks( File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 377, in _run_checks return checks.run_checks(**kwargs) File "/usr/lib/python3/dist-packages/django/core/checks/registry.py", line 72, in run_checks new_errors = check(app_configs=app_configs) File "/usr/lib/python3/dist-packages/django/core/checks/urls.py", line 13, in check_url_config return check_resolver(resolver) File "/usr/lib/python3/dist-packages/django/core/checks/urls.py", line 23, in check_resolver return check_method() File "/usr/lib/python3/dist-packages/django/urls/resolvers.py", line 399, in check for pattern in self.url_patterns: 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/urls/resolvers.py", line 584, in url_patterns patterns = getattr(self.urlconf_module, "urlpatterns", self.urlconf_module) 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/urls/resolvers.py", line 577, in urlconf_module return import_module(self.urlconf_name) 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 "/etc/mailman3/django/urls.py", line 30, in <module> url(r'^hyperkitty/', include('hyperkitty.urls')), File "/usr/lib/python3/dist-packages/django/urls/conf.py", line 34, in include urlconf_module = import_module(urlconf_module) 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 973, in _find_and_load_unlocked ModuleNotFoundError: No module named 'hyperkitty.urls' ``` ``` # dpkg --contents python3-django-hyperkitty_1.3.2+b1-20.04_amd64.deb|grep urls -rw-r--r-- root/staff 1356 2020-01-14 12:22 ./usr/local/lib/python3.7/dist-packages/HyperKitty-1.3.2-py3.7.egg/example_project/urls.py -rw-r--r-- root/staff 1043 2020-01-14 12:22 ./usr/local/lib/python3.7/dist-packages/HyperKitty-1.3.2-py3.7.egg/hyperkitty/tests/urls_test.py -rw-r--r-- root/staff 7783 2020-01-14 12:22 ./usr/local/lib/python3.7/dist-packages/HyperKitty-1.3.2-py3.7.egg/hyperkitty/urls.py -rw-r--r-- root/root 1356 2019-09-01 02:56 ./usr/share/doc/python3-django-hyperkitty/examples/urls.py ``` No such issue with python3 3.7.5-3. Any suggestion?

3 6

Random characters in "The results of your email commands" e-mail
by Jeffrey D 18 Feb '20

18 Feb '20

Hi, Today I sending an e-mail to "mylist-request(a)domain.tld" with the subject "help" and I received the expected e-mail with the following content; confirm - Confirm a subscription request. echo - Echo back your arguments. end - Stop processing commands. help - Get help about available email commands. join - Join this mailing list. leave - Leave this mailing list. stop - An alias for 'end'. subscribe - An alias for 'join'. unsubscribe - An alias for 'leave'. No such command: -- No such command: vriendelijke Only I think my mail signature broke something in Mailman (see the No such command). Because every e-mail with a subject like "help", "stop" or "join", gives a reply with random characters. The Mailman logs doesn't show any error, so I'm not sure what is wrong. Deleting the mailinglist and create a new one won't fix the issue, also restarting Mailman doesn't help. An example of the random characters: Nzzf&ju[zZ0:v,jzkb^}nJyazZCj}{m5t5Cx<{iysG5o[w}jgn+g[lrwf*mzrLk)rjwliazZZnjyW(fvrh{aXXWj+&j)b b-'jX+zwl&v{rx &~y6.r(fu4:' Is this a bug in Mailman? Or something in my Mailman config...

2 2

Listing/Exporting member list error: Mailman REST API not available. Please start Mailman core.
by Thomas Lehker 17 Feb '20

17 Feb '20

Our MailMan3 server is extremely slow and when trying to list or export members for a larger list it is throwing 'Mailman REST API not available. Please start Mailman core'. In Mailman core logs I am seeing [27] [CRITICAL] WORKER TIMEOUT (pid:40) [43] [INFO] Booting worker with pid: 43 Has anyone seen this issue? Is there any way to increase 'timeouts'? Thanks for any help! Tom Mailman Novice 16/Jan/2020:16:55:58 +0000] "GET /3.1/lists/somelist(a)somelist.com/requests HTTP/1.1" 200 982 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:55:58 +0000] "GET /3.1/lists/somelist(a)somelist.com/held?count=50&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:55:58 +0000] "GET /3.1/lists/list.somelist.com HTTP/1.1" 200 347 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:55:58 +0000] "GET /3.1/lists/list.somelist.com/roster/owner HTTP/1.1" 200 634 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:01 +0000] "GET /3.1/lists/list.somelist.com/roster/moderator HTTP/1.1" 200 638 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:01 +0000] "GET /3.1/lists/somelist(a)somelist.com/config HTTP/1.1" 200 2257 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:05 +0000] "GET /3.1/lists/list.somelist.com/archivers HTTP/1.1" 200 81 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:08 +0000] "GET /3.1/lists/list.somelist.com/archivers HTTP/1.1" 200 81 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:08 +0000] "GET /3.1/lists/somelist(a)somelist.com/requests HTTP/1.1" 200 982 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:10 +0000] "GET /3.1/lists/list.somelist.com/member/somelist@somelist HTTP/1.1" 404 26 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:16 +0000] "GET /3.1/lists/somelist(a)somelist.com/requests HTTP/1.1" 200 982 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:19 +0000] "GET /3.1/lists/somelist(a)somelist.com/held?count=50&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:26 +0000] "GET /3.1/lists/list.somelist.com HTTP/1.1" 200 347 "-" "GNU Mailman REST client v3.3.0" [2020-01-16 16:56:58 +0000] [27] [CRITICAL] WORKER TIMEOUT (pid:40) [2020-01-16 16:57:00 +0000] [43] [INFO] Booting worker with pid: 43 DISCLAIMER: The information contained in this message is privileged and confidential. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please reply to the message and delete/destroy any copy of this message. Information in this message that does not relate to the official business of the firm shall be understood as neither given nor endorsed by it.

4 4

Mailman stopping message distribution because of SMTP errors
by Victoriano Giralt 12 Feb '20

12 Feb '20

Hi list, I have recently migrated some lists from Mailman 2 to Mailman 3. Users have been added using the mailman client as pre-verified addresses so the migration happened "silently". Thus, there was a dozen "bad" addresses (domains that did not exist anymore). Unfortunately, Mailman got some of the "bad" addresses in the first message batch for sending out, so, Postfix closed the connection because of "too many errors" and this stopped the process completely, i.e. Mailman did not continue sending messages to the rest of the list over 600 addresses. There was no more information in the logs than the Postfix error messages in smtp.log. Once the "bad" addresses were removed, the list started working as expected. I consider this a bug. The bouncing addresses should have been marked as "non deliverable" and the subscriptions "paused" and the rest should have been delivered. Or, the list owner should have been notified that there was a problem with message distribution. None of these happened. Thanks! -- Victoriano Giralt CIO University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

2 2