Just announce my project #wormhole for #Dovecot on the dovecot users list:
https://dovecot.org/mailman3/archives/list/dovecot@dovecot.org/thread/YSLZ6T5S2YNH7TUT3BZHMRGXROQWCR3V/
Let's see if I get some feedback on it.
For more details about #wormhole see it's website on my homepage: https://people.mpi-klsb.mpg.de/~pcernko/wormhole.shtml
If you are creating a new #mailserver and you need to migrate mailbox files to mail directories. How would you do it?
We are using #dovecot on both machines and want to try to migrate to #mailcow.
what #disroot, #systemli, and #riseup did that made me build a similar collective. currently running some services under #openbsd from #indonesia:
but, i ponder what i must do to pass the #security and perfomance standard.
can someone answer my question? i appreciate it so much
If I could choose one piece of technology that never let me down, that'd be Dovecot.
Their replication works amazingly. As soon as a server gets back online, all e-mail is synchronized back from the backup MX.
That kind of peace of mind is priceless.
I really want to update a server to Debian 13 "trixie", but Dovecot was updated to a version with incompatible configuration format.
Weekend plans, I suppose...
I was expecting this page to tell me if #Dovecot was supported..
OK quick update from my life as a mail server #admin :)
Thanks to the very kind help from @yichalal we figured out that apparently my #Yunohost #Dovecot package is so broken that apt and dpkg fail to upgrade, --configure, even reinstall it.
Really strange and now I'm wondering if I need to rebuild the entire server just because this one single package is broken :(
I'll keep you posted and am open for any ideas ;)
Okay I've used up all other options, so now it's #FollowerPower and #FediMagic :
Would someone here be able to help me fix my broken #Yunohost instance? I've been without email for several weeks now
All apps and admin interface work without problems, but #Dovecot fails to start with a cryptic #SSL error. I've tried the forum of course but so far without success.
Happy to share logs and all. Thanks a million!
An update to @sacha 's gnus local imap pipeline config, due to dovecot 2.3 -> 2.4 breaking changes:
1. Note mail_location option split up. Specify all options like this:
(nnimap-shell-program "/usr/libexec/dovecot/imap -o mail_driver=maildir -o mail_path=$HOME/Maildir -o mail_inbox_path=$HOME/Maildir/INBOX -o mailbox_list_layout=fs")
Alternatively, put everything into system config.
2. System config must have these two lines:
dovecot_config_version = 2.4.1
dovecot_storage_version = 2.4.1
3. Official migration guides:
<https://doc.dovecot.org/2.4.1/installation/upgrade/2.3-to-2.4.html>
<https://doc.dovecot.org/2.4.1/installation/upgrade/2.4-to-2.4.x.html>
P.S.
Offtopic. Helpful resource on the upgrade: <https://willem.com/blog/2025-06-04_breaking-changes/>
Sample configs: <https://source.willem.com/dovecot-2.4-sample-config/>
@marcuwekling Großartige Idee! Ich bin (eh schon) dabei! #dutgemacht #ididit
Hier was ich derzeit schon so nutze:
- Eigener Mailserver #postfix #clamav #rspamd #roundcubemail #dovecot
- Notebooks auf #Linux
- #pfsense Firewall
- #thunderbird
Selber gehostete freie Dienste/Software derzeit:
- #Nextcloud
- #PaperlessNGX
- #Peertube
- #HomeAssistant
- #Mastodon
- #Matrix
- #Wordpress
Fremdgehostete freie Dienste:
- #pixelfed
- #bigbluebutton
- #letsencrypt
Leider kann ich meinen Windowsrechner noch nicht loswerden #gamer - aber das kommt bestimmt auch noch irgendwann...
because running a mail server wasn’t fun enough: the Dovecot 2.3 → 2.4 update has tons of breaking config changes
(h/t to https://willem.com/blog/2025-06-04_breaking-changes/ for the exhaustive breakdown of the changes)
That whole #dovecot breaking update (and from what I've seen the unreasonable pro version, at least for small setups) makes me question self-hosting my mail server…
I'm fine with investing time to setup something the first time - but updates (especially not minor) should never be breaking… - neither should they require quiet some time investment imho…
#SelfHosting #mailserver
@stefano would have happily paid a reasonable price for the commercial version of #dovecot, but the pricing is only targeted at large ISPs, so everyone with less than 10k mailboxes isn't interesting at all to them. I asked them a few months back just after the deletions happened in their repo. Didn't even ask about #freebsd support.
This is just after a reboot.
CPU: Intel Core 2 Quad Q9550 (4) @ 2.545GHz
Memory: 0.70GiB / 3.70GiB (18%)
Disk (/): 23G / 40G (61%)
It is running #Nextcloud, and so effectively does the cloud storage, calendar & contacts. I've been running this since before Nextcloud (I used to use OwnCloud).
This and SSH is all that is accessible outside of home. Both have MFA and China is currently blocked (I mean to expand this list).
However it also handles DHCP & DNS for the home LAN using #dnsmasq and I use it as an email archive (#dovecot). There is a functional #fetchmail install, but this is currently switched off.
It also has my #Subversion archive. That stays until I get around to having a proper look at #git.
With #USA going downhill I do have plans to get it do do more - but I'm playing with using #docker containers so if anything gets hacked, that will minimise the damage. I currently have too much running on the raw iron.
I'm using #borg for backups onto an external HDD that then occasionally is copied elsewhere (physical media off-site).
For anyone who just upgraded to #dovecot 2.4 (it's now in debian testing), the deliver command now doesn't work unless you specify -d <user> as well as -m <mailbox>
This bit me badly because I use procmail with deliver and it was simply throwing away all inbound email.
#Dovecot Does anyone know how I can use the #zlib plugin to compress my mail archive while transferring from another server? I tried to set it up, but the mail just comes over as-is. The docs suggest that it should convert with #dsync to compressed files. I seem to miss something. #help
https://doc.dovecot.org/2.3/configuration_manual/zlib_plugin/