On 2. Nov 2025, at 13.19, Gerhard Wiesinger via dovecot <[email protected]>
wrote:
>
> Hello,
>
> Regarding dovecot upgrade from 2.3.x to 2.4.x and mailbox_alias plugin:
> I've already converted my config and scripts but I'm still missing this
> config change:
> plugin {
> mailbox_alias_old = Spam
> mailbox_alias_new = Junk
> }
>
> I saw in the link
> https://doc.dovecot.org/2.4.0/installation/upgrade/2.3-to-2.4.html
> mailbox-alias plugin Depending on the use case, replacement may be the
> mailbox_special_use mailbox setting and/or Sieve filters.
>
> Any ideas what's the best alternative?
Why do you need/want the mailbox_alias plugin? There is no direct replacement.
But if you configure e.g.:
namespace inbox {
mailbox Junk {
special_use = \Junk
}
}
Then modern clients should use it. The worst part of mailbox_alias plugin was
that it caused the mailbox content to be duplicated on client side for both old
and new mailboxes.
> Another question, is the following correct:
> mail_home = /home/vmail/%n
> mail_location = maildir:~/Maildir
> =>
> mail_home = /home/vmail/%{user | username}
> mail_driver = maildir
> mail_path = ~/Maildir
This is the same as above.
> mail_inbox_path = ~/Maildir
This isn't harmful, but it doesn't do anything.
> (Especially mail_inbox_path, I don't have a ".INBOX" directory currently, I
> guess .INBOX is now default. How to deal with this?)
This I don't understand. It's not using .INBOX by default, and with or without
mail_inbox_path it's not using .INBOX (I just tested to be sure). If you see
.INBOX then I need to see the full doveconf output.
_______________________________________________
dovecot mailing list -- [email protected]
To unsubscribe send an email to [email protected]
