Idempotency

[johtso]

Hey, cool project!

While exploring different email providers, they all had the same issue. They didn't give you any way to avoid sending the same email more than once.

Sending email in an automated way without this assurance seems kind of reckless. A bug can easily result in you spamming your users.

I ended up having to implement some frankenstein DIY pseudo-idempotency on top of Postmark involving database locks and making API calls to check if emails have already been sent.

Is this something on the road map?

Hacker news discussion: https://news.ycombinator.com/item?id=41172351
Stripe idempotency: https://docs.stripe.com/api/idempotent_requests

[driaug]

This could be a good addition, I am leaving it open for now to gather some feedback from the community.

If there is demand for it, we can definitely implement it!

[killion]

I used Blueshift a few years ago. They had a way to set a limit per-contact on the number of emails you can send per day. It doesn't directly solve this issue, but may help.