Hello,
On 2015-03-12 12:19, Konstantin wrote:
We have users and domains with different retention policies.
The attached script was created to update retained field of old
messages.
We update field only for messages arrived before 2015.
After update `retained` field you can execute pilerpurge.
Janos,
Similar function available in webui. But it does not work.
It would be great if admin will be able to update `retained` field
from webui.
I think a well established retention policy is the answer, not
ad hoc fixes on the metadata table.
I suppose since execution time can pass for several hours then
retention update script need to be executed in background.
indeed, especially with a large installation. Anyway a well
written sql query may do the trick, however let me emphasize
that such an archive which is fixed all the time is less
credible.
Or this script can be included with piler installation like additional
tool.
I tell you that such modification attempts may work out, but I
don't encourage it, so I won't create such a tool, sorry.
2015-03-10 23:28 GMT+02:00 James Macdonell <[email protected]>:
When we receive a litigation hold, I’d to be able to identify
relevant messages already existing in the archive and exclude them
from periodic purging. Though, I’m not sure how to set that.
a little background on how piler purges aged messages.
By default the purge cron job is not installed (check crontab -l -u
piler,
and look for "purge"), so whatever retention is set it won't affect the
archive.
Let's say you have the following cron entry:
1 2 * * * /usr/local/libexec/piler/purge.sh
Now check the health page if it has the purging enabled. If not
then the archive is not affected, and pilerpurge quits without
removing actually a thing.
So whenever you have to maintain a litigation hold, simply disable
purging on the health page, and piler won't remove even aged messages.
When the hold is over, then enable it again, that's all.
However if the purge cron entry is present and purging is enabled
on the health page, then pilerpurge removes aged messages (and
related attachments).
I’m tempted to update the metadata.retained column, but the docs
state “retention period is included in the per message
verification digest, so the retention period should not be changed
after the message has been archived”
pilerpurge decides whether to remove the given message by checking
the retention column in the metadata table. This value is set at
archive time, and you should not fix it later, though you can, the
message verification (on the gui) won't tell it.
However, you are right that the retention value is used to compute
anothe checksum (vcode), but currently it's not used for verification.
Note that it may change in the future, especially with time stamping.
I’m also tempted to set a retention rule, but my impression from
the docs is that retention rules that only affect messages arriving
after the rule is implemented. I need to affect messages already in
the archive.
correct, a rule is effective on messages arriving after it's set.
Janos
