* Case Number: a20150313.1 * Status: init * Claimant: Werner D for Support * Respondent: CAcert * initial Case Manager: EvaStöwe * Case Manager: name case manager * Arbitrator: name arbitrator * Date of arbitration start: 201Y-MM-DD * Date of ruling: 201Y-MM-DD * Case closed: 201Y-MM-DD * Complaint: primary Email address does not exist * Relief: TBD Before: Arbitrator name arbitrator (A), Respondent: CAcert (R), Claimant: Werner D for Support (C), Case: a20150313.1 <> == History Log == . 2015-03-13 (issue.c.o): case [s20150313.93] . 2015-03-18 (iCM): added to wiki, request for CM / A . 2015-03-18 (iCM): notification send to C - no direct R identified, yet == Private Part == * '''Link to Arbitration case [[Arbitrations/priv/a20150313.1|a20150313.1 (Private Part)]], Access for (CM) + (A) only''' ## ==> INCLUDE SECTION BOT <> ## <== INCLUDE SECTION EOT ==== EOT Private Part ==== == Original Dispute == {{{ Dear Arbitrators, please give us the guideline how to proceed in this case: The user created the account on [a date] with accepting the latest CCA, he created a client certificate on the same day. The account shows one email address, one domain, one client certificate expiring [6 month later], no received or given Assurances. Now he got the reminder mail that the certificate is expiring in [some] days. Support received a return mail with the quote the email address no longer exists. Support tried a again with the same result. As this is a clear violation of the CCA to keep the primary email address in good working order (3.5) support suggests the following procedure: Support locks the account and revokes the certificate immediatly. After the retention time of 3 month after the expiration/revocation of the certificate the account should be anonymised in the following way: The user data is anonymised the same way as it is done in the delete account precedent way BUT opposed to the normal procedure the primary email address and the domain should be kept in the account to prevent that the email address and domain can be used again without CAcert getting notice of it. Support hopes that a first ruling about the locking and revoke of the certificate is given in a short timespan as we see the urgency for the community to rely on correct data in the user account and of users following the CCA. The second part of the ruling about the further handling of the account does not need to be handled shortly. Please think about making a precedent ruling from this case. }}} parts in [] anonymised by iCM (can be added by CM or A again, if needed) ## You may remove unneeded sections at your discretion... == Discovery == == Elaboration == == Ruling == == Execution == == Similiar Cases == to be identified ## || [[Arbitrations/a20YYMMDD.n|a20YYMMDD.n]] || [[Arbitrations/a20YYMMDD.n|]] || ---- . CategoryArbitration . CategoryArbCaseAccountDelNonAssurer . CategoryArbCaseAccountCleanup . [[CategoryArbCaseCCAViolation]]