Community » Applications » Ingo
Ingo, the "Email Filter Rules Manager", started as a frontend for the Sieve filter language, and is now a generic and complete filter rule frontend that currently is able to create Sieve, procmail, maildrop, and IMAP filter rules. The IMAP filter driver translates the filter rules on demand to IMAP commands.
Ingo is the default filtering management application used in IMP.
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 drivers can be written and "plugged in". Each filter driver exposes it's capabilities to Ingo, that in return adapts its UI to display only those rules and features that the driver can actually handle.
It supports a set of "special" 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.
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, 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 Cyrus' 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.
The application's name was created during the quest for a nice, "hordish" name for the new born code, and is short for "Mail comes 'in'...Where does it 'go'?".
The Horde Project
@soydeedo The official roadmap is at http://t.co/llnrh6v5qu though it hasn't been updated since the last release. Thanks for the reminder.
1 week ago