Hi everyone,
I’ve been working on a mail migration tool called MailSwiftSync, and I’m at the point where I’d really like some feedback from people who actually manage mail servers day to day.
A lot of it came from my own frustration with migrations being a mix of scripts, manual checks, logs, and trying to keep track of what has or hasn’t finished.
The idea behind MailSwiftSync is to make that process a little more controlled. It handles things like IMAP migrations, local Dovecot migrations, batch jobs, preflight checks, retries, verification, and keeping track of the migration state if something gets interrupted.
I’m not really looking for “looks good” feedback. I’d rather hear what’s wrong with it.
If you manage Virtualmin/Webmin, Dovecot, Postfix, or do mailbox migrations regularly, I’d be interested in things like:
-
What would you need to see before you’d trust something like this on a real server?
-
What are the biggest headaches you run into during mail migrations?
-
Are there any Virtualmin/Dovecot-specific features you’d expect it to have?
-
What checks should happen before a migration is allowed to start?
-
What information would actually be useful while a migration is running?
-
What would you want in a final verification/report?
-
Is anything about the workflow too complicated or just unnecessary?
It’s still under active development, so I’m trying to get this kind of feedback now rather than after everything is set in stone.
GitHub:
If anyone feels like trying it in a test environment, I’d also love to hear how it behaves with different Webmin/Virtualmin and Dovecot setups.
Thanks — and feel free to be critical. That’s honestly more useful to me right now.