Hi folks, I spent many hours last night trying to get Mailman 3 up and running. I am using Ubuntu on a Digital Ocean LAMP droplet (so PHP, Apache, Sql, and Postfix are already installed). The LAMP stack works as I have a successful installation of YOURLS going on.
So, I tried to use this guide (https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plant...) to install the Mailman3 package and got to the configuration screen (the one with all the DOS-esque GUI). I ran it but it kept saying the DB wasn't installed. Was I supposed to create SQL databases and users before running that and use those usernames/databases in the credentials it asks for? It doesn't seem like that in the way it asks the questions (since it asks to create a password) but I wasn't sure.
Anywho, I tried to remove the package completely and restart but I keep spinning my wheels. So my questions:
- Does that guide actually work? Did I just foul up the database part?
- Is there a better way to install mailman3 with some nice step-by-step directions to follow?
- Is there a way to completely wipe my previous installs without wiping the server? ( I didn't back up...silly I know ). I used apt-get --purge remove to uninstall mailman3 and mailman to start over, did that do the trick?
Sorry for all the questions.
On Sat, 25 Jul 2020 at 20:35, <joseverde@gmail.com> wrote:
Hi folks, I spent many hours last night trying to get Mailman 3 up and running. I am using Ubuntu on a Digital Ocean LAMP droplet (so PHP, Apache, Sql, and Postfix are already installed). The LAMP stack works as I have a successful installation of YOURLS going on.
So, I tried to use this guide ( https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plant...) to install the Mailman3 package and got to the configuration screen (the one with all the DOS-esque GUI). I ran it but it kept saying the DB wasn't installed. Was I supposed to create SQL databases and users before running that and use those usernames/databases in the credentials it asks for? It doesn't seem like that in the way it asks the questions (since it asks to create a password) but I wasn't sure.
Anywho, I tried to remove the package completely and restart but I keep spinning my wheels. So my questions:
- Does that guide actually work? Did I just foul up the database part?
- Is there a better way to install mailman3 with some nice step-by-step directions to follow?
- Is there a way to completely wipe my previous installs without wiping the server? ( I didn't back up...silly I know ). I used apt-get --purge remove to uninstall mailman3 and mailman to start over, did that do the trick?
Sorry for all the questions.
DISCLAIMER: I have no experience at all with MM3. I haven't even succeeded in installing it as yet because I am trying to do it manually on FreeBSD. I have an Ubuntu box that runs mailman-2.1.34 manually installed as well, but I am wondering if you tried the following:
root@lists:/home/wash# apt search mailman3 Sorting... Done Full Text Search... Done mailman3/bionic 3.2.0-1~ubuntu18.04.1 all [residual-config] Mailing list management system
mailman3-doc/bionic 3.2.0-1~ubuntu18.04.1 all Mailing list management system documentation
mailman3-full/bionic 3.2.0-1~ubuntu18.04.1 all Full Mailman3 mailing list management suite (metapackage)
mailman3-web/bionic 0+20180916-2~ubuntu18.04.1 all [residual-config] Django project integrating Mailman3 Postorius and HyperKitty
python-django-hyperkitty/bionic 1.1.4-4 all Web user interface to access GNU Mailman3 archives
python-django-mailman3/bionic 1.1.0-4 all Django library to help interaction with Mailman3 (Python 2 version)
python-django-postorius/bionic 1.1.2-3 all Web user interface to access GNU Mailman3
python-mailmanclient/bionic 3.1.1-5 all Python bindings for Mailman3 REST API (Python 2 version)
python-mailmanclient-doc/bionic 3.2.0-2~ubuntu18.04.1 all Python bindings for Mailman3 REST API (Documentation)
python3-django-hyperkitty/bionic 1.2.1-3~ubuntu18.04.1 all Web user interface to access GNU Mailman3 archives
python3-django-mailman3/bionic 1.2.0-2~ubuntu18.04.1 all Django library to help interaction with Mailman3 (Python 3 version)
python3-django-postorius/bionic 1.2.2-2~ubuntu18.04.1 all Web user interface to access GNU Mailman3
python3-mailman-hyperkitty/bionic 1.1.0-9~ubuntu18.04.1 all [residual-config] Mailman3 plugin to archive emails with HyperKitty
python3-mailmanclient/bionic 3.2.0-2~ubuntu18.04.1 all Python bindings for Mailman3 REST API (Python 3 version)
root@lists:/home/wash# apt install mailman3 Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: python3-aiosmtpd python3-alembic python3-dateutil python3-falcon python3-flufl.bounce python3-flufl.i18n python3-flufl.lock python3-lazr.config python3-lazr.delegates python3-mako python3-mimeparse python3-nose python3-passlib python3-psycopg2 python3-public python3-sqlalchemy python3-sqlalchemy-ext python3-zope.configuration python3-zope.i18nmessageid python3-zope.schema Suggested packages: mailman3-doc python3-editor python-flufl.bounce-doc python-flufl.i18n-doc python-flufl.lock-doc python-lazr.config-doc python-lazr.delegates-doc python3-beaker python-mako-doc python-nose-doc python-psycopg2-doc python-public-doc python-sqlalchemy-doc python3-mysqldb python3-fdb python3-zope.testing The following NEW packages will be installed: mailman3 python3-aiosmtpd python3-alembic python3-dateutil python3-falcon python3-flufl.bounce python3-flufl.i18n python3-flufl.lock python3-lazr.config python3-lazr.delegates python3-mako python3-mimeparse python3-nose python3-passlib python3-psycopg2 python3-public python3-sqlalchemy python3-sqlalchemy-ext python3-zope.configuration python3-zope.i18nmessageid python3-zope.schema 0 upgraded, 21 newly installed, 0 to remove and 2 not upgraded. Need to get 2,862 kB of archives. After this operation, 16.7 MB of additional disk space will be used. Do you want to continue? [Y/n]
Where would that end you???
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
joseverde@gmail.com writes:
Hi folks, I spent many hours last night trying to get Mailman 3 up and running. I am using Ubuntu on a Digital Ocean LAMP droplet (so PHP, Apache, Sql, and Postfix are already installed). The LAMP stack works as I have a successful installation of YOURLS going on. So, I tried to use this guide (https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plant...)
That's not our guide, we don't support it, and at least I don't recognize the author offhand, can't speak for the rest of the team.
Now that our NO WARRANTY notice is out of the way, I will say that guide is written in very good style, with great attention to detail and appropriate warnings about delicate parts of the procedure. If you end up succeeding with it, I'll add a link to it to our docs.
to install the Mailman3 package and got to the configuration screen (the one with all the DOS-esque GUI).
That's Ubuntu's UI, not ours. Your questions so far are all really Ubuntu questions, not Mailman questions. We'll do what we can to answer, but I don't think any of the core developers use Ubuntu packages to manage their Mailman installations. You are likely to get more help, more accurate help, and faster help in Ubuntu (or perhaps Debian) channels.
I ran it but it kept saying the DB wasn't installed.
Mailman can use any of several database backends (at least SQLite3, PostgreSQL, and MySQL). It seems possible that Ubuntu Mailman is configured for one, and the preinstalled one is another. Which SQL implementation was preinstalled, and which one are Mailman and Django configured to use?
- Does that guide actually work?
Ask the author, not us. Internal evidence (quality of presentation, dates, the NOTE at the top) strongly suggests it works for somebody.
Did I just foul up the database part?
Not clear what got fouled up or where in the process, but clearly getting database installation and configuration right is necessary to proceed.
- Is there a better way to install mailman3 with some nice step-by-step directions to follow?
Don't know. We provide docker containers, but I don't know if those are compatible with Digital Ocean's droplets.
Our docs are at mailman.readthedocs.io, but they're not step-by-step the way the guide you reference is because they're distribution- agnostic, and generally oriented toward a build from source.
- Is there a way to completely wipe my previous installs without wiping the server? ( I didn't back up...silly I know ).
Just wipe the server and create a backup image. Multiple, if you have the space for one every time you successfully install and configure a subsystem. You will save yourself a lot of time.
dpkg --purge will wipe out the Mailman stuff, but if your config process touched anything else (the database, the MTA config) rerunning the process is not guaranteed to do the right thing. It probably will do the right thing, but why not be sure you have a reset to known state?
Steve
On 7/26/20 12:37 AM, Stephen J. Turnbull wrote:
That's not our guide, we don't support it, and at least I don't recognize the author offhand, can't speak for the rest of the team.
The author has been involved in a few threads on this list.
Now that our NO WARRANTY notice is out of the way, I will say that guide is written in very good style, with great attention to detail and appropriate warnings about delicate parts of the procedure. If you end up succeeding with it, I'll add a link to it to our docs.
It is currently linked from the first paragraph at <https://wiki.list.org/DOC/Mailman%203%20installation%20experience>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Sun, 26 Jul 2020 at 18:22, Mark Sapiro <mark@msapiro.net> wrote:
On 7/26/20 12:37 AM, Stephen J. Turnbull wrote:
That's not our guide, we don't support it, and at least I don't recognize the author offhand, can't speak for the rest of the team.
The author has been involved in a few threads on this list.
Now that our NO WARRANTY notice is out of the way, I will say that guide is written in very good style, with great attention to detail and appropriate warnings about delicate parts of the procedure. If you end up succeeding with it, I'll add a link to it to our docs.
It is currently linked from the first paragraph at <https://wiki.list.org/DOC/Mailman%203%20installation%20experience>.
I followed the steps outlined in the subject document and got mailman3 running. However, what is missing in that document is the process of setting up a webserver for accessing the MM3 UI. I have spent two days trying to figure out that aspect and discovered a few things (I could be wrong in what I think):
- For one to use the uwsgi.ini that is dropped in /etc/mailman3/ by the installation process, the uwsgi daemon must be installed:
*apt install uwsgi-core uwsgi*
The uwsgi.ini must be linked in the directory where the uwsgi daemon looks for config files: *cp /etc/mailman3/uwsgi.ini /etc/uwsgi/apps-available/uwsgi.ini* *ln -s /etc/uwsgi/apps-available/uwsgi.ini /etc/uwsgi/apps-enabled/uwsgi.ini*
The uwsgi daemon needs to be started *systemctl start uwsgi*
root@lists:/etc/mailman3# ps ax | grep wsgi 5838 ? S 0:00 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/uwsgi.ini --daemonize /var/log/uwsgi/app/uwsgi.log 5841 ? Sl 0:00 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/uwsgi.ini --daemonize /var/log/uwsgi/app/uwsgi.log 5842 ? Sl 0:00 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/uwsgi.ini --daemonize /var/log/uwsgi/app/uwsgi.log
Now that uwsgi daemon is running, the last step would be to configure the webserver to serve the MM3 pages.
The apache config snippet dropped by the mailman3 install process in /etc/mailman3/apache.conf contains:
<BEGIN> Alias /mailman3/favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico Alias /mailman3/static /var/lib/mailman3/web/static
<Directory "/var/lib/mailman3/web/static"> Require all granted </Directory>
<IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ </IfModule> <END>
I added those to a virtualhost where I am running mailman2.x, but I couldn't access any of the defined aliases:
https://lists.my.site/mailman3/static/ - gives "You don't have permission to access this resource." Apache says AH01276: Cannot serve directory /var/lib/mailman3/web/static/: No matching DirectoryIndex (index.html,index.cgi,index.pl,index.php,index.xhtml,index.htm) found, and server-generated directory index forbidden by Options directive
I am stuck at that point ...
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
On 8/2/20 12:42 PM, Odhiambo Washington wrote:
It is currently linked from the first paragraph at <https://wiki.list.org/DOC/Mailman%203%20installation%20experience>.
I followed the steps outlined in the subject document and got mailman3 running. However, what is missing in that document is the process of setting up a webserver for accessing the MM3 UI. I have spent two days trying to figure out that aspect and discovered a few things (I could be wrong in what I think):
Which document are you talking about? If you mean <https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5PlantPTs/edit>, that talks about the Debian/Upuntu package installation and that package is quite behind the current releases.
I thought that after mush back and forth with you following <https://wiki.list.org/DOC/Mailman%203%20installation%20experience> you got Mailman 3 up and running, so why would you now be trying to install the Debian/Ubuntu package?
If you have issues with the <https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5PlantPTs/edit> document, you should contact its author. See <https://wiki.list.org/x/12812344>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Sun, 2 Aug 2020 at 23:56, Mark Sapiro <mark@msapiro.net> wrote:
On 8/2/20 12:42 PM, Odhiambo Washington wrote:
It is currently linked from the first paragraph at <https://wiki.list.org/DOC/Mailman%203%20installation%20experience>.
I followed the steps outlined in the subject document and got mailman3 running. However, what is missing in that document is the process of setting up a webserver for accessing the MM3 UI. I have spent two days trying to figure out that aspect and discovered a few things (I could be wrong in what I think):
,
Which document are you talking about? If you mean < https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plant... that talks about the Debian/Upuntu package installation and that package is quite behind the current releases.
That same document. The Ubuntu package is updated to the latest.
I thought that after mush back and forth with you following <https://wiki.list.org/DOC/Mailman%203%20installation%20experience> you got Mailman 3 up and running, so why would you now be trying to install the Debian/Ubuntu package?
I was trying to help the other poster :-)
If you have issues with the < https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plant...
document, you should contact its author. See <https://wiki.list.org/x/12812344>.
I just thought that since it was being discussed here (and because you linked it to your document), we could still discuss it here.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
participants (4)
-
joseverde＠gmail.com -
Mark Sapiro -
Odhiambo Washington -
Stephen J. Turnbull