parsemail VS python-ksuid

It's a pain in the ass right now. Original I come up with the domain hanami.run because I explained here https://www.youtube.com/watch?v=O1p2crPpFIc I feel like wind blow flowers where Hanami blow out emails.

I run an email forwarding services (https://hanami.run if you want to check it out) and I can share some info:

I found https://hanami.run (soon to be mailwip.com due to name conflict with hanamirb.org) to setup email forwarding and a simple blog platform by "email to post" and webhook.

Use it you can consolidate emails from multiple domains to forward to the same inbox. And you can add webhook/slack notification too.

You can look into mine (https://hanami.run) very fast to sign up and have a few cool features about webhook or smtp.

Also, improvmx.com is a great product as well.

If you like open source, https://maddy.email/ is a single binary deployment that can handle everything even IMAP.

https://mailcow.github.io/mailcow-dockerized-docs/ is a dockerize solution with super detail document as well.

If you want to compete with the big players, you have to solve the most important pain point and work upward from that small use base.

My case: I work on https://hanami.run (will soon move to https://mailwip.com due to hanamirb.org conflict) and email forwarding is very competitive. Big and old players are all over the place because at the end of day, setting up email forwarding isn't hard and many open source project did it, heck you can spin up AWS lambda for incoming email in no time.

The pain point is: email will drop sometime, time to time no matter how good an email forwarding service is because they have to scan spam, have false positive, or because of strict DMARC/SPF rule. And I have no tools available to help me out there. So I focus strongly on my maillog features with many level of privacy:

- no log at all

- docker-compose to spin up everything. It's super nice. Again, the deployment is done with a `rsync` then `docker-compose up -f docker-compose-prod.yml`

Eventually when deployment changes very frequent and need scale/ha I added in Kubernetes. K8S is way easiser to setup than you think and it handle all other suff(load balancer, environment variable etc).

And my deploy now become: `kubectl apply -f`

One trick I used is to use `sed` or `envsubst` to replace the image hash.

For backedup, I again, literally setup cronjob from an external server, `ssh` into database and run `pgdump`.

I also have a nice NFS server to centralize config and sync back to our git repo.

I used this whole setup to operate https://hanami.run an email forwarding service for the first 3 months before I added Kubernetes.

So I want to share a story about user asking for a feature then not using it.

I run an email forwarding services(https://hanami.run) basically you add your domains in and add some records.

We had this one heavy users who has like hundreds of domains. So our UI isn't design for that. Who has hundreds of domains? So they approach and asked us for a way to organize those domains into a hierarchy structure.

All good.

They are paid our highest tier ($30 per month) so we prioritize the requests and work on it.

2 days later that same user downgrade to the lowest plan and delete all of their hundred of domains...

That complicated features remain unused to nowadays...

I used hanami.run and they support that. A catch-all then an explicitly deny rule to disable certain address.

Wix doesn't have built-in email forwarding but you can use any email forwarding service. Look into hanami.run and simply follow their onboarding process to add your MX record. https://hanami.run/docs/configure_dns#mx

Homepage: https://www.svix.com

It's really fast, it makes writing secure and correct code easier, it's easier to deploy and distribute (one static binary), and it's a lot more fun. :)

Webhooks are really cool, and I absolutely love what they enable. They make the web compose-able, interconnected, and enable people to automate a lot of their work! Our goal is to make them easy, reliable, and consistent, so that more services offer them and they are easier to consume.

I'd love to hear your feedback! We've incorporated most of the comments we got the last time[0] (thanks again everyone!), and we would love to know how we can improve the product further. Got any suggestions?

Homepage: https://www.svix.com

Repo: https://github.com/svix/svix-webhooks/

Docs: https://docs.svix.com/

API reference: https://api.svix.com/

[0] https://news.ycombinator.com/item?id=26399672

I wasn't going to post it here because it feels a bit small for a show HN, but then I figured: why not. :)

It's a pure Rust implementation of Segement's KSUID, and I created this library while working on Svix[0].

I haven't written any Rust for a while, so even though I have written quite a bit of Rust code in the past (see Etebase[1]), I'm a bit rusty (no pun intended).

Anyhow, I just wanted to share, and I'm hoping to get some feedback if you have any. :)

Code and examples: https://github.com/svix/rust-ksuid/

P.S, the package is tested for compatibility against the reference Go implementation.

[0] https://www.svix.com

I created this library while working on Svix. We have a highly scalable and distributed environment there, which is where KSUIDs really shine.

These reasons are exactly why we started Svix[1] (we do webhooks as a service). I wish we existed to serve you guys back when you started working on it. :)

[1] https://www.svix.com

Hey everyone, my name is Tom, and I'm the founder of Svix (https://www.svix.com) - previously known as Diahook. Svix makes it easy for developers to send webhooks from their service using a simple API. Think Twilio or SendGrid but for webhooks.

Webhooks are how servers notify each other of events, so they are a key component of many APIs such as Stripe, Shopify, Slack, Dropbox and Github.

Code and examples: https://github.com/svixhq/python-ksuid/