|
 |
6a8fdd |
# Mailing Lists
|
|
|
6a8fdd |
|
|
|
6a8fdd |
The CentOS Project hosts some public mailing lists that people can subscribe to.
|
|
|
6a8fdd |
|
|
|
6a8fdd |
It's hosted at [https://lists.centos.org](https://lists.centos.org) and on a sponsored node.
|
|
|
6a8fdd |
|
|
|
6a8fdd |
Due to the fact that it was created (back in time decision) on the centos.org MX machine , the lists are using the `@centos.org` domain, and so mailman is hosted *on* the main centos [mailserver](/apps/mailservers/), reason why the postfix ansible role will have the `postfix_mailman` [variable boolean](https://github.com/CentOS/ansible-role-postfix/blob/master/defaults/main.yml#L80) set to `True`, as it will automatically create the `<list>@centos.org` aliases on the host (needed to pass through mailman)
|
|
|
6a8fdd |
|
|
|
6a8fdd |
Some links:
|
|
|
6a8fdd |
|
|
|
6a8fdd |
* [Upstream mailman 2](http://www.list.org/docs.html) documentation
|
|
|
6a8fdd |
* [mailman](https://github.com/centos/ansible-role-mailman) ansible role
|
|
|
6a8fdd |
|
|
|
6a8fdd |
Worth knowing that to initially fight against spam registration, we added a [recaptcha](https://github.com/CentOS/ansible-role-mailman/blob/master/defaults/main.yml#L24) option to filter massive users registration.
|
|
|
6a8fdd |
You can find the applied patches (collaboration between Red Hat, Gnome and CentOS, all using the same applied patch for their mailman2 lists) in the mailman role
|
|
|
6a8fdd |
|
|
|
6a8fdd |
The CentOS Theme (written by the Artwork SIG) is also pushed from ansible role and some elements can be modified through `mailman_html_tpl_{head,bodystart,bodyclose}` variables. (also all coming from the ansible mailman role
|
|
|
6a8fdd |
|
|
|
6a8fdd |
## Some operations
|
|
|
6a8fdd |
|
|
|
6a8fdd |
### Adding a new list for a project/SIG
|
|
|
6a8fdd |
|
|
|
6a8fdd |
The Ansible mailman role supports adding lists automatically so it's just a matter of , through ansible inventory, adding new list to the `mailman_lists` ansible list variable with some parameters like :
|
|
|
6a8fdd |
|
|
|
6a8fdd |
* name: the mailman list name
|
|
|
6a8fdd |
* description: list description appearing on mailman ui
|
|
|
6a8fdd |
* password: unique password for that list, as we can have specific operators for that list
|
|
|
6a8fdd |
* admin: the email address of the list owner
|
|
|
6a8fdd |
|
|
|
6a8fdd |
Once pushed to git and applied by ansible, the new list will appear
|
|
|
6a8fdd |
|
|
|
6a8fdd |
### Modifying lists settings
|
|
|
6a8fdd |
|
|
|
6a8fdd |
If the setting you want to modify is one of the previously mentioned variables, updating in git/ansible would then trigger a reconfig with these settings.
|
|
|
6a8fdd |
|
|
|
6a8fdd |
But some settings are just configured through mailman itself, so to modify these ones, you need either the `password` list (specific to that list), or the whole `mailman_admin_pass` (also called site password, that can be used to admin all lists)
|
|
|
6a8fdd |
|
|
|
6a8fdd |
To do this, just browse the [mailman admin UI](https://lists.centos.org/mailman/admin), select your list and auth with the needed password.
|
|
|
6a8fdd |
|
|
|
6a8fdd |
You can then proceed with changes like, adding/removing subscribers, work with moderation queue, etc, etc ..
|