Yes, you are right. The problems are not of technical nature. The reason
seems to be some sort of fear (and "admins").
We have all we need. We have the old dovecot config, we have the mdbox files
and the complete directory structure. We are simply not allowed to do all the
stuff on the live
mdbox is a proprietary format, only dovecot can handle it (afaik). Postfix can
write maildir natively, other MTAs, too. There are many tools to help in case
something strange happens. I believe that using maildir seems to be not that
bad. And I don't see the real benefits of mdbox. Maybe
Thank you.
Do you means two servers? One as source and one as destination? As I understood, destination does not need an imap server...
Description of dsync says: ... All of these can be used within the same server ...
Adapted it says:
mdbox -> maildir migration. Set
It was a decision we have not been involved in. That's it.
We have to do what we are paid for.
But I did not want to start a meta-discussion. I was looking for ideas and technical experience.
(And I agree with Justina that maildir seems to be much more manageable. It is a well-known
Hi!
We need to move all users from one (pretty old) installation of dovecot to a
new one.
The old one uses mdbox for users' mailboxes and maildir for shared/public
mailboxes.
The new one must be maildir only.
I believe that I can just copy the shared/public maildir structure to the new
Hi,
we have a very simple user-/passdb (like passwd) to authenticate virtual IMAP
users.
We also use this for Postfix authentication. Nothing special.
But, we need to exclude some of the users from IMAP login.
This means, some users should be allowed to send mail via Postfix (submission)
and
I have several mbox files (unstructured, only the big plain mbox files) and
I would like to integrate/read these mbox files into mdbox subfolders of
specific users. This is a production system and I don't want to disturb
running services and I am a bit afraid of not using the right
Hi!
I have several mbox files (unstructured, only the big plain mbox files) and I
would like to integrate/read these mbox files into mdbox subfolders of specific
users. This is a production system and I don't want to disturb running
services and I am a bit afraid of not using the right