MailPace

Exciting news, we've rebranded! blog.mailpace.com/blog/ohmysmtp-…

mailpace.com/blog/guides/ho… #tailwindcss #alpinejs

Too few APIs offer an idempotency guarantee, especially so many years after @stripe led the way. In many cases this is really the only way to make it possible (and much easier) for your API users to build a robust integration that can handle common distributed systems edge cases, application bugs, and retries, all without accidentally generating duplicate work or costing additional money. When I was recently evaluating transactional email API providers for River’s customer billing service, I could only find *2* offerings with idempotent email send APIs: @MailPace and @UseWaypoint. None of the others made it easy to guarantee that my system didn’t accidentally generate duplicate onboarding or notification emails to spam my customers by mistake. Idempotency should be the default in modern APIs, not a rare exception! It’s a problem I’ve faced again and again when integrating with 3rd party APIs or even when sending events between internal systems. River offers built in unique job features to make it easy to implement this in your API, but there are many ways to build this kind of capability. Check out the blog post in the reply 🔗

Some SMTP and Inbound services experiencing some network issues over the last 10 minutes. Has been resolved but we are keeping a close eye on it.

Our upstream cloud provider are currently experiencing a network outage that is affecting deliveries

I'm launching a new Monthly Mailing List for @MailPace, Awesome Email, filled with developer-focused content on email, as well as the latest mailpace product updates, sign up here: buttondown.email/mailpace

We just updated our HTML email templates to @maizzlejs 4 and @tailwindcss 3! github.com/mailpace/templ…

It was a bug with our upstream provider and cloudflare, which sent SSL requests into an infinite loop

Should be fixed now… famous last words

We are having ongoing network connectivity issues. Bear with us while we investigate and resolve

Back online now.

Our upstream hosting provider is having issues tonight, apologies

@goodenoughllc @bjhess Just published here: blog.mailpace.com/blog/postgres-…

@goodenoughllc @bjhess Yes absolutely, we’re working through the root cause(s) and will write a post-mortem on the blog when complete It was caused by a nightly clean up job failing silently for a few weeks, and when we added more memory it ran and exhausted the entire db hdd space available

We have an ongoing issue right now with our main API. We are investigating and will update shortly

@GazBuilds Hi - sign up for an account and email us at support@mailpace.com, and we'll be happy to help :)

@MailPace 🙁

@MailPace 👋 - how can I trial your product? (I would sign up for your solo plan if it wasn't billed annually)