On Sun, 9 Dec 2018 at 22:37, Mark Sapiro <mark@msapiro.net> wrote:
On 12/9/18 10:14 AM, Odhiambo Washington wrote:
In my quest to run Mailman3, I obtained a VM running Ubuntu 18.04 and started on getting to run Mailman3. I found this link -> https://github.com/iomarmochtar/mailman3_ei It has instructions which looked fairly simple to get Mailman3 installed. However, I did encounter some hitches since the script is not meant for Ubuntu.
First, a more appropriate list for Mailman 3 is mailman-users@mailman3.org <https://lists.mailman3.org/mailman3/lists/mailman-users@mailman3.org/>.
I am shifting to that list, after this.
Also, we find it very difficult to address issues arising from third party packages and how-tos. See <https://wiki.list.org/x/12812344>.
And, there is a Mailman 3 package for Debian/Ubuntu
apt install mailman3-full
In all my searching, I never found this in any documentation. I must have been searching in the wild, or my FreeBSD-mindedness got me stuck to containers and VENVs.
With a few runs and observing the logs and modifying the script at every step it encountered and error, I finally managed to install Mailman3. It seems this is what you guys call a virtual environment in the Linux world? :-)
I think the virtual environment in this case is a Python thing, not a Linux thing.
I agree with you on that.
<snip>
Much of what I snipped is specific to <https://github.com/iomarmochtar/mailman3_ei>, the details of which I'm not interested in learning.
That is fine. I have put it aside for now.
From this point now is where I need help - serious help in smoothening things up and getting to understand these venv stuff!
So I did run 'service mailman3 start' but this seems to be waiting for too long to drop me back into the CLI. I also run 'systemctl start supervisord' and that seems to work. What I am not sure is whether 'systemctl stop supervisord' actually does what it is expected to do because after I execute it, I still see processes running that I think are related.
So far, I have been able to access the webUI on my VM using https://N.N.N.N:9090 I created a domain. But when I create a test list, I get an error - and I do not have a clue which logfile would have the error details - nginx or mailman... (I am 100% new to nginx).
The nginx logs generally aren't too useful. Both Mailman core and Django write logs. Core's log is probably in var/log/mailman.log where is defined in mailman.cfg as var_dir. Django's log is defined in Django's settings in the LOGGING setting.
Which file contains Django's settings?
So now, I am stuck at: thinking!)
- Creating the mailing list
- Getting to know whether the archiver is installed and running
- Knowing is there are cron jobs to be running (Mailman2 type of
See <http://docs.mailman3.org/en/latest/config-core.html#configuring-cron-jobs
and < http://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required
Great to see that. I'll read and see if I make heads or tails of the writeup.
Ultimately I need to figure out:
- How the mailman queue runners are started and stopped
mailman start
Why not systemctl mailman start?? Just wondering, as that is what I am seeing is common in Ubuntu. Does this make the components start after a reboot?
- Migrate s few lists from Mailman2 to this Mailman3
mailman import21 <django management> hyperkitty_import
Please show me where that is documented. I have to pull my lists from an old machine to this new one.
- Mailman3 should use MySQL storage and Exim4 as the MTA (I have configured these bits in mailman.cfg)
You also need to configure MySQL in Django. See the DATABASES setting in the Django settings.
So, when you talk about Django settings, you are referring to mailman.cfg file??? :-)
I have spent all my weekend till now, trying to figure all this out. Life seems a little easier with mm2.x ....
Thank you.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft."