@@ -194,7 +194,7 @@ handles the CiviCRM bounces that way. Support for other bounces should
be added there as we can.
Special cases should be reported to the CiviCRM admin by forwarding
the email to the `Giving` queue in [RT](howto/rt).
the email to the `Giving` queue in [RT](service/rt).
Sometimes complaints come in about Mailman lists. Those are harder to
handle because they do not have individual bounce addresses...
...
...
@@ -381,7 +381,7 @@ backups, by TPA.
Full documentation on the installation of this system is somewhat out
of scope for TPA: sysadmins only installed the servers and setup basic
services like a VPN (using [IPsec](howto/ipsec)) and an Apache, PHP, MySQL
services like a VPN (using [IPsec](service/ipsec)) and an Apache, PHP, MySQL
stack.
The Puppet classes used on the CiviCRM server is `role::civicrm_int`. That
...
...
@@ -598,7 +598,7 @@ As other TPA servers, the CRM servers are monitored by
particularly monitored, using a `blackbox` check, to make sure both
ends can talk to each other.
There's also graphs rendered by [Grafana](howto/grafana). This includes an
There's also graphs rendered by [Grafana](service/grafana). This includes an
elaborate [Postfix dashboard](https://grafana.torproject.org/d/Ds5BxBYGk/postfix-mtail?orgId=1&from=now-24h&to=now&var-node=mx-dal-01.torproject.org&var-node=crm-int-01.torproject.org) watching to two mail servers.
We started working on [monitoring the CiviCRM health better](https://gitlab.torproject.org/tpo/web/civicrm/-/issues/78). So
