1.1 --- a/docs/wiki/FrontPage Fri Oct 30 23:12:02 2015 +0100
1.2 +++ b/docs/wiki/FrontPage Fri Oct 30 23:12:54 2015 +0100
1.3 @@ -14,9 +14,9 @@
1.4 will inspect, and for whom no inspection or sharing will occur at all.
1.5
1.6 * It can provide a [[/CalendarManager|Web-based interface]] to calendar
1.7 - information for users who cannot or choose not to use mail software with
1.8 - calendaring support. This is optional and your users can choose to adjust,
1.9 - ignore or disable this functionality.
1.10 + information for users who cannot or choose not to use
1.11 + [[/MailClients|mail software]] with calendaring support. This is optional
1.12 + and your users can choose to adjust, ignore or disable this functionality.
1.13
1.14 * It supports autonomous entities such as meeting rooms and resources,
1.15 automatically accepting or declining invitations according to their
1.16 @@ -66,7 +66,8 @@
1.17 existing support provided by imip-agent; support for other software can
1.18 always be added).
1.19
1.20 - * It does not require your users to change their mail client software.
1.21 + * It does not require your users to change their [[/MailClients|mail client]]
1.22 + software.
1.23
1.24 * It does not insist that everybody must store their schedules on a single
1.25 server in order to collaboratively schedule events.
2.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
2.2 +++ b/docs/wiki/MailClients Fri Oct 30 23:12:54 2015 +0100
2.3 @@ -0,0 +1,48 @@
2.4 += Mail Clients =
2.5 +
2.6 +Since imip-agent is integrated with mail infrastructure defined by Internet
2.7 +standards, users can use any mail program that is capable of sending and
2.8 +receiving standards-based mail. However, it is recommended that
2.9 +[[http://tools.ietf.org/html/rfc2045|MIME]]-capable mail programs are used
2.10 +in order to properly present messages produced by imip-agent. Since the MIME
2.11 +standards have been in existence since the 1990s, most commonly-used mail
2.12 +programs should work with imip-agent with few difficulties.
2.13 +
2.14 +Meanwhile, mail clients that can understand and present calendar data are
2.15 +less common. The following Free Software programs have been tested with
2.16 +imip-agent:
2.17 +
2.18 +{{{#!table
2.19 +'''Program''' || '''Remarks'''
2.20 +==
2.21 +[[http://claws-mail.org/|Claws Mail]]
2.22 +||
2.23 + * Supports basic scheduling
2.24 + * Does not support recurring events
2.25 + * Does not support the `COUNTER` scheduling method
2.26 + * Does not support free/busy exchange over e-mail
2.27 +==
2.28 +[[http://kontact.org/|Kontact]]
2.29 +||
2.30 + * Supports scheduling including methods like `COUNTER`
2.31 + * Supports recurring events
2.32 + * Seems to support free/busy exchange over e-mail (although not
2.33 + transparently) and over HTTP
2.34 + * Seems to require numerous libraries and KDE components, including the
2.35 + somewhat unpolished [[WikiPedia:Akonadi]] system
2.36 +==
2.37 +[[https://www.mozilla.org/thunderbird/|Mozilla Thunderbird]] (with
2.38 +[[https://www.mozilla.org/projects/calendar|Lightning Calendar]]
2.39 +extension)<<BR>>
2.40 +''Also known as Icedove (and Iceowl) in Debian''
2.41 +||
2.42 + * Supports basic scheduling including recurring events
2.43 + * Does not support the `COUNTER` scheduling method
2.44 + * Does not support free/busy exchange over e-mail, but can be made to
2.45 + fetch free/busy data over HTTP
2.46 +}}}
2.47 +
2.48 +== Notes ==
2.49 +
2.50 +See [[http://tools.ietf.org/html/rfc5546#section-3.2.7|RFC 5546 section 3.2.7]]
2.51 +for details of the `COUNTER` scheduling method.
3.1 --- a/docs/wiki/MailIntegration--LMTP Fri Oct 30 23:12:02 2015 +0100
3.2 +++ b/docs/wiki/MailIntegration--LMTP Fri Oct 30 23:12:54 2015 +0100
3.3 @@ -1,20 +1,21 @@
3.4 = LMTP Delivery =
3.5
3.6 -When imip-agent is configured to use LMTP, it connects directly to mail
3.7 -storage solutions. By using LMTP from the agent software, the issue of
3.8 -configuring the mail system to integrate with such solutions is avoided, but
3.9 -then those solutions must expose their LMTP interface appropriately.
3.10 +When imip-agent is configured to use LMTP, it connects directly to
3.11 +[[../../MailboxIntegration|mail storage solutions]]. By using LMTP from the
3.12 +agent software, the issue of configuring the mail system to integrate with
3.13 +such solutions is avoided, but then those solutions must expose their LMTP
3.14 +interface appropriately.
3.15
3.16 -Although this topic is largely beyond the scope of this document, systems such
3.17 -as Cyrus and Dovecot can be configured to provide a Unix domain socket
3.18 -offering support for LMTP connections.
3.19 +Although this topic is largely beyond the scope of this documentation,
3.20 +systems such as Cyrus and Dovecot can be configured to provide a Unix domain
3.21 +socket offering support for LMTP connections.
3.22
3.23 For Cyrus, the following bug report is pertinent:
3.24
3.25 * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494746
3.26
3.27 -A permanent change in permissions on the Cyrus LMTP socket is therefore
3.28 -required to make delivery available to the `lmtp` group:
3.29 +A permanent change in permissions on the Cyrus LMTP socket may be required to
3.30 +make delivery available to the `lmtp` group:
3.31
3.32 {{{
3.33 dpkg-statoverride --force --update --add cyrus lmtp 750 /var/run/cyrus/socket