Email and opt-outs
Murmle sends email for one purpose: inviting people to a session, then reminding and following up. How a presenter sends them is covered in Invitations and reminders. This page is the administrator's view.
Sending is configured per deployment
The sending service and the sender address are set by the deployment's operator, for the whole deployment. A deployment can also be configured to send nothing at all, logging each message instead - useful for a test environment, so that it never emails real people.
Transactional and optional mail
| Message | Kind | Opt-out honoured |
|---|---|---|
| Invitation | Transactional - it carries the join link | No |
| Reminder | Optional | Yes |
| Follow-up | Optional | Yes |
An opt-out applies to the address across every workspace on the deployment. Suppressing an optional message never changes the recorded outcome of the invitation that came before it.
Templates
Any member who can present sessions (presenter, creator, admin, owner) can set the workspace's templates for each kind of message and language through the workspace API. See Languages and templates.
Addresses at rest
Invitation addresses are stored encrypted, alongside a one-way hash used to prevent duplicates and to look up opt-outs. They are never included in the workspace export, which shows only counts.
There is no link between an invitation and a participant. Murmle cannot tell which invited person joined or answered, in any privacy mode.
Delivery outcomes
Each send records whether the mail provider accepted the message, and its message when it did not. A bounce that arrives later from the receiving mail server is not reflected, and Murmle does not track whether messages are opened.