Earlier quoted context omitted.
Sure, you might get kicked off a newsletter provider platform. It's a risk. But you have far far more options to take your subscriber list and go to a different provider (substack, tinyletter) or even build your own solution using something like mailgun or AWS SES. (Yes, that latter option would be quite a bit of work, but if you had, say, 20k email subscribers, it might be worth it.) If you get kicked off twitter or…
It took me about four hours to build an SES based mailing system. With dynamodb, lambda and the API gateway it is almost trivial. Put docker in the mix and it’s more like going to the moon.
* Email HTML is gnarly. Hope you like tables. The vast majority of web developers aren't equipped to write email HTML for something as simple as a button and have it render correctly in all email clients.
* Things get much more complicated when you need to email a large number of people (say 10s of thousands - very real for a lot of newsletters) and want to both personalize your content (e.g. add unsubscribe links) and not take 30 minutes to email all your subscribers.
* The metrics you get with SES are extremely barebones. Makes Sendgrid look incredible, and that's saying something. Deliverability and inboxing will be even more of a black box than usual.