Introducing Calendars, Contacts and Files in Stalwart | Stalwart Labs


Introducing Calendars, Contacts and Files in Stalwart |...
stalw.art/blog/collaboration/
in reply to jwr1

I had to give up on stalwart because on 4gb ram dual core with mechanical HDD the performance for a single account domain was abysmal and after some support back and forth there was no solution.

On the same hardware the good old postfix+dovecot just handles perfectly with 90% spare capacity

Sorry guys, maybe it was time to optimize it a bit before adding more features?

in reply to Shimitar

It's a 0.x release. It makes sense building the intended features first before optimizing heavily. There's no point having an optimized data structure that then falls flat once you need to add new features that brings new requirements to the data structure.

Once they label it 1.x (i.e. feature complete and production ready) I would expect it to be optimized. If it isn't, criticism is warranted.

in reply to jwr1

Being one of the few JMAP servers, adding these features is great although there's still some things yet to consider. The iCalendar standard also includes tasks and notes and Stalwart hasn't implemented those yet. Calendar scheduling is coming in the next few months, so that's good news.

I can't wait until service providers in privacy respecting countries start using complete solutions that enable users to really replace Google with a standards compliant alternative.

in reply to trewq

Yes. You can simply not expose SMTP at all and just use the IMAP/JMAP part. Unless you need also JMAP, I am not sure it brings you a lot to the table you wouldn't also get from a good old dovecot. IMO the big advantage of Stalwart is the all-in-one package it delivers plus the good defaults. It also shines when you want a multi node deployment. For a single node IMAP only it might not be the best choice, in my opinion. But it would work, if you want to.