This PR now sends a separate message per recipient.
This was planned eventually - sending a separate email message per recipient, each with a separate download link. But that was for a different issue. I don't think we even have any issue filed for that yet on browser extension.
As for this issue as we are tackling now, I think we should still be sending single one message, and then make another API call that updates FES with regards to the message ID that it was sent with.
Originally posted by @tomholub in #4284 (comment)
This was planned eventually - sending a separate email message per recipient, each with a separate download link. But that was for a different issue. I don't think we even have any issue filed for that yet on browser extension.
As for this issue as we are tackling now, I think we should still be sending single one message, and then make another API call that updates FES with regards to the message ID that it was sent with.
Originally posted by @tomholub in #4284 (comment)