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