Carol Tardif wrote:
[...]
One thing I would like to know is instead of synchronising everything can I:
1- delete mailboxe.db on mupdate.
2- do "ctl_mboxlist -d -f /var/imap/mailboxes.db > mailbox_backend1.txt"
on both backends
3- Then on the mupdate import mailbox via: ctl_mboxlist -u -f /var/imap/mailboxes.db < mailbox_backend1.txt ctl_mboxlist -u -f /var/imap/mailboxes.db < mailbox_backend2.txt
Is this gonna work? Or I am forced to have a big downtime waiting for "ctl_mboxlist -m"
on both backends.
Unfortunately it wont work and according to the devs, it should never work that way, because this way you could potentially create inconsistencies on the master server.
Fortunately there is a patch that add this capacity to ctl_mboxlist, you can find it here:
http://asg.web.cmu.edu/archive/message.php?mailbox=archive.cyrus-devel&searchterm=ctl_mboxlist&msg=905
But as I mentioned above, you can easily end up with an inconsistent mailbox list on your master server.
One more thing on my frontends I have lines like this:
May 19 15:30:41 frontend3 imap[11454]: kick_mupdate: can't connect to target: Connection refused
May 19 15:30:41 frontend3 mupdate[1503]: accepted connection
May 19 15:31:19 frontend3 imaps[11783]: kick_mupdate: can't connect to target: Connection refused
It's because your master mailboxes.db is corrupted. The master server will behave crazy.
--
-------------------------------- - Jo�o Assad - ParPerfeito Comunica��o LTDA - http://www.parperfeito.com.br/
--- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
