Crontab: update documentation files.

app/views/App/apps/imp/docs/PERFORMANCE.html

@@ -11,8 +11,7 @@ <h1 class="title">IMP Performance Guide</h1>
 <p>Tips on performance tuning systems for IMP.  See <a class="reference external" href="../../horde/docs/PERFORMANCE">horde/docs/PERFORMANCE</a>
 for general performance tips for Horde.</p>
 <ul>
-<li><p class="first">Use an IMAP server that supports CONDSTORE (<a class="reference external" href="http://www.faqs.org/rfcs/rfc4551.html">RFC 4551</a>) and/or QRESYNC (<a class="reference external" href="http://www.faqs.org/rfcs/rfc5162.html">RFC
-5162</a>).</p>
+<li><p class="first">Use an IMAP server that supports CONDSTORE and/or QRESYNC (<a class="reference external" href="http://www.faqs.org/rfcs/rfc7162.html">RFC 7162</a>).</p>
 <p>These extensions are required to properly cache data and to properly keep
 the dynamic display synchronized. It is impossible to do otherwise, and the
 UI experience will be limited without these extensions. Additionally, if

app/views/App/apps/imp/docs/RFCS.html

@@ -94,8 +94,7 @@ <h1>IMAP</h1>
 </tr>
 <tr class="field"><th class="field-name"><a class="reference external" href="http://www.faqs.org/rfcs/rfc6851.html">RFC 6851</a>:</th><td class="field-body">MOVE</td>
 </tr>
-<tr class="field"><th class="field-name" colspan="2"><a class="reference external" href="http://www.faqs.org/rfcs/rfc4551.html">RFC 4551</a>/<a class="reference external" href="http://www.faqs.org/rfcs/rfc5162.html">RFC 5162</a>/RFC XXXX:</th></tr>
-<tr><td>&nbsp;</td><td class="field-body">CONDSTORE/QRESYNC</td>
+<tr class="field"><th class="field-name"><a class="reference external" href="http://www.faqs.org/rfcs/rfc7162.html">RFC 7162</a>:</th><td class="field-body">CONDSTORE/QRESYNC</td>
 </tr>
 <tr class="field"><th class="field-name" colspan="2">draft-ietf-morg-inthread-01:</th></tr>
 <tr><td>&nbsp;</td><td class="field-body">THREAD=REFS</td>

app/views/App/apps/ingo/docs/CHANGES.html

@@ -3,6 +3,7 @@ <h3>Changes by Release</h3><pre>
 v3.2.0-git
 ----------
 
+[mms] Honor 'auto_update' preference when re-sorting filters list (<a href="http://bugs.horde.org/ticket/13216">Bug #13216</a>).
 [mms] Fix regression in copying a rule when storing in SQL backend (<a href="http://bugs.horde.org/ticket/13213">Bug
       #13213</a>).
 

app/views/App/apps/webmail/docs/INSTALL.html

@@ -506,14 +506,13 @@ <h1><a class="toc-backref" href="#id7">4&nbsp;&nbsp;&nbsp;Configuring Horde Grou
 </ol>
 </li>
 <li><p class="first">Configuring Horde Groupware Webmail Edition</p>
-<p>Documentation on the format and purpose of the configuration files
-in the <tt class="docutils literal">config/</tt> directory can be found in each file. The
-defaults will be correct for most sites. If you wish to customize
-Horde Groupware Webmail Edition's appearance and behavior, create
-&quot;local&quot; files for the configuration file you want to change. For
-example if you want to change the default value and lock a
-preference, create a <tt class="docutils literal">config/prefs.local.php</tt> file with the
-following content:</p>
+<p>Documentation on the format and purpose of the configuration files in the
+<tt class="docutils literal">config/</tt> directory can be found in each file. The defaults will be
+correct for most sites. If you wish to customize Horde Groupware Webmail
+Edition's appearance and behavior, create &quot;local&quot; files for the
+configuration file you want to change. For example if you want to change the
+default value and lock a preference, create a <tt class="docutils literal">config/prefs.local.php</tt>
+file with the following content:</p>
 <pre class="literal-block">
 &lt;?php
 $_prefs['prefname']['value'] = 'somedefault';
@@ -522,24 +521,36 @@ <h1><a class="toc-backref" href="#id7">4&nbsp;&nbsp;&nbsp;Configuring Horde Grou
 <p>This works with any configuration file.</p>
 <div class="warning">
 <p class="first admonition-title">Warning</p>
-<p>All configuration files in Horde Groupware Webmail
-Edition are PHP scripts that are executed by the web
-server. If you make an error in one of these files,
-Horde might stop working. Thus it is always a good
-idea to test the configuration files after you edited
-them. If you want to test mime_drivers.local.php for
+<p>All configuration files in Horde Groupware Webmail Edition are
+PHP scripts that are executed by the web server. If you make an
+error in one of these files, Horde might stop working. Thus it
+is always a good idea to test the configuration files after you
+edited them. If you want to test mime_drivers.local.php for
 example run:</p>
 <pre class="last literal-block">
 php -l mime_drivers.local.php
 </pre>
 </div>
-<p>The default configuration stores files uploaded through the file manager in
-the SQL database. This is the most compatible configuration but doesn't
-scale well, may hit some database server limits, and may only work for very
-small installations. You should configure a different backend as soon as
-possible. See <tt class="docutils literal">gollem/config/backends.php</tt> and
+<ul>
+<li><p class="first">By default, Horde Groupware Webmail Edition is configured to NOT display
+text/html message parts inline.  This is done for various security
+reasons.  If you would like to see text/html parts inline, you must create
+a <tt class="docutils literal">imp/config/mime_drivers.local.php</tt> file (or add to the existing
+mime_drivers.local.php file) with the following content:</p>
+<pre class="literal-block">
+&lt;?php
+$mime_drivers['html']['inline'] = true;
+</pre>
+</li>
+<li><p class="first">The default configuration stores files uploaded through the file manager
+in the SQL database. This is the most compatible configuration but doesn't
+scale well, may hit some database server limits, and may only work for
+very small installations. You should configure a different backend as soon
+as possible. See <tt class="docutils literal">gollem/config/backends.php</tt> and
 <tt class="docutils literal"><span class="pre">gollem/config/backends.d/10-webmail.php</span></tt> for details.</p>
 </li>
+</ul>
+</li>
 <li><p class="first">Setting up alarm emails</p>
 <p>If you want your users to be able to receive emails from the Horde_Alarm
 system, you must set up a cron entry for <tt class="docutils literal"><span class="pre">horde-alarms</span></tt>, you