[mdlug] mailman on ubuntu

[admin at bclug.ca]

Ron / BCLUG wrote on 2024-04-28 08:20:

> Firing up Mailman3 adds 1000MB RAM consumed to that! For *mailing list* 
> software!

It was for this reason that I hesitated on putting mailman3 live.

Using most of my VPS for that one, rarely used, software package seems 
ridiculous.


Also, looking at how many processes are consumed by mailman3:

  └─» # ps -ef | grep venv | grep -v "grep" | wc -l
25

That's 25 processes running in a Python venv (excluding the grep 
itself). 25 Python interpreters in memory...


Also, mailman3 by default runs an nntp bridge - another Python 
interpreter. Useless waste of resources. That has been *disabled* on 
mine, so isn't counted in the 25 processes!



  └─» # ps -ef | grep mailman | grep -v "grep" | wc -l
39

And that's a count of how many processes are consumed by mailman in 
total, i.e. connections to PostgreSQL, Python interpreters, everything.



So, migration has paused, old VPS with invalid rDNS is still used for 
this account, and my email doesn't make it to the list unless I:

## Starting at home PC:
`ssh $user@$email_old`
`postqueue -p`
`postcat -hb $msg_id > mdlug.eml`
`postsuper -h -q $msg_id`
## Back at home PC
`rsync $user@$email_old:mdlug.eml .`
`rsync mdlug.eml $user@$email_new:/tmp/mdlug.eml`
`ssh $user@$email_new`
`sendmail mdlug at mdlug.org < /tmp/mdlug.eml`


What a headache (no fault of mdlug, of course).

rb