←back to thread

309 points StalwartLabs | 2 comments | | HN request time: 0.415s | source
Show context
matesz ◴[] No.45674066[source]
Running Stalwart in production for ~20 heavily used accounts for some company and no problems so far! The simplicity for such a complex stack and flexibility of deployments is off the charts!
replies(3): >>45674374 #>>45675950 #>>45678888 #
1. Bender ◴[] No.45675950[source]
Out of curiosity do you front-end SMTP with postfix to have many queues/MX entries and a battle hardened front-end or is Stalwart handling inbound connections directly? Im thinking of moving from Dovecot to Stalwart so family members have more modern features on my fallback domains about half of my domains do not use Fastmail. In multiple companies I had several Postfix inbound servers to keep the internet from touching Exchange directly and have multiple nodes for companies to quickly hand off to in multiple locations.
replies(1): >>45677798 #
2. matesz ◴[] No.45677798[source]
I just run single instance for now with RocksDB backend for internal / search and S3 for blobs - that is what made me think it’s so flexible.

Never hosted Postfix / Dovecot stack, in fact this is the first time I host emails, but from what I understand Stalwart is designed to handle inbound directly.

For very high throughput inbound you could check out KumaMTA - it was designed specifically for that, but I think Stalwart doesn’t have bottlenecks in it’s clustered topologies which would require it unless you are doing something crazy.

They have very good docs in general IMO, here are docs on how to cluster - https://stalw.art/docs/cluster/configuration