This is actually a very good question.
The English version of the Data Protection Act requires that systems
are registered that they contain personal data. However, what
"personal" data would be registered by an ASSP system? An email
address? Questionalbly personal. An IP address? Again, I wouldn't say
this was personal...
But, in either case, (as far as my memory of the UK DPA goes), as long
as the system is registered, it can store whatever data you want. You
must be ready to provide users with any personal data you may have
stored on your server if/when the user requests it.
Taking it a stage further, if the German equivilent if RIPN couldn't
store the IP addresses/user details of IP's allocated, then "whois"
would cease to work in Germany.
Steve
Sent from my iPhone
On 29.12.2009, at 10:24, "Thomas Eckardt/eck" <Thomas.Eckardt@...
> wrote:
> Philipp,
>
> frist - changing the IP's in the log will break many features in ASSP.
>
>> At least in germany it's not allowed to save personal data
>
> This is not absolute correct. You are allowed to store personal data
> as
> long as you need them to do your business (deliver mails) and you
> have to
> delete them if no more needed. eg. Every mail header contains all
> hop-IP's
> - and nobody is allowed to delete them (RFC). This is the same like
> if the
> Post/DHL ... is delivering a packet. They store your personal data for
> revision purposes even if they have delivered the packet. Or: all
> german
> ISP's storing personal mails for there customers (containing all
> data) on
> there server (for there business).
>
> I don't know any mailserver, that is not writing log files, which
> contains
> email addresses and/or IP's. So it should be not allowed to use any
> mail
> server in germany!?
> ASSP stores IP's and email addresses to do it's (your) business (spam
> detection). If configured, all uneeded data (logs and email files) are
> deleted after some time (the time you need them to do your business).
>
> The document in your link belongs to ISP - dynamic IP's (and IP's on
> webpages) - which are no longer allowed to store. I think this does
> not
> belong to email delivery.
>
> But how ever - if you think you have to do it, add the following
> line to
> sub mlog (found at the end of the sub)
>
> $m =~ s/(\d+\.\d+)\.\d+\.\d+/$1.0.0/g; # <-- add this line
> threads->yield();
> $mlogQueue->enqueue("$m");
>
> don't forget to disable griplist, griplistupload and heloblack -
> they are
> build form the logfiles and will contain wrong data.
>
> Thomas
>
>
>
>
> Philipp Niethammer <webmaster@...>
> 28.12.2009 23:55
> Bitte antworten an
> ASSP development mailing list <assp-test@...>
>
>
> An
> Assp-test@...
> Kopie
>
> Thema
> [Assp-test] Anonymisation of IPs in logfiles
>
>
>
>
>
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi there,
>
> At least in germany it's not allowed to save personal data [1]. Thus
> we
> are in
> the progress to make all our log files anonymous. In fact that means
> that
> we
> have to delete the last two bytes of IPs before writing them to the
> disk
> (i.e.
> 123.45.0.0 instead of 123.45.67.89).
>
> Is there a way to do this for ASSP? May be it's worth a feature
> request?
> Or is
> there any other way you can think of?
>
> We're using the newest 2.0.1*
>
> Thanks for helping and for your great work!
>
> Regards,
> Philipp
>
> [1]
> http://www.daten-speicherung.de/index.php/speicherung-von-ip-adressen-ist-
> unzulaessig-auch-auf-websites/
>
> - --
> Philipp Niethammer nochwer.de
> Birkenwaldstr. 204 guite.de
> D-70191 Stuttgart
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAks5MuoACgkQOw1zFs7lUln+xwCeMsgBC0ypckrkSAmSF+tFW7hT
> FtAAn1Xmtm0Jx5V9zVQCc58aFCPHukNX
> =ESnX
> -----END PGP SIGNATURE-----
>
> ---
> ---
> ---
> ---------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast
> and
> easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev
> _______________________________________________
> Assp-test mailing list
> Assp-test@...
> https://lists.sourceforge.net/lists/listinfo/assp-test
>
>
>
>
> DISCLAIMER:
> *******************************************************
> This email and any files transmitted with it may be confidential,
> legally
> privileged and protected in law and are intended solely for the use
> of the
>
> individual to whom it is addressed.
> This email was multiple times scanned for viruses. There should be no
> known virus in this email!
> *******************************************************
>
>
> ---
> ---
> ---
> ---------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast
> and easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev
> _______________________________________________
> Assp-test mailing list
> Assp-test@...
> https://lists.sourceforge.net/lists/listinfo/assp-test
|