A ti Javier :)
Egoitz Aurrekoetxea Dpto. de sistemas 944 209 470 Parque Tecnológico. Edificio 103 48170 Zamudio (Bizkaia) ego...@sarenet.es <mailto:undefined> www.sarenet.es <http://www.sarenet.es/> Antes de imprimir este correo electrónico piense si es necesario hacerlo. > El 18 jul 2019, a las 16:27, Infraestructura TIC - UNNOBA > <tecnolo...@unnoba.edu.ar> escribió: > > Muchísimas gracias, Egoitz! > > > El 18/7/19 a las 11:12, Egoitz Aurrekoetxea escribió: >> Hi!!, >> >> Fine! Very happy sharing then :) :) . It only handles email. For >> Calendars/Contacts we have been long time now, using Davical (to which we >> contributed in it’s day https://wiki.davical.org/index.php/DAViCal-cli >> <https://wiki.davical.org/index.php/DAViCal-cli>) . We don’t refuse to use >> Caldav with Cyrus, it’s just we did the system previous to Cyrus Caldav >> system. >> >> I attach the code in this email. I explain how we use it. We have each >> mailbox server running this code as a cron job and we have too some servers >> with Cyrus IMAP for just storing removed content (without the cron >> obviously). Each user in the restore server (a normal mailbox server but >> just for storing deleted content) is something like : >> user_dom...@recuperaciones.saremail.com >> <mailto:user_dom...@recuperaciones.saremail.com>. All our servers have >> autocreate feature (although in our mailbox servers is not being used >> nowadays). So, we keep track of what has been removed in a mailbox server >> with two elements… the Cyrus log and cyradm command. With cyradm command we >> keep track of deleted “folders" in each user account. With the log, we know >> where expunges had been run. Later, we take the DELETED mailboxes (the >> folders of each user) and upload them to Saremail-Restore. After that, we >> check the log (from some hours before till the present moment). Then we ask >> unexpunge to see what has been removed in each place. We upload them. We >> keep track in a database of what exactly has dealed with and what is >> remaining to deal with, so in the case a fail over to a slave is produced >> unexpunges can then be run there, even if there’s nothing in the logs that >> say that (because it’s obviously a slave). >> >> >> If you think it could be useful, perhaps could be uploaded to contrib >> directory… >> >> Cheers! > > -- > Lic. Javier Charne > Responsable Infraestructura Tecnológica > Prosecretaría de TIC | UNNOBA > Junín, Buenos Aires, Argentina > jav...@unnoba.edu.ar <mailto:jav...@unnoba.edu.ar> > Tel: +54 (0236) 4407750 int 11712 > Cel: +5492364542182 > ---- > 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
