DeadmanDAO Mailman Attempt: Difference between revisions

From Traxel Wiki
Jump to navigation Jump to search
(Created page with " === install === <pre> sudo apt install mailman </pre> === init list === <pre> sudo newlist > roundtable </pre> It tells me that I should put the following in aliases: <p...")
 
No edit summary
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
AWS SES may be the solution: https://docs.aws.amazon.com/ses/latest/dg/lists-and-subscriptions.html
No, it doesn't have nearly the capabilities of a real mailing list system.
Mailchimp is out because it was bought for so much money that the money squeeze is going to be intense.
Other commercial providers are not significantly less risky than Mailchimp.
Mailman is robust once deployed and the initial build-out is not too painful.
= Earlier Attempts =
* [[MailingListDeadmanFirstPass]] (Deb 10, Mailman 3: installed Apache and Certbot before Mailman, which made it hard to deploy the Mailman web console)
* [[MailingListDeadmanSecondPass]] (Deb 10, Mailman 3: had trouble getting the Snap/PIP/VirtualEnv version of Mailman to let me in as an administrator)
* [[MailingListDeadmanThirdPass]] Deb 9, Mailman 2, had trouble getting the Mailman executables to execute as cgi's.
* [[MailingListDeadmanFourthPass]]: Deb 10, Mailman 2. Repeatedly failed sendmail test (as have/would the others, though I was inconsistently testing)
* [[MailingListDeadmanFifthPass]]: Frustrated. Using traxel.com's install of Mailman. Successful, if unsatisfying.
* Sixth Pass: Deb 10, two instances, more relaxed exploration now that the traxel list is working.
= Last (unsuccessful) Attempt =


=== install ===
=== install ===

Latest revision as of 20:48, 12 June 2022

AWS SES may be the solution: https://docs.aws.amazon.com/ses/latest/dg/lists-and-subscriptions.html

No, it doesn't have nearly the capabilities of a real mailing list system.

Mailchimp is out because it was bought for so much money that the money squeeze is going to be intense.

Other commercial providers are not significantly less risky than Mailchimp.

Mailman is robust once deployed and the initial build-out is not too painful.

Earlier Attempts

  • MailingListDeadmanFirstPass (Deb 10, Mailman 3: installed Apache and Certbot before Mailman, which made it hard to deploy the Mailman web console)
  • MailingListDeadmanSecondPass (Deb 10, Mailman 3: had trouble getting the Snap/PIP/VirtualEnv version of Mailman to let me in as an administrator)
  • MailingListDeadmanThirdPass Deb 9, Mailman 2, had trouble getting the Mailman executables to execute as cgi's.
  • MailingListDeadmanFourthPass: Deb 10, Mailman 2. Repeatedly failed sendmail test (as have/would the others, though I was inconsistently testing)
  • MailingListDeadmanFifthPass: Frustrated. Using traxel.com's install of Mailman. Successful, if unsatisfying.
  • Sixth Pass: Deb 10, two instances, more relaxed exploration now that the traxel list is working.

Last (unsuccessful) Attempt

install

sudo apt install mailman

init list

sudo newlist
> roundtable

It tells me that I should put the following in aliases:

## roundtable mailing list
roundtable:              "|/var/lib/mailman/mail/mailman post roundtable"
roundtable-admin:        "|/var/lib/mailman/mail/mailman admin roundtable"
roundtable-bounces:      "|/var/lib/mailman/mail/mailman bounces roundtable"
roundtable-confirm:      "|/var/lib/mailman/mail/mailman confirm roundtable"
roundtable-join:         "|/var/lib/mailman/mail/mailman join roundtable"
roundtable-leave:        "|/var/lib/mailman/mail/mailman leave roundtable"
roundtable-owner:        "|/var/lib/mailman/mail/mailman owner roundtable"
roundtable-request:      "|/var/lib/mailman/mail/mailman request roundtable"
roundtable-subscribe:    "|/var/lib/mailman/mail/mailman subscribe roundtable"
roundtable-unsubscribe:  "|/var/lib/mailman/mail/mailman unsubscribe roundtable"
Enter the name of the list: test
Enter the email of the person running the list: bob@traxel.com
Initial test password: 
To finish creating your mailing list, you must edit your /etc/aliases (or
equivalent) file by adding the following lines, and possibly running the
`newaliases' program:

## test mailing list
test:              "|/var/lib/mailman/mail/mailman post test"
test-admin:        "|/var/lib/mailman/mail/mailman admin test"
test-bounces:      "|/var/lib/mailman/mail/mailman bounces test"
test-confirm:      "|/var/lib/mailman/mail/mailman confirm test"
test-join:         "|/var/lib/mailman/mail/mailman join test"
test-leave:        "|/var/lib/mailman/mail/mailman leave test"
test-owner:        "|/var/lib/mailman/mail/mailman owner test"
test-request:      "|/var/lib/mailman/mail/mailman request test"
test-subscribe:    "|/var/lib/mailman/mail/mailman subscribe test"
test-unsubscribe:  "|/var/lib/mailman/mail/mailman unsubscribe test"

Version 2 Instructions for Mailman

Install PIP

sudo apt install python3-pip

Lots of dependencies

Side Note: Django Command Reference

Run the dev webserver

cd /path/to/project
sudo python manage.py runserver

Pull all the static files to a single location (for serving via Apache, for example)

python manage.py collectstatic

Install Mailman3 Full Suite

Lots of dependencies here.

sudo apt install mailman3-full

Webserver Install

sudo apt install apache2

Enable UWSGI, Link Mailman

Something Like

sudo apt install libapache2-mod-uwsgi
sudo a2enmod proxy_uwsgi
sudo ln -s /etc/mailman3/apache.conf /etc/apache2/sites-available/100-mailman.conf
sudo a2ensite 100-mailman
sudo service apache2 restart


Add TLS/SSL

https://certbot.eff.org/instructions?ws=apache&os=debianbuster

Add Snapd

sudo apt update
sudo apt install snapd
sudo snap install core
sudo snap refresh core

Snap Install Certbot

sudo snap install --classic certbot
sudo ln -s /snap/bin/certbot /usr/bin/certbot

Get a Cert for Apache

sudo certbot --apache -d deadmandao.com -d www.deadmandao.com

Verified to here.

Mailman Core Configuration

https://docs.mailman3.org/en/latest/config-core.html


Short Term Solution

Using interserver.systemicbias.com

Enter the name of the list: crypto
Enter the email of the person running the list: bob@traxel.com
Initial crypto password: 
To finish creating your mailing list, you must edit your /etc/aliases (or
equivalent) file by adding the following lines, and possibly running the
`newaliases' program:

## crypto mailing list
crypto:              "|/var/lib/mailman/mail/mailman post crypto"
crypto-admin:        "|/var/lib/mailman/mail/mailman admin crypto"
crypto-bounces:      "|/var/lib/mailman/mail/mailman bounces crypto"
crypto-confirm:      "|/var/lib/mailman/mail/mailman confirm crypto"
crypto-join:         "|/var/lib/mailman/mail/mailman join crypto"
crypto-leave:        "|/var/lib/mailman/mail/mailman leave crypto"
crypto-owner:        "|/var/lib/mailman/mail/mailman owner crypto"
crypto-request:      "|/var/lib/mailman/mail/mailman request crypto"
crypto-subscribe:    "|/var/lib/mailman/mail/mailman subscribe crypto"
crypto-unsubscribe:  "|/var/lib/mailman/mail/mailman unsubscribe crypto"