With simple minimal config
dovecot_config_version = 2.4.2 dovecot_storage_version = 2.4.0 mail_driver = maildir mail_home = /home/vmail/%{user} mail_path = ~/mail passdb static { password = # hidden, use -P to show it }
doveadm mailbox create -u testuser foo.bar.baz
~# find /home/vmail/testuser/ /home/vmail/testuser/mail/tmp /home/vmail/testuser/mail/cur /home/vmail/testuser/mail/new /home/vmail/testuser/mail/.foo.bar.baz /home/vmail/testuser/mail/.foo.bar.baz/tmp /home/vmail/testuser/mail/.foo.bar.baz/new /home/vmail/testuser/mail/.foo.bar.baz/dovecot.index.log /home/vmail/testuser/mail/.foo.bar.baz/maildirfolder /home/vmail/testuser/mail/.foo.bar.baz/cur /home/vmail/testuser/mail/.foo.bar.baz/dovecot-uidlist
Does this suffice as evidence?
Aki
On 10/12/2025 12:34 EET byteme--- via dovecot <dovecot@dovecot.org> wrote:
You haven't provided a plausible solution to this claim yet. So, for me, it's just an unproven assertion! Okay?
Furthermore, you haven't provided a single working solution for our situation. If anything, we've only received brief statements, no explanation of why or how!
The fact is, it didn't work here! Therefore, "maildir++ style .foo.bar folders are totally still accepted by Dovecot 2.4" is an unproven and boastful claim. I've now found a solution.
Your complete upgrade from 2.3 to 2.4, which was supposed to run better than major release 3.0, is a disgrace in terms of implementation and, above all, documentation. Given these facts, I would suggest you be a bit more modest and at least say thank you for the external support.
These kinds of half-baked claims really make me angry!
ByteMe
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org