GitHub - stalwartlabs/mail-server: Secure & Modern All-in-One Mail Server (IMAP, JMAP, SMTP)
github.com
Secure & Modern All-in-One Mail Server (IMAP, JMAP, SMTP) - GitHub - stalwartlabs/mail-server: Secure & Modern All-in-One Mail Server (IMAP, JMAP, SMTP)

Copied from r/selfhosted as seems interesting enough to share with wider audience.

I’m excited to announce the release of Stalwart Mail Server, a single binary solution that combines the Stalwart JMAP, Stalwart IMAP, and Stalwart SMTP servers into one easy-to-install package.

In response to user feedback, some key enhancements were made. Stalwart Mail Server now supports LDAP and SQL authentication, providing seamless integration with your existing infrastructure.

For single node setups, RocksDB has been replaced with SQLite with the option of using LiteStream for replication. For larger, distributed setups, support for FoundationDB was added, letting you scale to millions of users without sacrificing performance. Additionally, it is now also possible to store your emails in an S3-compatible storage solution such as MinIO, Amazon S3, or Google Cloud Storage.

Other notable updates include support for disk quota, subaddressing (or plus addressing) and catch-all addresses.

Check it out here: https://github.com/stalwartlabs/mail-server

I look forward to your feedback and questions!

    • Outcide@lemmy.worldOPEnglish
      61·
      1 year ago

      I think there’s a lot of FUD around this. Yes, deliverability can be a PITA, but with a clean IP and good setup it’s usually solvable. Worst case, you can pay a small amount to use a 3rd party SMTP relay and still get most of the benefits of selfhosting. It wasn’t deliverability that made me stop selfhosting it was spam, and it wasn’t that dealing with spam was that hard, it was just annoying.

      • mystik@lemmy.worldEnglish
        2·
        1 year ago

        As an anecdote – I have been sitting on an elastic IP at AWS for years, with reverse DNS configured properly for it. Way early on (years ago), some spam filters would block the whole netblock, but I can’t remember the last time the IP Block was wholesale blocked. I think AWS is very much on top of any spam complaints from their Elastic IPs, and as long as you don’t abuse your specific IP, you are in good shape for light volume, non-spam mail.

      • The Stoned Hacker@lemmy.worldEnglish
        1·
        1 year ago

        I use Mail-in-a-Box (planning to move to ISPMail though) and i rarely have deliverability issues. My main issue is actually that the grey filter takes too long for my preferences! With self hosting mail, i consider that a good issue to have

  • Agility0971@lemmy.worldEnglish
    41·
    1 year ago

    written in rust

    👀

    What the hell is JMAP anyway? Never heard of Another new alternative to IMAP. Can be read here.

    • Outcide@lemmy.worldOPEnglish
      2·
      1 year ago

      JMAP was developed by the guys that run FastMail (who are the primary developers of the open source email server Cyrus-IMAP). It’s easier to implement and more performant.

      Side note, Cyrus is a pretty amazing mail server. It doesn’t get much love here, but it’s bombproof, fast, supports multi-node clusters, IMAP, NNTP, CalDAV, CardDAV and more that I’m forgetting. It’s just a bit old school as far as configuring goes.

  • ananas@sopuli.xyzEnglish
    2·
    1 year ago

    I am placing careful (nevermind that, this seems very nice) interest in this.

    Few questions (since I’m on mobile, and it’ll take me a while to get back to my computer to find out for myself):

    • How does managing sieve work with this?
    • Does it play along with rspamd?
    • Is it tested on x64_64 only?
    • Does it support PGP, can email be encrypted-at-rest using this?
    • Is there a way to run this behind a reverse proxy that handles the certificates? I’m not too keen on dealing with two separate sets of those in separate places.
    • Does this require LDAP?

    If missing, are those on roadmap?

    • Outcide@lemmy.worldOPEnglish
      2·
      1 year ago

      The author is actively answering questions on the Reddit thread, probably best to ask them.

      It has sieve support and rspamd/spamd are supported via filters. It doesn’t require ldap. PGP doesn’t require any server support so that should work fine. I haven’t seen anything about supporting encryption at rest.

    • mystik@lemmy.worldEnglish
      2·
      1 year ago

      LMTP support would be nice too: existing mail routing infrastructure could send messages into stalwart-managed mailboxes. (Edit: reading the docs, they do support LMTP! This is awesome)

  • shadowbert@kbin.social
    2·
    1 year ago

    The single binary thing is a nice idea. I don’t see myself migrating off mailcow anytime soon though - I have no desire to set up mailservers more often than required.

  • cmeerw@programming.devEnglish
    1·
    1 year ago

    a single binary solution

    but that means that it’s not using any OS-level privilege separation?

    • mystik@lemmy.worldEnglish
      2·
      1 year ago

      A single binary can be invoked with different privilege levels. OpenSSH, for example is a single binary, but uses OS privilege separation when setting up connections from the root-owned daemon. (Just to be clear, I’m not sure that stalwart is using this technique, just that single binary apps do not exclude the possibility of OS privilege separation.)