Hello Frank,
On 2013-04-01 22:29, Frank Ellebrecht wrote:
hmm, that's a surprise to me. In that case you shouldn't use the
pilerpurge
utility because it's based on a calculated timestamp when you receive
the message.
Yes, that's a tough one. You only know after the period if a message
can
be deleted. The only simplification I can think of is to add a tag to
the message, noting which year it belongs to. But that would have to
be
made manually. As an example: A message in 2012 regarding a contract
signed in 2013 would belong to the year 2013; the retention period
would
start on January, 1st 2014. It gets even more complicated when you
want
to know when the retention period is over. That depends on (too) many
things.
then I would recommend to set the retention time to 20 years or so.
Hopefully
it will be sufficient.
it may very well be 14 or 15 years. For this time I would have to
keep
the information about the processed messages, too.
ok, what about if I don't make a log purging utility?
Well, someday you for sure want to delete old log entries. But you'll
have at least some years for that feature to add. ;-)
:-)
just to clarify: you don't need to create log for archived messages
via
smtp, rather you want logging only for pilerimport processed
messages,
right?
Actually, I'm not sure. I would think that for archived message it
isn't
necessary to log the archive entry if they entered through SMTP. There
is one solution [1] that claims that *every* entry in the archive is
logged (it seems only to be mentioned in the German version of the web
site); there the log itself is secured by a hash sum.
ok, then what shall we log exactly?
I think it should be the date of piler's action, e.g. when the
decision
of (not) archiving a message was made.
ok
I guess you tried to contact some of them. Didn't they reveal any
detail on how (or to what extent) they comply?
To be honest, I didn't. Just came across the problem, looked for an
open
source solution and discarded everything that was built on top of
Tomcat
(because of system resources). And thought that everything would be up
and running after two or three hours. :-) Then I started reading,
looked
at computer and law journals, and ... well, here I am. I also took a
:-) you are not the first, who doesn't like java based solutions
look at some company's web sites, but there's only a lot of buzz words
about compliance and so on.
If you really want to make piler comply with the German law, I could
try
to compile a list of requirements by law and features that German
vendors offer. But you have been warned! ;-)
if you had some time, then I would appreciate it. Just to know what
piler
should match.
Janos
