The system documentation is currently rewritten in a new system that builds HTML from ReStructuredText/Sphinx sources.

The git-Repository is at http://git.cacert.org/gitweb/?p=cacert-infradocs.git.

The generated documentation is published to https://infradocs.cacert.org.

Instructions on how to work on the new documentation are available at https://infradocs.cacert.org/building.html.

For some more background information see the mailing list thread at https://lists.cacert.org/wws/arc/cacert-sysadm/2016-05/msg00000.html.

The system related content of this page has been moved to https://infradocs.cacert.org/systems/email.html


The following part has not been moved to the new documentation because it is more of a legal discussion than a system administration aspect.

Archiving Email

Problem

The Threat of Legal Discovery is an emerging disaster in USA litigation, and is also spreading to other anglo countries. The basic model is to use the courts to force the delivery of all data on an issue, spread over many different events. Each event costs money (a full legal "act" might cost from $5k to $1m).

Considerations

Normally, most people use their own emails because the use of business and private stuff is hard to separate. Most people keep and store their email on their laptops (which may then become subject of seizure orders for examination by opposition counsel).

Solution

Employing of CAcert email addresses and server for all official businesses allows escrow into a black hole (unreadable store). In the event of a discovery motion, an Arbitrator can compel the opening of the store and the delivery of the documents. See Threats of Legal Discovery for more.

Policy consideration is that as much business for CAcert as possible should go through CAcert email addresses. This means that all roles (or officers) should use the addressess.

Permission & Tracking

As CAcert is effectively then tracking the email of Members, there will need to be permission and clear information / notification as to what is being done. E.g., check this, the applicable laws, TELECOMMUNICATIONS (INTERCEPTION AND ACCESS) ACT 1979 http://www.austlii.edu.au/au/legis/cth/consol_act/taaa1979410/ cannot intercept email inbound until it has completed http://www.efa.org.au/Issues/Privacy/tia.html. Ok checked - entirely not applicable (Daniel - 02 May 2009 - section 5(5) - telecommmunication system isn't in Australia)

Tech

Need an address to archive archive@cacert.org with bcc there on sending/receiving.

SystemAdministration/Systems/Email (last edited 2016-05-08 20:21:49 by JanDittberner)