Mailman 3 Service and Troubleshooting: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
== Service Configuration and Installation == | == Service Configuration and Installation == | ||
There are two services needed: | |||
systemctl status mailman3 # AKA mailman-core you only need this for lists to work | |||
systemctl status mailmanweb # AKA hyperkitty, postorius, uwsgi, django hell, needed for the web interface | |||
== Manual Start and Restart == | == Manual Start and Restart == |
Revision as of 14:24, 1 January 2024
Service Configuration and Installation
There are two services needed:
systemctl status mailman3 # AKA mailman-core you only need this for lists to work systemctl status mailmanweb # AKA hyperkitty, postorius, uwsgi, django hell, needed for the web interface
Manual Start and Restart
Only do this when manually troubleshooting otherwise this will conflict with systemctl
initiated services.
Basics
- Mailman 3 relies on its own mailman user to handle the processing of the emails.
su mailman # switch to the mailman user cd # make sure you cd to mailman's home !IMPORTANT
- You're now ready to control mailman
- Everything is handled with the mailman command line tool. Do not run these commands with another user!
mailman status # report on the service mailman start # start mailman mailman stop # stop mailman mailman restart # stop and start mailman shorcut
==