PostieDay 35 · 4 October 2026
Chapter 2 · 36 days to the chapter deadlineChapter 1 · The chapter deadline day
- First Chapter Done
It's been 35 days since I started Postie and I'm glad to say this little project built out of annoyance and spite has lasted more than most of my other projects. I am really motivated and equally energised about this, I really see potential in helping people have a better email experience.
We've done the following:
- Have the core mailbox experience completed with the ability to receive and send email reliably to people
- Created the structure for groups / shared inboxes and collaboration
- Implemented an automated setup / provisioning of Postie for incoming domains
- Created a robust framework for testing, iterating and developing Postie
- Created tenant-wide administration tools for management of accounts and email flow
While this is mostly corporate-speak it's true. That's the wild part. We've done so much in 35 days but there's still so much more to do! Having a deadline that I've had to push myself too was good initially because it forced me to get into the habit and push past the initial 2-week hurdle where most other projects fall by the wayside.
So what happens now? We continue. The first countdown is done, the first chapter complete. On to the next one. Chapter 2! While there is still a countdown active again for this chapter it's more a loose one. I'll still be working on this every day but I now don't feel pressured to prove (to myself more than anyone else) that this is serious. The structure and deadline of countdown still helps me focus though so that's why it stays.
I'll start showing off Postie in the next few days as promised. Just need to figure out how to do this properly in the CMS. Chapter 2... let's go!
- Improving Email Logs
I am consistently improving things, even to the extent that small changes don't normally warrant a post here. I think this one especially needs mention because i previously mentioned the need to log email most of all (more so than admin events at this time). However my initial implantation was not as thorough as I would like.
I am slightly hampered in the way that I'm integrating postie and the way that Cloudflare email sending requires me to have "connectors" in order to send email through. It's a logistical nightmare as it requires the customer (although automated) to provision a worker on their account. So effectively the "status updates" on whether a thing was sent or not hinge on that being truthful and up until now as I'm trying to implement it with a "reference connector" which is consistently changing as I'm updating it.
It's made me worried about the transmission of data into a Postie controlled server or whether things instead stay segmented so the connections themselves don't matter... what happens if someone changes their connector? How do I implement things without changing the core experience for normal people. Staging, feature flags.
A lot of things doing this email log have actually made me think more broadly about the architecture of this and if it is actually viable or scaleable. It shoudln't matter at this stage when I don't actually have any commercial users but at the same time I want to be set up for success.