stalwart-proxyMulti-protocol e-mail migration proxy for Stalwart
1.0.5mailΣ=1 Package not present on quarterly.This port was created during this quarter. It will be in the next quarterly branch but not the current one.
Stalwart Proxy is a multi-protocol e-mail migration proxy. It sits in
front of one or more mail backends and decides, per account, which
backend a connection belongs to. It terminates IMAP, POP3, ManageSieve,
SMTP submission, SMTP/LMTP and HTTP (JMAP) sessions, identifies the
account from the credentials the client already presents, replays the
authentication to the assigned backend and bridges the session, so no
client reconfiguration is required.
It is intended for migrating from legacy servers such as Dovecot or
Cyrus to Stalwart one mailbox at a time, for migrating between Stalwart
versions, and as a cache-locality router in front of a Stalwart cluster.
Account mappings can be stored in a flat file, Redis, PostgreSQL, MySQL,
or SQLite. The proxy is written in Rust.
===> The following configuration options are available for stalwart-proxy-1.0.5:
EXAMPLES=on: Build and/or install examples
===> Use 'make config' to modify these settings
mail/stalwart-proxy: [NEW PORT] e-mail migration proxy for Stalwart
Stalwart Proxy is a multi-protocol e-mail migration proxy from the
Stalwart Labs team (the authors of mail/stalwart). It routes IMAP,
POP3, ManageSieve, SMTP submission, SMTP/LMTP and HTTP (JMAP) sessions
per account to the right backend, based on the credentials the client
already presents. It is meant for migrating from Dovecot, Cyrus or
older Stalwart versions to Stalwart one mailbox at a time.
PR: 300326
