>>>>> "byteme---" == byteme--- via dovecot <[email protected]> writes:
> Hello everyone,
> I have a Dovecot 2.3 installation on a Debian 12 Linux system that
> is being upgraded to Dovecot 2.4. The server hosts many domains with
> numerous email accounts. Users had created folder structures
> containing many received and sent emails, following the Maildir
> standard as "dot-prefixed folders."
Folowing up on this in backwards timeline because I've got the same
type of setup, though much smaller, so I'm interested in what the
solution will be.
My folder structure looks like this too:
/var/mail/<domain>/<user>/Maildir/.<folders>/
as well. You can probably guess my values here. LOL!
> When switching to Dovecot 2.4, all these emails and folders are no
> longer visible. This is what it looks like on the old system:
> root@mx1 /var/vmail/example.com/systemmails # ll -a
> insgesamt 256
> drwx------ 14 vmail vmail 4096 3. Nov 09:15 .
> drwx------ 15 vmail vmail 4096 6. Apr 2021 ..
> drwx------ 5 vmail vmail 4096 3. Nov 09:15 .Archive
> drwx------ 2 vmail vmail 86016 27. Okt 12:19 cur
> -rw------- 1 vmail vmail 0 15. Sep 2018 dovecot-acl-list
> -rw------- 1 vmail vmail 1080 29. Okt 06:50 dovecot.index
> -rw------- 1 vmail vmail 23400 30. Okt 01:36 dovecot.index.cache
> -rw------- 1 vmail vmail 10600 30. Okt 01:41 dovecot.index.log
> -rw------- 1 vmail vmail 6627 26. Aug 09:56 dovecot.index.thread
> -rw------- 1 vmail vmail 24 20. Apr 2024 dovecot-keywords
> -rw------- 1 vmail vmail 1256 3. Nov 09:05 dovecot.list.index
> -rw------- 1 vmail vmail 5156 3. Nov 09:15 dovecot.list.index.log
> -rw------- 1 vmail vmail 672 15. Jul 16:45 dovecot.mailbox.log
> -rw------- 1 vmail vmail 1781 30. Okt 01:36 dovecot-uidlist
> -rw------- 1 vmail vmail 8 15. Jul 16:45 dovecot-uidvalidity
> -r--r--r-- 1 vmail 1002 0 15. Sep 2018 dovecot-uidvalidity.5b9d20a3
> -r--r--r-- 1 vmail vmail 0 15. Sep 2018 dovecot-uidvalidity.5b9d20a5
> drwx------ 5 vmail vmail 4096 3. Nov 09:15 .Drafts
> drwx------ 5 vmail vmail 4096 3. Nov 09:15 .INBOX.Fail2ban
> drwx------ 5 vmail vmail 4096 3. Nov 09:15 .INBOX.vzdump
> drwx------ 5 vmail vmail 4096 3. Nov 09:15 .Junk
> drwx------ 2 vmail vmail 36864 30. Okt 01:36 new
> drwx------ 5 vmail vmail 4096 3. Nov 09:15 .Quarantine
> drwx------ 5 vmail vmail 4096 3. Nov 09:15 .Sent
> drwx------ 3 vmail vmail 4096 3. Dez 06:25 sieve
> -rw------- 1 vmail vmail 70 15. Jul 16:45 subscriptions
> drwx------ 2 vmail vmail 4096 2. Nov 16:41 tmp
> drwx------ 5 vmail vmail 4096 3. Nov 09:15 .Trash
I have in my setup the following in my 2.3 config:
mail_location = maildir:/var/mail/%d/%n/Maildir
while from your recent email I see you have:
mail_home = /var/vmail/%d/%n
mail_location = maildir:~/
Which implies to me that you don't push them down as far as I do into
the directory tree. But that all looks good to me.
> This should be preserved so that users don't notice the system
> upgrade. Dovecot 2.4 works quite differently in this regard. What
> solution is there for migrating both the namespace and the existing
> emails to Dovecot 2.4?
I've got a super simple namespace setup:
namespace inbox {
inbox = yes
location =
mailbox Drafts {
special_use = \Drafts
}
mailbox Junk {
autoexpunge = 10 days
special_use = \Junk
}
mailbox Sent {
special_use = \Sent
}
mailbox "Sent Messages" {
special_use = \Sent
}
mailbox Trash {
autoexpunge = 30 days
special_use = \Trash
}
prefix =
}
And I wonder if your 'seperator' entry in your inbox namespace when
translated to the 2.4 format is the problem?
Could it be your prefix definition in your new 2.4 config where you
have
prefix = .INBOX.
But I haven't had the time or energy to try and migrate my setup to
v2.4 as well either. Good luck!
John
_______________________________________________
dovecot mailing list -- [email protected]
To unsubscribe send an email to [email protected]
