Mailman 3 Service and Troubleshooting: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 19: | Line 19: | ||
mailman restart # stop and start mailman shorcut | mailman restart # stop and start mailman shorcut | ||
== | == Troubleshooting == | ||
Don't think you can start understand anything without at least doing the following: | Don't think you can start understand anything without at least doing the following: |
Revision as of 14:34, 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
Troubleshooting
Don't think you can start understand anything without at least doing the following:
- mailman core
tail -f /home/mailman/we.lurk.org/mm/var/logs/* tail -f /var/log/mail.err /var/log/mail.log /var/log/mail.warn journalctl --follow _SYSTEMD_UNIT=mailman3.service + _SYSTEMD_UNIT=mariadb.service
- web stuff
tail -f /home/mailman/we.lurk.org/web/logs/* tail -f /var/log/nginx/*log