diff --git a/CAcertCommunicationPolicy.html b/CAcertCommunicationPolicy.html
deleted file mode 100644
index e2b6b34..0000000
--- a/CAcertCommunicationPolicy.html
+++ /dev/null
@@ -1,179 +0,0 @@
-
-
-
-
-
- CAcert Communication Policy (CCP)
-
-
-
-
- CAcert Communication Policy (CCP)
-
-
- ![CAcert Draft](Images/cacert-draft.png)
- Editor: Sam Johnston
- Creation date: 2008-04-16
- Status: DRAFT 2008-04-25 (m20080425.1)
- Next status: POLICY 2008-XX-XX
-
-
-
- 0. Preliminaries
-
-
- This CAcert policy describes how CAcert communicates as required for achieving its mission.
-
-
- 1. Scope
-
-
- CAcert Community Members are subjected to the CAcert Communication Agreement (CCA).
-
-
- This policy is applicable to:
-
-
- - Press Releases and Announcements
-
- - Internet Email
-
- - Internet Relay Chat (IRC)
-
-
-
- 2. Requirements
-
-
- This section describes all CAcert communication channels.
-
-
- -
- Press Releases and Announcements
-
- - CAcert Community Members may communicate on their areas, but these are considered community views.
-
- - Targeted announcements may be sent to a minority subset of users who have opted-in to receiving information on the topic.
-
- - Press releases and official announcements must be approved by the board and issued via:
-
- - Digitally signed email to appropriate mailing list(s).
-
- - Posting and indefinite archiving on the official CAcert web site(s)
-
-
-
-
-
- -
- Internet Email
-
- -
- Email Aliases are official email addresses within the CAcert domain(s) (eg john@cacert.org).
-
- - All official CAcert communications must be conducted using an official address, which is typically a forwarding service.
-
- - Access to full accounts (available only to officials listed on the organisation chart) shall be available via web interface and standard mail protocols.
-
- - Outbound mail should contain the full name and short reference to the official capacity of the user: John Citizen (CAcert AO) <john@cacert.org>.
-
- - Role accounts (eg support@cacert.org) shall be implemented as a mailing list or automated issue tracking system as appropriate.
-
-
-
- -
- Mailing Lists are automated distribution lists containing CAcert community members.
-
- - List management (new list creation, dead list removal) shall be managed by the board.
-
- - List membership shall be restricted to CAcert Community members and all posts are contributions, as described in the CCA.
-
- - Lists shall follow the naming convention of cacert-<listname>@lists.cacert.org, with important lists (eg support, board) aliased @cacert.org
-
- - List policy shall be set on a per-list basis (eg open/closed, searchable archives, etc.)
-
- - Open lists (eg cacert-policy) shall be accessible by anyone (including Internet search engines) and closed lists (eg cacert-board) only by list members.
-
- - Posting to discussion lists (eg cacert-policy) must be restricted to list members and must not be restricted for role lists (eg cacert-board).
-
- - Messages which do not meet list policy (eg size, non-member) must be immediately rejected.
-
-
-
- - Subscription requests must be confirmed by the requestor and subscriber lists must not be revealed..
-
- - Web based archives shall be maintained and authentication must reflect list policy.
-
-
-
- -
- Automated Email is sent by various CAcert systems automatically
-
- - All new automated emails must be approved by the board.
-
- - Automated emails should only be sent in response to a user action.
-
-
-
- -
- Personal Email is individual personal addresses of CAcert Community members (eg john@gmail.com).
-
- - Personal email must not be used for official CAcert purposes.
-
-
-
-
-
- -
- Internet Relay Chat (IRC)
-
- - An IRC service shall be maintained at irc.cacert.org which shall be available via SSL.
-
-
-
-
-
- 3. Implementation
-
-
- This section describes how CAcert communication channels are to be implemented.
-
-
- -
- General
-
- - CAcert System Administrators shall have discretion as to the technical implementation of this policy and shall report status to the board periodically.
-
-
-
- -
- Security
-
- - Authentication (where required) must be done via username and password and/or CAcert certificate.
-
- - Transport encryption must be used where possible.
-
- - Content encryption may be used where appropriate.
-
- - All outbound mail should be digitally signed.
-
-
-
- -
- Internet Email
-
- - All mails must be securely archived.
-
- - All mails must be subject to appropriate spam prevention mechanisms (eg SpamAssassin, greylisting).
-
- - All mails must be subject to appropriate virus and content filtering (eg ClamAV, content types).
-
-
-
-
-
-
-
-
-