Update ancient Ingo information

app/views/App/apps/ingo/ingo.html.php

@@ -4,10 +4,10 @@
 create
 Sieve, <a href="http://www.procmail.org/">procmail</a>, <a href="http://www.courier-mta.org/maildrop/">maildrop</a>,
 and IMAP filter rules. The IMAP filter driver translates the filter rules on
-demand to IMAP commands, executed via <a href="http://www.php.net/imap">PHP's
-IMAP extension</a> and has replaced IMP's internal filtering code. It is now
-the default filtering agent in <?php echo $this->linkTo('IMP',
-array('controller' => 'app', 'action' => 'app', 'app' => 'imp')) ?>.</p>
+demand to IMAP commands.</p>
+
+<p>Ingo is the default filtering management application used in
+<?php echo $this->linkTo('IMP', array('controller' => 'app', 'action' => 'app', 'app' => 'imp')) ?>.</p>
 
 <p>Ingo is able to create and eventually run server as well as client filter
 scripts. The filter script API is flexible enough that any number of filter
@@ -18,25 +18,19 @@
 <p>It supports a set of &quot;special&quot; rules that are either translated to
 their native counterparts of the filter script backend or emulated through
 filter script commands. These rules are Blacklist, Whitelist, Forwards, and
-Vacation. Maybe they will replace the existing Horde modules <?php echo
-$this->linkTo('Vacation', array('controller' => 'app', 'action' => 'app', 'app'
-=> 'vacation')) ?> and <?php echo $this->linkTo('Forwards', array('controller'
-=> 'app', 'action' => 'app', 'app' => 'forwards')) ?> of the <?php echo
-$this->linkTo('Sork', array('controller' => 'app', 'action' => 'app', 'app' =>
-'sork')) ?> suite in the future. These are much older than Ingo and currently
-support dot-forward, LDAP, SQL, qmail, Mdaemon, and SOAP backends.</p>
+Vacation.</p>
 
 <p>Ingo abstracts storage, script, and transport backends. That means that the
 filter rules in Ingo's internal format can be stored in several
-places. Currently only Horde's preferences are supported, but SQL or LDAP
-storage drivers would be easy to write. The transport backends are responsible
+places. Currently, both Horde's preferences and SQL-based storage are
+supported. The transport backends are responsible
 for uploading the generated filter scripts to the filter backends, for example
 to <a href="http://asg.web.cmu.edu/cyrus/">Cyrus</a>' timsieved daemon or
 through Horde's VFS (Virtual File Storage) API via FTP to the users' home
 directories or into a SQL database. System administrators are able to switch to
 a different filter system or script storage at any time and the users' filter
 rules will persist.</p>
 
-<p>The application's name has been created during the quest for a nice,
+<p>The application's name was created during the quest for a nice,
 &quot;hordish&quot; name for the new born code, and is short for &quot;Mail
 comes 'in'...Where does it 'go'?&quot;.</p>

app/views/App/index.html.php

@@ -81,9 +81,8 @@
           => 'ingo')) ?>">Ingo</a> <?php echo
           HordeWeb_Utils::downloadIcon($this, 'ingo') ?></h3>
           <p>Ingo is an email filter rules manager.  It can generate Sieve,
-          procmail and IMAP scripts and upload them to or execute them on the
-          server (using a timsieved or VFS FTP driver, or the PHP IMAP
-          extension, respectively).</p>
+          procmail, maildrop, and IMAP scripts and upload them to or execute
+          them on the server.</p>
 
           <h3><a href="<?php echo $this->urlWriter->urlFor('app', array('app'
           => 'sork')) ?>">Sork</a></h3>