| |
@@ -7,7 +7,7 @@
|
| |
Contact::
|
| |
#fedora-admin, sysadmin-main, sysadmin-tools, sysadmin-hosted
|
| |
Servers::
|
| |
- mailman01, mailman02, mailman01.stg
|
| |
+ mailman01, mailman01.stg
|
| |
Purpose::
|
| |
Provides mailing list services.
|
| |
|
| |
@@ -29,6 +29,54 @@
|
| |
(to avoid [no description available] on listinfo index)
|
| |
====
|
| |
|
| |
+ === Adding user as admin
|
| |
+
|
| |
+ . Log in to db01 server
|
| |
+ . Start the postgreSQL console
|
| |
+ +
|
| |
+ ``sudo -u postgres psql``
|
| |
+ +
|
| |
+ . Connect to hyperkitty DB
|
| |
+ +
|
| |
+ ``\connect hyperkitty``
|
| |
+ +
|
| |
+ . Add admin permissions to user
|
| |
+ ** By username
|
| |
+ +
|
| |
+ ``UPDATE auth_user SET is_staff = TRUE, is_superuser = TRUE WHERE username=<username>;``
|
| |
+ +
|
| |
+ ** By email (only primary mail is used)
|
| |
+ +
|
| |
+ ``UPDATE auth_user SET is_staff = TRUE, is_superuser = TRUE WHERE email=<email>;``
|
| |
+
|
| |
+
|
| |
+ === Accessing admin page in mailman
|
| |
+
|
| |
+ Admin page will allow you to change some of the settings that are not able to be changed
|
| |
+ anywhere else. The admin page could be accessed link:https://lists.fedoraproject.org/django-admin
|
| |
+ or link:https://lists.stg.fedoraproject.org/django-admin for staging.
|
| |
+
|
| |
+ [NOTE]
|
| |
+ ====
|
| |
+ You need to be added as admin to mailman to access the admin console.
|
| |
+ ====
|
| |
+
|
| |
+ == Deployment
|
| |
+
|
| |
+ In case of new deployment of mailman in infrastructure, there are few tasks
|
| |
+ that need to be done manually.
|
| |
+
|
| |
+ === Migrating social accounts from OpenID Fedora to OpenIDC
|
| |
+
|
| |
+ This needs to be done only once when you update from old OpenID Fedora auth provider
|
| |
+ to OpenIDC version. Doing this will correctly map the old accounts to new auth provider.
|
| |
+
|
| |
+ . Log into mailman01
|
| |
+ . ``cd /srv/webui/bin/``
|
| |
+ . ``python migrate_fedora_auth.py``
|
| |
+ +
|
| |
+ This script does nothing if the users were already migrated.
|
| |
+
|
| |
== Removing content from archives
|
| |
|
| |
We don't.
|
| |
@@ -85,13 +133,21 @@
|
| |
sudo -u mailman mailman3 members -R moderator example@example.com
|
| |
....
|
| |
|
| |
+ == How to delete a mailing list
|
| |
+
|
| |
+ Delete a list, but keep the archives:
|
| |
+
|
| |
+ ....
|
| |
+ sudo -u mailman mailman3 remove <listname>
|
| |
+ ....
|
| |
+
|
| |
== Troubleshooting and Resolution
|
| |
|
| |
=== List Administration
|
| |
|
| |
Specific users are marked as 'site admins' in the database.
|
| |
|
| |
- Please file a issue if you feel you need to have this access.
|
| |
+ Please file an issue if you feel you need to have this access.
|
| |
|
| |
=== Restart Procedure
|
| |
|
| |
@@ -99,14 +155,21 @@
|
| |
own. Otherwise each service on it can be restarted:
|
| |
|
| |
....
|
| |
- sudo service mailman3 restart
|
| |
- sudo service postfix restart
|
| |
+ systemctl restart mailman3
|
| |
+ systemctl restart postfix
|
| |
+ systemctl restart mailmanweb
|
| |
....
|
| |
|
| |
- == How to delete a mailing list
|
| |
+ === Log locations
|
| |
|
| |
- Delete a list, but keep the archives:
|
| |
+ Most of the logs are located in `/var/log/mailman3/`. In case you are looking for
|
| |
+ postfix logs, they could be found in `/var/log/maillog`.
|
| |
|
| |
- ....
|
| |
- sudo -u mailman mailman3 remove <listname>
|
| |
- ....
|
| |
+ === Known error messages
|
| |
+
|
| |
+ These are the error messages that are common in mailman3 logs:
|
| |
+
|
| |
+ * `NNTP error for list <listname>`
|
| |
+ +
|
| |
+ We don't have NNTP server and this couldn't be disabled in mailman3, so you
|
| |
+ can saw this error in logs, but it could be ignored.
|
| |
zlopez
commented a year ago
Signed-off-by: Michal Konecny mkonecny@redhat.com