Re: What you do with old account
On Tue, 2020-06-09 at 15:51 +0200, Albert Shih wrote:> > After switching to cyrus imap, I think about how to do that. > If I'm correct I cannot just copy the file somewhere else, because cyrus > database would keep the information about the existance of the mailbox, so > what will the «state of the art» way to remove a mail account and all the > mail. > And how what would be the «state of the art» way to put it back ? I create a calendar event [task] to delete the mailbox and otherwise just leave it. If the account itself is disabled it cannot be accessed. Putting things back-into a mailstore is too much of a pain with current storage prices. -- Adam Tauno Williams, awill...@whitemice.org Multi-Modal Activists Against Auto Dependent Development resisting the unAmerican socialists of the Motorist hegemony http://www.mmaaadd.org Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Cyrus Murder Environment Upgrade
Wolfgang, I'm sure your help and experience with Cyrus Murder upgrading will save a lot of time and reduce the possibility of an eventual problem during the upgrade. Thankful -- Miguel Moreira DTE/SRE/GRE - Gerência de Redes +55(31)3339-1401 PRODEMGE - Companhia de Tecnologia da Informação do Estado de Minas Gerais Aviso: Esta mensagem é destinada exclusivamente para a(s) pessoa(s) a quem é dirigida, podendo conter informação sigilosa e legalmente protegida. O uso impróprio será tratado conforme as normas da empresa e a legislação em vigor. Caso não seja o destinatário, favor notificar o remetente, ficando proibidas a utilização, divulgação, cópia e distribuição. Em Terça, Junho 09, 2020 10:39 -03, Wolfgang Breyha escreveu:Hi! On 09/06/2020 14:56, Miguel Mucio Santos Moreira wrote: > Dear Wolfgang, > > Firstly thanks for your answer, secondly I have one more doubt, during this > time where the new Mupdate Master is receiving mailboxes information from > backend servers, is necessary stopping comunications between frontend > servers and mupdate master or none action is necessary besides that one > you've mentioned before? > We're concerned if frontend servers will connect to Mupdate Master and > receive from it an information which there's no mailboxes anymore until the > backend push entirely mailboxes information and this situation to cause any > trouble. I recommend the follow steps: *) check that your currently running setup has no conflicts in mailboxes.db by running "ctl_mboxlist -mw". It is possible that you see output if somebody changes his mailboxes while you run the command, but it should not appear again if you run the command a second time. If everything is fine... *) shut down all running cyrus frontends first, then backends and mupdate last *) backup your mailboxes.db on mupdate server *) replace/update mupdate and start it with empty/removed mailboxes.db. *) backup your mailboxes.db on the backends *) do the ctl_mboxlist -m by hand on the backends (only one at the same time) you can check if everything went ok with "-mw" at any time afterwards. *) start cyrus on backends In our setup the frontends have mupdate running as well. I can't currently remember if this is mandatory. If this is true in your setup then: *) remove or rename the mailboxes.db database on the frontends and start them. They will fetch the database immediately from the mupdate server. This is visible in syslog as well and takes about 30 seconds in our setup (~250MB mailboxes.db). otherwise *) start the frontends At this point everything should be up and running again. Watching syslog output all the time usually helps. IIRC we updated the mupdate server to 2.5 first. Then we had a mix of 2.4 and 2.5 backends for some time. The 2.5 backends had some capabilities suppressed. Frontends had 2.4 until all backends had 2.5. Last but not least we upgraded to 2.5 on the frontends. If you need more info/details feel free to ask. Greetings, Wolfgang -- Wolfgang Breyha | https://www.blafasel.at/ Vienna University Computer Center | Austria Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
What you do with old account
Hi I like to know what you do in time with the olds accounts. Long time ago (well 2 years) we using dovecot as imap server. And when some accounts are closed we create a archive of the person mailbox (with tar), put that in some backup server where the file going to stay about 2 years. After that the data are destroy The reason we keep that is some time (30% of the time) the person going to come back and event it's not mandatory for us, the person are very happy to go it old mailbox. After switching to cyrus imap, I think about how to do that. If I'm correct I cannot just copy the file somewhere else, because cyrus database would keep the information about the existance of the mailbox, so what will the «state of the art» way to remove a mail account and all the mail. And how what would be the «state of the art» way to put it back ? Regards. JAS -- Albert SHIH DIO bâtiment 15 Observatoire de Paris Heure local/Local time: Tue 09 Jun 2020 03:44:13 PM CEST Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Cyrus Murder Environment Upgrade
Hi! On 09/06/2020 14:56, Miguel Mucio Santos Moreira wrote: > Dear Wolfgang, > > Firstly thanks for your answer, secondly I have one more doubt, during this > time where the new Mupdate Master is receiving mailboxes information from > backend servers, is necessary stopping comunications between frontend > servers and mupdate master or none action is necessary besides that one > you've mentioned before? > We're concerned if frontend servers will connect to Mupdate Master and > receive from it an information which there's no mailboxes anymore until the > backend push entirely mailboxes information and this situation to cause any > trouble. I recommend the follow steps: *) check that your currently running setup has no conflicts in mailboxes.db by running "ctl_mboxlist -mw". It is possible that you see output if somebody changes his mailboxes while you run the command, but it should not appear again if you run the command a second time. If everything is fine... *) shut down all running cyrus frontends first, then backends and mupdate last *) backup your mailboxes.db on mupdate server *) replace/update mupdate and start it with empty/removed mailboxes.db. *) backup your mailboxes.db on the backends *) do the ctl_mboxlist -m by hand on the backends (only one at the same time) you can check if everything went ok with "-mw" at any time afterwards. *) start cyrus on backends In our setup the frontends have mupdate running as well. I can't currently remember if this is mandatory. If this is true in your setup then: *) remove or rename the mailboxes.db database on the frontends and start them. They will fetch the database immediately from the mupdate server. This is visible in syslog as well and takes about 30 seconds in our setup (~250MB mailboxes.db). otherwise *) start the frontends At this point everything should be up and running again. Watching syslog output all the time usually helps. IIRC we updated the mupdate server to 2.5 first. Then we had a mix of 2.4 and 2.5 backends for some time. The 2.5 backends had some capabilities suppressed. Frontends had 2.4 until all backends had 2.5. Last but not least we upgraded to 2.5 on the frontends. If you need more info/details feel free to ask. Greetings, Wolfgang -- Wolfgang Breyha | https://www.blafasel.at/ Vienna University Computer Center | Austria Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Cyrus Murder Environment Upgrade
Dear Wolfgang, Firstly thanks for your answer, secondly I have one more doubt, during this time where the new Mupdate Master is receiving mailboxes information from backend servers, is necessary stopping comunications between frontend servers and mupdate master or none action is necessary besides that one you've mentioned before? We're concerned if frontend servers will connect to Mupdate Master and receive from it an information which there's no mailboxes anymore until the backend push entirely mailboxes information and this situation to cause any trouble. One more time, thanks Cheers! -- Miguel Moreira DTE/SRE/GRE - Gerência de Redes +55(31)3339-1401 PRODEMGE - Companhia de Tecnologia da Informação do Estado de Minas Gerais Aviso: Esta mensagem é destinada exclusivamente para a(s) pessoa(s) a quem é dirigida, podendo conter informação sigilosa e legalmente protegida. O uso impróprio será tratado conforme as normas da empresa e a legislação em vigor. Caso não seja o destinatário, favor notificar o remetente, ficando proibidas a utilização, divulgação, cópia e distribuição. Em Terça, Junho 09, 2020 05:31 -03, Wolfgang Breyha escreveu:On 08/06/2020 17:37, Miguel Mucio Santos Moreira wrote: > Now we're in doubt about how is the best solution to replace the mupdate > master server for a new one. > Nowadays we have around 16K mailboxes. IIRC we simply replaced the mupdate server and did a "ctl_mboxlist -m" on all backends to fill it. Shouldn't take that long since we did it with 130k on 8 backends in under 20 minutes (or even shorter). Greetings, Wolfgang -- Wolfgang Breyha | https://www.blafasel.at/ Vienna University Computer Center | Austria Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Cyrus Murder Environment Upgrade
On 08/06/2020 17:37, Miguel Mucio Santos Moreira wrote: > Now we're in doubt about how is the best solution to replace the mupdate > master server for a new one. > Nowadays we have around 16K mailboxes. IIRC we simply replaced the mupdate server and did a "ctl_mboxlist -m" on all backends to fill it. Shouldn't take that long since we did it with 130k on 8 backends in under 20 minutes (or even shorter). Greetings, Wolfgang -- Wolfgang Breyha | https://www.blafasel.at/ Vienna University Computer Center | Austria Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
