From the canned language doc we can built an email template according to the AR configuration:
Note: today we store the email templates in the source code as plain text files or as hard-coded strings to build the email body. We might want to consider storing this templates externally, an option might be using a dedicated synapse project and store the templates in files using the versioning mechanism. Another option could be to use wiki pages to allow more flexibility and editing. Yet another option might be to use mailchimp templates (need to check how those works). The advantage of storing them externally is that the interest parties might provide modifications without the direct involvement of an engineer (which would just need to validate the template variables and update the referenced version). We would still the templating engine we use today (velocity) to build the actual body of the email. This might go to a separate JIRA, for now we can use the current solution and store the template in the repository as the templates are not likely to change very often.
Will be part of the overall testing of reminders and revocations.