Emails from Sydent should include headers that enable automated bounce and complaint handling about sydent

[reivilibre]

Alternatively at sending time, Sydent could store the context against message-id in the email and the API provides that message-id back

Assuming these headers can end up in someone's inbox, this would be much more preferable since otherwise you open yourself up to someone sending the API request themselves with someone else's MXID and attempting to deny them the ability to send e-mail invites. If the message ID is unpredictable then that closes this hole.

[benbz]

I had been wondering about the parameters just being a single base64 encoded blob that's signed by the IS's signing key to prevent modifications. However I don't super care about the implementation more that some functionality exists that can automatically handle these reports :)