What problem it solves

Organizations need to operate email and collaboration services across multiple client protocols while also addressing authentication, spam filtering, security, administration, and deployment requirements. The project aims to provide these capabilities in one server written in Rust and designed to be secure, robust, and scalable.

Key features

• Email Protocol Support — The email server supports JMAP, IMAP4, POP3, and SMTP, along with related extensions for message management, filtering, transport security, and delivery queues.

  Source: README

• Collaboration Services — The collaboration server provides calendaring, scheduling, contact management, and file storage through CalDAV, CardDAV, WebDAV, and corresponding JMAP support. It also includes sharing capabilities backed by fine-grained access controls.

  Source: README, crates/groupware

• Spam and Phishing Protection — Built-in filtering includes configurable rules, statistical and AI-based classifiers, DNS blocklists, phishing protection, sender reputation, greylisting, and spam traps. The project also supports collaborative digest-based filtering with Pyzor.

  Source: README, crates/spam-filter

• Encryption and Security — Mailbox encryption at rest, an outbound encryption gateway, and OpenPGP and S/MIME support are included. The server also provides automated TLS certificate provisioning, SSRF protection, rate limiting, and automated blocking of addresses that attack or scan it.

  Source: README

• Administration and Operations — A web-based dashboard supports account, domain, group, mailing list, queue, and configuration management. The project also provides logging, tracing, metrics, alerts, pluggable storage backends, full-text search, and multi-tenancy with domain and tenant isolation.

  Source: README

Who it may suit

Inference: may suit administrators and organizations seeking to deploy a unified mail and collaboration server, including self-hosted setups and multi-tenant hosting environments.

Topics to discuss

• Which storage backend and deployment model best fits different hosting scenarios?

• How should default roles and the new OAuth scopes be configured during upgrades?

• Which collaboration and security features should be prioritized for a community evaluation?

Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.

Read the original README https://github.com/stalwartlabs/stalwart#readme

ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.