Re: Migration Planning for Dovecot 2.3 to 2.4
John Stoffel via dovecot <[email protected]> Tue, 5 May 2026 14:20:24 -0400
| Newsgroups | gmane.mail.imap.dovecot |
|---|---|
| Message-ID | <[email protected]> |
>>>>> "Gregory" == Gregory Carter <[email protected]> writes: > Build a lab first, lots of things to consider: > 1) copy a mailbox from your existing production system and test it > against a client to insure it doesn't screw up peoples folder views. Done, playing with it now. > 2) Performance. Test various things, like indexing, download speed > and connection performance. Not as worried, it's a small personal system. > These are the two I will be raked over the coals with if I screw it up. > Users are such testy creatures. :-) Since I'm the main user... I get to beat myself up. So here's a question. The 2.3 to 2.4 converter suggests this small snippet of proposed configuration: mail_driver = maildir mail_path = /var/mail/%{user | domain}/%{user | username}/Maildir managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress compar protocols = imap lmtp sieve sieve_script personal { driver = file path = ~/sieve } Will the 'sieve_script personal { ... } ' block work ok with it's path being ~/ and will it inherit the mail_path defined farther up? Right now under 2.3 it creates the following: /var/mail/stoffel.org/john/sieve/ /var/mail/stoffel.org/john/Maildir/ directories, but I think I need to add in for 2.4 the following: mail_home = /var/mail%{user | domain}/%{user | username}/ And then the sieve_script_personal will work properly. Is this correct? And no, I haven't tried it yet, working on deploying my new test VM. Now my old system is configured to use sqlite3 as the backend mechanism, and I see that it does define the following queries: driver = sqlite password_query = SELECT email as user, password FROM virtual_users WHERE email='%u'; user_query = SELECT '/var/mail/%d/%n' as home, 'maildir:/var/mail/%d/%n/Maildir' as mail, 'mail' AS uid, 'mail' AS gid FROM virtual_users WHERE email = '%u'; iterate_query = SELECT email AS user from virtual_users; and I think the 'user_query' returning the 'home' value and the correct directory would do the right thing and mean I don't need to explicitly define mail_home. Is this true? Thanks, John _______________________________________________ dovecot mailing list -- [email protected] To unsubscribe send an email to [email protected]