Archanian

Great question! We achieve this by using a top-level grouping mechanism for all mail sent through Helo (called "Channels"). Every message sent must be associated with a Channel, and this is typically how you would organise your tenants (one per Channel).

This allows us to track deliverability signals separately for each tenant, regardless of the sending domain they happen to be using. When we see signs of suspicious behaviour or poor sending practices (ie. bounces, spam complaints), we can pause sending for individual tenants before they cause problems for the entire set of senders using that domain (and the platform as a whole).

> Above all, what’s dangerous about JavaScript is that it is executed without the user’s knowledge or consent.

Ummm ... is this not how all software works? Is the average person 'aware' of the code that is executing as he/she clicks around in any piece of software? How is a web browser any different?

You should probably remove "Event Sourcing" from the description ... CQRS has nothing to do with Event Sourcing (even though they are often used in conjunction with each other), nor does your library from what I can tell.