Just to understand that correctly: I could setup a (cron) based process for doveadm sync, but no longer a setup like plugin { mail_replica = tcp:$IMAP_REPLICA_SERVER:$IMAP_REPLICA_PORT } where the cron would lead to some delay and would have to check for concurrent jobs?
You can also have that too.
doveadm sync -d
makes it use mail_replica setting.
@Aki:
Is it possible to monitor actions that would have triggered replication in dovecot < 2.4, e.g. parsing logs or a lua script to imitate the previous behaviour?
@Michael Slusarz:
While I understand it takes effort to maintain the replication plugin, this is especially problematic for small active/active high-availability deployments. I guess there are lots of servers that use replication for just 50 or 100 mailboxes. Cloudstorage (like S3) would be overkill for these.
Do you provide dovecot pro subscriptions for such small deployments?
The basic replication functionality with dsync seems to be available in future versions. Would you consider releasing a "dovecot smb" version for small/medium businesses that maintains the replication plugin (without director) for a yearly subscription fee? Otherwise those affected would have to look for alternatives. The recent release of rust-written Stalwart mailserver comes to mind, that bundles a lot of functionality (smtp, pop, imap, jmap, s3, sieve, dkim/arc/spf/dmarc, dane, mta-sas, ...): https://stalw.art/blog/
Best regards, Gerald