- Mailman-users - lists.mailman3.org

Initial success: Mailman 3.3 integrated with Zimbra 8.8
by Morris Jones Dec. 2, 2020

Dec. 2, 2020

I have a very old existing mail server running Zimbra 6 with a mailman 2.1 instance alongside. I needed to rebuild my mail server for some compelling reasons (the old server used outdated TLS protocol, I could no longer compile clamav, nothing could really be updated). The final straw was a lack of support for my old commercial SSL certificates. I patched in a letsencrypt certificate to get through the past six months. I'm in the process of commissioning a new mail server using an 8GB Linode, Ubuntu 18, Zimbra 8.8, and Mailman 3.3. A couple of days ago I had my first successful list creation, with user confirmation working by email. I have django running with uwsgi, and am using Zimbra's installed nginx proxy to reverse proxy http traffic to Postorius and Hyperkitty. Nginx is doing the SSL layer. The mailman core mta hooks are all done using Zimbra's "local configuration" technique. In theory I should be able to do Zimbra upgrades with a minimum of hassle. I've written up a "case history" of how it came together. I have a .rst file in a gitlab project here: https://gitlab.com/MojoLA/mailman3.3-zimbra-8.8-integration I suppose this is a crazy project, but it's worthwhile to me. (Mark, thank's so much for integrating the virtual domain maps. It took me about three days to recognize that they were the solution to bounced mails to list-owner@...) Now I can spend some time migrating my email accounts (only four) from the old server to the new one, and move a dozen or so mailing lists to the new mailman3 instance. I'll have to get accustomed to a new way to manage the mail lists, and already really like what I've seen. Thank you. :) Best regards, Mojo -- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>

1 0

Mailmansuite.log Entries
by Brian Carpenter Dec. 2, 2020

Dec. 2, 2020

I see the following log entries in mailmansuite.log: INFO 2020-11-28 00:00:52,242 29142 hyperkitty.lib.mailman 2117 emails left to refresh, checked 1000 INFO 2020-11-28 00:01:00,600 29142 hyperkitty.lib.mailman 2117 emails left to refresh, checked 2000 INFO 2020-11-29 00:00:52,135 15513 hyperkitty.lib.mailman 2117 emails left to refresh, checked 1000 INFO 2020-11-29 00:01:00,192 15513 hyperkitty.lib.mailman 2117 emails left to refresh, checked 2000 INFO 2020-11-30 00:00:52,484 22622 hyperkitty.lib.mailman 2117 emails left to refresh, checked 1000 INFO 2020-11-30 00:01:00,758 22622 hyperkitty.lib.mailman 2117 emails left to refresh, checked 2000 INFO 2020-12-01 00:00:50,246 11946 hyperkitty.lib.mailman 2117 emails left to refresh, checked 1000 INFO 2020-12-01 00:00:59,688 11946 hyperkitty.lib.mailman 2117 emails left to refresh, checked 2000 I assume this is a result of importing archives from a MM2 mbox file. This happen months ago however. Why are these entries still showing up? -- Brian Carpenter Harmonylists.com Emwd.com

2 3

12/24 hour clock ?
by Per Jessen Nov. 28, 2020

Nov. 28, 2020

Hi all at openSUSE we have recently migrated to mailman3, and we seem to be having a couple of teething issues: a) hyperkitty and postorius both seem to insist on using a 12 hour clock format, no matter what the user has set. Is there a way of changing it system-wide ? b) overriding the default set of footers - despite having set the template "list:member:regular:footer" to empty for a specific list, I am still getting the default footers attached. We are using version 1.3.3. thanks Per Jessen

2 2

No styling for web apps?
by Morris Jones Nov. 27, 2020

Nov. 27, 2020

I have most of a new mailman suite server built and working ... collectstatic gathered a good array of static files (uncompressed so far) nginx appears to be serving them successfully The Firefox developer tools show css and js files all being delivered But none of the postorius or hyperkitty pages exhibit any styling at all, only bare HTML elements. The Firefox inspector will show the available styles being requested and delivered (style.css, bootstrap, jquery, all the things). But if I use the inspector to look at the page, nothing has any CSS properties. I know I'm missing something simple. (Happy Thanksgiving!) Mojo -- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>

2 3

where is manage.py for migration?
by Dan Langille Nov. 26, 2020

Nov. 26, 2020

Hello, I am following https://docs.mailman3.org/en/latest/migration.html and I'm trying to "Migrate the list archives from Mailman 2 to Mailman 3 by running the following command": [mailman@mailman ~]$ python manage.py hyperkitty_import -l biking(a)lists.example.org /usr/local/mailman/archives/private/biking.mbox python: can't open file 'manage.py': [Errno 2] No such file or directory Is the documentation correct? I cannot locate manage.py in the code: $ git clone https://gitlab.com/mailman/mailman.git Cloning into 'mailman'... ... $ cd mailman/ $ find . -name manage.py $ Am I doing this wrong? Thank you. -- Dan Langille dan(a)langille.org

2 1

mailman 3.3.2 config file location
by Eric Broens Nov. 25, 2020

Nov. 25, 2020

Hi, I am trying to install Mailman 3.3.2 in a python virtual environment, and don't understand why the following is happening.When executing "mailman info", it shows that "the config file is located in /etc/mailman3/mailman.cfg as is intended, hence "outside" the virtual environment. However, after having started mailman, and running "mailman info" again, the default (empty) config files seems to be created in the directory where mailman has been started:config file: /opt/mailman/mailman-suite/mailman-suite_project/var/etc/mailman.cfg This happens even when mailman is started with the option "-C /etc/mailman3/mailman.cfg".Does this mean that the config file needs to be located in a subdirectory of python's virtual environment? (venv) [root@test-vps mailman-suite_project]# mailman infoGNU Mailman 3.3.2 (Tom Sawyer)Python 3.6.8 (default, Apr 16 2020, 01:36:27)[GCC 8.3.1 20191121 (Red Hat 8.3.1-5)]config file: /etc/mailman3/mailman.cfgdb url: mysql+pymysql://*****:*****@localhost/mailman?charset=utf8&use_unicode=1devmode: DISABLEDREST root url: http://localhost:8001/3.1/REST credentials: restadmin:restpass (venv) [root@test-vps mailman-suite_project]# mailman startStarting Mailman's master runnerGenerating MTA alias maps (venv) [root@test-vps mailman-suite_project]# mailman infoGNU Mailman 3.3.2 (Tom Sawyer)Python 3.6.8 (default, Apr 16 2020, 01:36:27)[GCC 8.3.1 20191121 (Red Hat 8.3.1-5)]config file: /opt/mailman/mailman-suite/mailman-suite_project/var/etc/mailman.cfgdb url: sqlite:////opt/mailman/mailman-suite/mailman-suite_project/var/data/mailman.dbdevmode: DISABLEDREST root url: http://localhost:8001/3.1/REST credentials: restadmin:restpass Thanks,Eric

2 2

Welcome Message
by brian＠emwd.com Nov. 25, 2020

Nov. 25, 2020

Is it possible for a list admin to modify the welcome message for a list via Postorius? Is the process: 1. Log into Postorious 2. Click on the Templates tab. 3. Select New Template. 4. Select "The notice sent to a member when they are subscribed to the mailing list" 5. Add your text and click the save button. Is the correct process? I am using the latest Docker release of Mailman 3.

5 25

Mailman automatic accept notification
by tambet.paide＠mkm.ee Nov. 25, 2020

Nov. 25, 2020

How can I configure mailman so that all the users in mailing list won't get automatic accept notification (uncaught bounce notification)? I'm using Mailman 3 and cat figure it out

1 0

Mailman Core 3.3.2 is now out
by Abhilash Raj Nov. 25, 2020

Nov. 25, 2020

Hi Everyone, I am pleased to announce that with a week long delay from the planned date, GNU Mailman Core 3.3.2 is now finally out. This release includes both bug fixes and some new features. Some notable changes include: - Support for inviting users to join mailing lists. - New adddmembers, delmembers and syncmembers command to manage membership from CLI. - Addition of new REST API endpoints that return the count of held messages and subscription requests of much faster page loads in Postorius. - Addition of support for filtering in some API endpoints like Members and Subscription requests. - Support for address= option in email join command to subscribe an address other then sending address. - Addition of who email command to lookup memberships. - Expose emergency field for MailingList resource in REST API. - Several bug fixes to support new major version of libraries like dnspython, flufl.* etc. You can install it using: $ pip install --upgrade mailman The tarball for the release is available at PyPI: https://pypi.org/project/mailman/ Finally, many thanks to all the contributors who have helped make this release a success! -- Abhilash Raj (maxking) on behalf of Mailman Core team

5 12

Moderation not working?
by peter＠chubb.wattle.id.au Nov. 24, 2020

Nov. 24, 2020

Hi Folks, Running a shiny new instance of mailman3, as per the Debian package (version 3.2.2) but the moderation doesn't seem to work. WE got hit by a heap of spammers overnight, even though the 'hold for moderation' bit is set for non-members (and now for members too). Emails seem just to get straight through. Any advice on how to debug this? Would upgrading to a later version using pip help? Peter C

2 3