- Mailman-users - lists.mailman3.org

list owner creation
by Christian Stalberg 22 Feb '21

22 Feb '21

If one inadvertently deleted a list owner account, how could one either create a new account and make them a list owner -or- make an existing account a list owner? Thanks!

3 3

A new issue with installation
by Brian Carpenter 20 Feb '21

20 Feb '21

As usual, a new issue has arisen with installing Mailman 3. It seems Postorius and Hyperkitty want to install a module called cryptography. Which I am unable to install because of this: error: Can not find Rust compiler Question 1: Is cryptography a new addition to Hyperkitty/Postorius? Or was cryptography always included and something else is different about my installation process? "Building wheels for collected packages: hyperkitty, django-haystack, django-mailman3, mailmanclient, robot-detection, rcssmin, django-allauth, cryptography" Question 2: Will Hyperkitty/Postorius work without cryptography? I haven't proceed with this installation once I received the above error. Question 3: Are there any Mailman 3/Postorius/HK documentation that addresses with the installation of cryptography? -- Brian Carpenter Harmonylists.com Emwd.com

4 8

more about spanish translations
by Guillermo Hernandez (Oldno7) 20 Feb '21

20 Feb '21

I've just made a test creating a user in postorius to change an address that already has a suscription (from mailman 2.1). It's a test address with the digest enabled to be aware from any problem in the digest sending messages (e.g. I had to change all digest addresses to mime whe I did the migration from 2.1) The fact is that I cannot find from which template or Weblate term chains it could be from, and the address confirmation email is a language mix in spanish and english. I copy it down. I would like to translate it all, but as said, I cannot find where to do it. I wonder if it's comes from another package as allauth or something like this. Here is the mail: Subject: =?utf-8?q?=5Bescepticos=2Ees=5D_Por_favor_confirmar_direcci=C3=B3n_de_correo?= =?utf-8?q?_electr=C3=B3nico?= From: postorius(a)XXXXXXXXXXX.es To: XXXXXXXX(a)gmail.com Date: Fri, 19 Feb 2021 10:26:26 -0000 Message-ID: <161373038620.5080.16387108004007982309(a)XXXXXXX.es> X-Spam-Status: No, score=-1.0 required=8.0 tests=ALL_TRUSTED=-1,URIBL_BLOCKED=0.001 <dns:XXXXXXXXX.es> [172.67.131.28, 104.21.3.190] <dns:XXXXXXXXXX.es?type=MX> [0 XXXXXXXXXXXX.es.] autolearn=unavailable autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on XXXXXXXXXXX.es Hello from XXXXXXXXXXX.es! You're receiving this e-mail because user XXXXXXXXXX(a)gmail.com has given your e-mail address to register an account on XXXXXXXXXXXXXXX.es. To confirm this is correct, go to https://XXXXXXXXXXX.es/mailman3/accounts/confirm-email/MTM:1lD2zR:3GpALYKI1… Muchas gracias por usar XXXXXXXXXX.es! XXXXXXXXXXX.es

2 3

How to modify system preferences
by Jack Lenox 19 Feb '21

19 Feb '21

Hello everyone, I've been making headway with getting Mailman 3 to run how I like it. However I've hit something of a road-block with system preferences. By that, I'm referring to the default set of preferences set out in the documentation here: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… The documentation states that these are only accessible in a read-only format via the REST API, but presumably there is a way of modifying these somewhere? I can't find a way of specifying this in my config and can't find a relevant example in the sample schema.cfg. At this stage, all I want to do is set the default for "receive_own_postings" to False. Can anyone point me in the right direction here? Many thanks! Jack

3 2

archiving problem & updates
by Christian Stalberg 19 Feb '21

19 Feb '21

Archiving has stopped working. No changes were made to the server. How can I diagnose and troubleshoot this please? Are there instructions for how to update mailman3 somewhere? Is there a listing of bug fixes also? Thank you!

3 5

Membership list changes
by Vako Nicolian 18 Feb '21

18 Feb '21

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) 18 Feb '21

18 Feb '21

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 18 Feb '21

18 Feb '21

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 18 Feb '21

18 Feb '21

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 18 Feb '21

18 Feb '21

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