| A/I Orange Book (1.0): An how-to for the realization of a resilient network of self-managed servers | ||
|---|---|---|
| Prev | Chapter 5. Mail Services | Next |
The mailing list software can be configured copying the configuration of all the lists on all of the server and setting up the appropriate aliases on each single server.
A major complicatoin is dued to the structure of Mailman that includes two agents modifying the list configuration: the client used by the MTA where the list alias is available and qrunner dealing with periodic tasks. Tie this two agents to the specific lists on a single box is not very complex but implies a very complex mechanism to replicate the configuration on the various boxes.
Even keeping the mailing list software on a single box implies the need to generate transport maps to forward the list traffic to the correct server: the following command should be enough to generate a appropriate map to be moved to the other servers' transport_maps
cat virtual-mailman | awk '/^[^#]/ {print $1 " relay:[test2-vpn]" }'