# HG changeset patch
# User Paul Boddie <paul@boddie.org.uk>
# Date 1446243174 -3600
# Node ID f7813511d4122db7e1a096df0d64c1aa8433ce6d
# Parent  ef9449fd1ac18fefd862f2489dd268528fe4c523
Added documentation for mail clients and improved the LMTP documentation.

diff -r ef9449fd1ac1 -r f7813511d412 docs/wiki/FrontPage
--- a/docs/wiki/FrontPage	Fri Oct 30 23:12:02 2015 +0100
+++ b/docs/wiki/FrontPage	Fri Oct 30 23:12:54 2015 +0100
@@ -14,9 +14,9 @@
  will inspect, and for whom no inspection or sharing will occur at all.
 
  * It can provide a [[/CalendarManager|Web-based interface]] to calendar
- information for users who cannot or choose not to use mail software with
- calendaring support. This is optional and your users can choose to adjust,
- ignore or disable this functionality.
+ information for users who cannot or choose not to use
+ [[/MailClients|mail software]] with calendaring support. This is optional
+ and your users can choose to adjust, ignore or disable this functionality.
 
  * It supports autonomous entities such as meeting rooms and resources,
  automatically accepting or declining invitations according to their
@@ -66,7 +66,8 @@
  existing support provided by imip-agent; support for other software can
  always be added).
 
- * It does not require your users to change their mail client software.
+ * It does not require your users to change their [[/MailClients|mail client]]
+ software.
 
  * It does not insist that everybody must store their schedules on a single
  server in order to collaboratively schedule events.
diff -r ef9449fd1ac1 -r f7813511d412 docs/wiki/MailClients
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/docs/wiki/MailClients	Fri Oct 30 23:12:54 2015 +0100
@@ -0,0 +1,48 @@
+= Mail Clients =
+
+Since imip-agent is integrated with mail infrastructure defined by Internet
+standards, users can use any mail program that is capable of sending and
+receiving standards-based mail. However, it is recommended that
+[[http://tools.ietf.org/html/rfc2045|MIME]]-capable mail programs are used
+in order to properly present messages produced by imip-agent. Since the MIME
+standards have been in existence since the 1990s, most commonly-used mail
+programs should work with imip-agent with few difficulties.
+
+Meanwhile, mail clients that can understand and present calendar data are
+less common. The following Free Software programs have been tested with
+imip-agent:
+
+{{{#!table
+'''Program''' || '''Remarks'''
+==
+[[http://claws-mail.org/|Claws Mail]]
+||
+ * Supports basic scheduling
+ * Does not support recurring events
+ * Does not support the `COUNTER` scheduling method
+ * Does not support free/busy exchange over e-mail
+==
+[[http://kontact.org/|Kontact]]
+||
+ * Supports scheduling including methods like `COUNTER`
+ * Supports recurring events
+ * Seems to support free/busy exchange over e-mail (although not
+ transparently) and over HTTP
+ * Seems to require numerous libraries and KDE components, including the
+ somewhat unpolished [[WikiPedia:Akonadi]] system
+==
+[[https://www.mozilla.org/thunderbird/|Mozilla Thunderbird]] (with
+[[https://www.mozilla.org/projects/calendar|Lightning Calendar]]
+extension)<<BR>>
+''Also known as Icedove (and Iceowl) in Debian''
+||
+ * Supports basic scheduling including recurring events
+ * Does not support the `COUNTER` scheduling method
+ * Does not support free/busy exchange over e-mail, but can be made to
+ fetch free/busy data over HTTP
+}}}
+
+== Notes ==
+
+See [[http://tools.ietf.org/html/rfc5546#section-3.2.7|RFC 5546 section 3.2.7]]
+for details of the `COUNTER` scheduling method.
diff -r ef9449fd1ac1 -r f7813511d412 docs/wiki/MailIntegration--LMTP
--- a/docs/wiki/MailIntegration--LMTP	Fri Oct 30 23:12:02 2015 +0100
+++ b/docs/wiki/MailIntegration--LMTP	Fri Oct 30 23:12:54 2015 +0100
@@ -1,20 +1,21 @@
 = LMTP Delivery =
 
-When imip-agent is configured to use LMTP, it connects directly to mail
-storage solutions. By using LMTP from the agent software, the issue of
-configuring the mail system to integrate with such solutions is avoided, but
-then those solutions must expose their LMTP interface appropriately.
+When imip-agent is configured to use LMTP, it connects directly to
+[[../../MailboxIntegration|mail storage solutions]]. By using LMTP from the
+agent software, the issue of configuring the mail system to integrate with
+such solutions is avoided, but then those solutions must expose their LMTP
+interface appropriately.
 
-Although this topic is largely beyond the scope of this document, systems such
-as Cyrus and Dovecot can be configured to provide a Unix domain socket
-offering support for LMTP connections.
+Although this topic is largely beyond the scope of this documentation,
+systems such as Cyrus and Dovecot can be configured to provide a Unix domain
+socket offering support for LMTP connections.
 
 For Cyrus, the following bug report is pertinent:
 
  * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494746
 
-A permanent change in permissions on the Cyrus LMTP socket is therefore
-required to make delivery available to the `lmtp` group:
+A permanent change in permissions on the Cyrus LMTP socket may be required to
+make delivery available to the `lmtp` group:
 
 {{{
 dpkg-statoverride --force --update --add cyrus lmtp 750 /var/run/cyrus/socket