By the way, for your case I would recommend doing a script that does a get from dovecot and a put to Cyrus instead of copying Sieve files directly… it’s a much more cleaner way…
Cheers! Egoitz Aurrekoetxea Dpto. de sistemas 944 209 470 Parque Tecnológico. Edificio 103 48170 Zamudio (Bizkaia) ego...@sarenet.es <mailto:ego...@sarenet.es> www.sarenet.es <http://www.sarenet.es/> Antes de imprimir este correo electrónico piense si es necesario hacerlo. > El 9 jul 2019, a las 22:44, Egoitz Aurrekoetxea <ego...@sarenet.es> escribió: > > Hi Albert, > > If instead of -A you used -u for each of your users did it worked? Or did it > crashed in the same user as with -A?. Which Cyrus version were you running?. > > Cheers, > > > > Egoitz Aurrekoetxea > Dpto. de sistemas > 944 209 470 > Parque Tecnológico. Edificio 103 > 48170 Zamudio (Bizkaia) > ego...@sarenet.es <mailto:ego...@sarenet.es> > www.sarenet.es <http://www.sarenet.es/> > Antes de imprimir este correo electrónico piense si es necesario hacerlo. > >> El 9 jul 2019, a las 15:03, Albert Shih <albert.s...@obspm.fr >> <mailto:albert.s...@obspm.fr>> escribió: >> >> Le 09/07/2019 à 14:10:49+0200, Egoitz Aurrekoetxea a écrit >>> Good morning, >>> >>> >>> After we upgraded to Cyrus 3.0.8, we saw that some users in the replicas >>> didn't >>> have some folders (or all) subscribed the same way they had in previous env >>> in >>> Cyrus 2.3. Same happened for some users with Sieve scripts. It seemed the >>> content itself was perfectly copied. It was like, if the copy between >>> versions >>> would not had fully succeed. We fixed it easily by creating some scripts for >>> checking folder subscriptions and Sieve scripts existence. We though it >>> could >>> perhaps had something to do with some issue replicating folders >>> subscriptions >>> and sieve scripts from 2.3 to 3.0.8. After that, as we fixed it easily and >>> was >>> nothing related to content, we just didn’t go in deep in this topic. >> >> After my transfering all mail from my old server (dovecot) to the new one >> (under >> cyrus), I try to initialize the sync, so I launch the synchronization, and >> find out everytime the user got a sieve, the sync processus crash, >> but....event the >> it crash it still create « something », so the next time I launch the sync >> it pass (and email a actually synchronize). So for the first synchro I >> juste launch a infinite loop in bash to synchronize all user. >> >> I known it's not a very satisfying method but it work. >> >> With new user I don't have any problem. >> >> I already send a email here but don't get any solution >> >> https://lists.andrew.cmu.edu/pipermail/info-cyrus/2018-May/040186.html >> <https://lists.andrew.cmu.edu/pipermail/info-cyrus/2018-May/040186.html> >> >> Don't know if that help >> >> Regards >> -- >> Albert SHIH >> DIO bâtiment 15 >> Observatoire de Paris >> 5 Place Jules Janssen >> 92195 Meudon Cedex >> France >> xmpp: j...@obspm.fr <mailto:j...@obspm.fr> >> Heure local/Local time: >> Tue 09 Jul 2019 02:57:46 PM CEST >> ---- >> Cyrus Home Page: http://www.cyrusimap.org/ <http://www.cyrusimap.org/> >> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ >> <http://lists.andrew.cmu.edu/pipermail/info-cyrus/> >> To Unsubscribe: >> https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus >> <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
