Various options control how the messages are shown and how the display is organized.
The default value for the Display/Tags menu entry. When set to "Yes", a panel with a button for each tag is shown, each button being set when the corresponding tag is assigned to the message currently selected.
The default value for the Display/Headers menu entry. "None" means not to display any message header at all, "Most" means the most useful (From, To, Cc, Date...), and "All" means the full headers text.
Tells what should displayed in the "From" column of message lists: either the name of the sender (when known), or the email address.
When a message has both HTML and Text alternative representations, this option indicates which format should be shown first in the message pane. Text is the most secure choice.
when set to Yes, URLs in the body panel appear as clickable links. The browser may need to be configured in the Paths sections.
The default value for the Display/Threaded menu entry. When set to "Yes", the messages that belong to a same thread are shown in tree-like representation, and the threads can be opened and closed.
How the dates are displayed in the message lists. Choose DD/MM/YYYY HH:MI or YYYY/MM/DD HH:MI depending on what you find the more easy to read.
The contextual popup menu of a message on display has a command fetching the last messages of the same sender than the mail currently shown. This setting tells how much of these messages this command should retrieve in one go.
The Qt library has several builtin styles (the actual list depends on the platform the interface is running on). The style controls the overall look of the interface as well as some usability tips, such as the function of the middle mouse button. Just try different styles and keep the one you like the most.
An identity is the set of characteristics that define a sender. Multiple identities can be declared, and one of them only is the default. Once an identity is defined in the preferences, it can be choosen in the mail composer.
Only the email should be entered here, without any additional comment (example: john.doe@company.com). That field is required to be able to send mail messages with manitou-mail.
The full name of the user that goes along the email address. (example: John Doe)
The identity to use by default when a new outgoing message is started with the composer (menu command: ).
A multi-line piece of text that will be appended to an outgoing message before editing takes place.
The text can contain references to certain fields that will be dynamically replaced by their current values at compose time. The fields refer to the sender's identity and the person currently using the interface to compose the message, or in the case of a message generated by a script, a pseudo-user that has a entry in the users table whose login matches the database login used to connect. Field names need to be enclosed inside angle brackets to be recognized as such.
The fields available in the signature are:
{operator_login}: the operator's database login of the person who composes the messages{operator_firstname}: the operator's first name{operator_fullname}: the operator's first name and name{operator_email}: the operator's email address{sender_email}: the sender's email address for the outgoing message, corresponding to the sender's identity{sender_name}: the name associated to the identity of the outgoing message{operator_custom_field1}: the value for the operator's custom_field1 database field.{operator_custom_field2}: the value for the operator's custom_field2 database field.{operator_custom_field3}: the value for the operator's custom_field3 database field.
An optional string consisting of ASCII characters that are supposed to represent the face of the user, encoded in a black and white 48x48 bitmap. Manitou-mail can decode this string and display it graphically along the headers; other mail programs such as XEmacs VM or Sylpheed do this as well. To encode a picture in X-Face format, you may want to check out http://www.dairiki.org/xface
The list of programs that should be used to view attachments, each corresponding to a MIME type (a MIME type is a string like 'image/jpeg', 'application/x-tar' that defines the type of data contained in an attached file).
Plain text or HTML. In the case of HTML, an alternative plain text version of the body is automatically created and attached to the outgoing message, as expected by contacts who can't or don't want to use an HTML-capable program to read their mail.
Replies can be initiated in plain text, HTML, or the same format than the original message, the latter being assumed to be the best choice in general. In any case, the format can be changed manually inside the composer during the edition of the reply.
The paths used by the user interface
the directory where attachments are written just before launching the application that is associated with their MIME type.
the directory where manitou icons files are to be found. The path set at install time is used by default, but it can be changed later, if for example, icons should be read from a shared network drive.
the directory where help files reside. The default value is empty and means that they're looked up in a location depending on the installation and the current language defined by the OS environment.
A command that will be launched when an URL is clicked. If it contains $1, that will be replaced by the URL to be opened, otherwise the URL will be appended at the end of the command. Examples:
mozilla-xremote-client 'openurl($1,new-window)' kfmclient openURL
Note that it can be different from the program used to open 'text/html' attachments.
Options about database fetch.
when a list of messages is displayed, the program can pre-fetch to memory the bodies of messages not yet read and that are immediately below in the list. That may save some time when later going through the list, especially when connected remotely through a slow network link.
the program may use more than one connexion to perform simultaneous tasks. This number is the maximum number of such connexions.
When set to a non-zero value, this parameter gives the time interval to wait between two automatic refreshs of the currently selected messages list. When set to zero, automatic refresh is disabled.
The database configuration key for this setting is fetch/auto_refresh_messages_list
This setting is only effective when the automatic refresh interval is not zero. When checked on, it means that the contents of the list will automatically show new messages following an automatic refresh, without the need for any user interaction.
When checked off, new messages will not appear until the user refreshes the selection by using the command or by clicking on the "New mail" button at the bottom right of the main window.
The contents of the quick selection panel are updated in both cases.
The database configuration key for this setting is fetch/auto_incorporate_new_results