<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Muchísimas gracias, Egoitz!</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">El 18/7/19 a las 11:12, Egoitz
Aurrekoetxea escribió:<br>
</div>
<blockquote type="cite"
cite="mid:8435EBDA-5314-43AE-A1FF-90F9616F364D@sarenet.es">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
Hi!!,
<div class=""><br class="">
</div>
<div class="">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 <a
href="https://wiki.davical.org/index.php/DAViCal-cli" class=""
moz-do-not-send="true">https://wiki.davical.org/index.php/DAViCal-cli</a>)
. We don’t refuse to use Caldav with Cyrus, it’s just we did the
system previous to Cyrus Caldav system.</div>
<div class=""><br class="">
</div>
<div class="">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 : <a
href="mailto:user_domain@recuperaciones.saremail.com" class=""
moz-do-not-send="true">user_domain@recuperaciones.saremail.com</a>.
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).</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">If you think it could be useful, perhaps could be
uploaded to contrib directory…</div>
<div class=""><br class="">
</div>
<div class="">Cheers!</div>
</blockquote>
<p><br>
</p>
<pre class="moz-signature" cols="72">--
Lic. Javier Charne
Responsable Infraestructura Tecnológica
Prosecretaría de TIC | UNNOBA
Junín, Buenos Aires, Argentina
<a class="moz-txt-link-abbreviated" href="mailto:javier@unnoba.edu.ar">javier@unnoba.edu.ar</a>
Tel: +54 (0236) 4407750 int 11712
Cel: +5492364542182</pre>
</body>
</html>