document how to test the bridgedb service from the outside
as TPA, we sometimes have to look into this service and try to figure out "hey, did we break anything here?"
in our service list for bridgedb, there's a link to the bridgedb survival guide as the documentation portal. because that page doesn't follow the service template, it doesn't have a "monitoring and testing" which should document:
<!-- describe how this service is monitored and how it can be tested -->
<!-- after major changes like IP address changes or upgrades. describe -->
<!-- CI, test suites, linting, how security issues and upgrades are -->
<!-- tracked -->
typically, I try to test the service with this command:
mail -s test -r anarcat@example.com -- bridges@bridges-test.torproject.org < /dev/null
... if i want to relay to my local DKIM-signing. if i just want to send mail directly, i have also tried:
swaks -t bridges@bridges-test.torproject.org -s bridges.torproject.org -f anarcat@torproject.org
so it would be great to have that documented somewhere.