Horde is both a piece of software and a project. The Horde Project comprises a set of Web-based productivity, messaging, and project-management applications, each of which is described below. The Horde Framework is a common code-base used by Horde applications, including libraries and a common user interface.
The Horde Framework doesn't do anything on its own; as a user, you will always be interacting with a Horde-based application.
IMP is the Internet Messaging Program (formerly, among other things, the IMAP webMail Program), a webmail system and a component of the Horde project. IMP is the most widely-deployed component of Horde.
IMP offers most of the features users have come to expect from their conventional mail programs, including attachments, spell-check, address books, multiple folders, and multiple-language support.
Turba is the Horde Address book and Contact Management application. It grew out of the need for a more complete address book than the one built in to older versions of IMP. It provides a generic frontend to searching LDAP, SQL, and other contact sources.
Kronolith is a web-based calendar and daily organizer (think Day-Timer). It currently provides a robust web-based calendar for individual users with repeating events, and a smart algorithm to display a whole day of events even if many of them overlap with each other. Future plans include support for shared calendars, merging multiple calendars into a single view, and Palm syncing.
Nagis a simple, multiuser task list manager.
Mnemo is a simple note manager (meno pad application).
The best place to turn for assistance with Horde applications is the support staff at the Internet service provider, school, company, or other organization whose webmail service you are using. Many commonly-encountered problems involve local matters with which Horde developers cannot assist you.
If you are not able to obtain assistance from your local support staff, you may wish to try asking the mailing list for the component you're using. Make sure you describe the problem clearly, including all error messages you might have received. Remember to report the version number of the application (if you know it), as well as what browser and OS you are using to access it.
Please don't contact the developers or the FAQ maintainer directly. They usually don't have time to deal with individual installations of Horde and its components, being too busy developing and FAQ-maintaining. (Besides, they're probably on the mailing list anyhow.)
Unfortunately, the documentation for Horde applications often lags behind the application itself, and much of the current versions of Horde applications remain undocumented. Speak with your local support staff to see if local documentation has been made available.
If you would like to volunteer to write a user's manual for a component of Horde, please let us know on the docs mailing list!
Before you do anything, take a moment to read this article on bug reporting, and keep its comments in mind when reporting Horde bugs.
Having read that, there are two places where a bug can be reported. If you're on the mailing list for the component you think you've found a bug in, send a message to the mailing list, and be sure to keep an eye out for replies. You can also enter the bug into the Horde bug database.
Be sure to describe exactly how to reproduce the bug (if you know!), and include all error messages that appeared. Also, please inform your local support staff of the bug; they will be able to provide us with information specific to your organization's configuration which may be necessary in resolving the problem.
If, while using a Horde application, error messages appear in your browser, inform your support staff of the problem, being sure to note the exact error message, what you were doing when it occurred, and the time and date of the occurrence. Should they not be able to resolve the problem, they can follow the bug-reporting directions found in the Horde Administrator's FAQ.