Support / Training
Support Handbook / Precedent cases / Precedent case a20101025.1
How to handle cases that are similar to precedent case a20101025.1 Removing post from a CAcert mailing list
The procedure can be used by Support Engineer and any list owner of a CAcert mailing list.
First the SE / list owner must check if the preconditions are met.
- The original author of the post requests the removal of the post for a valid reason. Support personnel and mailing list owners decide whether a given reason is valid. Typical valid reasons include "accidental posting" and "disclosure of confident data".
- Anyone claims personal data concerning him-/herself are published in a posting, and the original author agrees the deletion of the post.
- An emergency action is necessary, as outlined in the deliberation of the precedent case, subject to confirmation by an Arbitrator.
- For completeness: An Arbitrator rules so in a regular Arbitration
The preconditions are fixed in these documents
SE or list owner checks if the preconditions to remove the requested post from the mailing list are met.
SE or list owner removes the post from the mailing list.
SE or list owner informs the user about the removal.
Possible answer to the user requesting the removal
Dear <user>, I deleted your post from the mailing list CAcert-<xxxx> following the precedent case a20101025.1 . CAcert is not able to delete copies of the requested post that are stored in copies of the mailing list hosted on other archives, as CAcert is not responsible for those copies.  https://wiki.cacert.org/Arbitrations/a20101025.1
If the removal was made by the list owner, the list owner sends the request with the execution statement and the link to the original post to firstname.lastname@example.org. for documentation.
SE enters information into the Audit Section of precedent case a20101025.1.
 Precedent case a20101025.1