zarafa-dagent.cfg (5) - Linux Man Pages
zarafa-dagent.cfg: The Zarafa dagent configuration file
zarafa-dagent.cfg - The Zarafa dagent configuration file
The file consists of one big section, but parameters can be grouped by functionality.
The parameters are written in the form:
name = value
The file is line-based. Each newline-terminated line represents either a comment, nothing, a parameter or a directive. A line beginning with `#' is considered a comment, and will be ignored by Zarafa. Parameter names are case sensitive. Lines beginning with `!' are directives.
Directives are written in the form:
The following directives exist:
Include and process
Example: !include common.cfg
EXPLANATION OF EACH PARAMETER
IP address to bind to. 0.0.0.0 for any address.
Unix socket to find the connection to the Zarafa server.
After correctly starting, the dagent process will become this user, dropping root privileges. Note that the log file needs to be writeable by this user, and the directory too to create new logfiles after logrotation. This can also be achieved by setting the correct group and permissions.
Default value is empty, not changing the user after starting.
After correctly starting, the dagent process will become this group, dropping root privileges.
Default value is empty, not changing the group after starting.
Write the process ID number to this file. This is used by the init.d script to correctly stop/restart the service.
Use this file as key to logon to the server. This is only used when server_socket is set to an HTTPS transport. See the
manual page on how to setup SSL keys.
Default: value not set.
The password of the SSL key file that is set in sslkey_file.
Default: value not set.
Port to listen to for LMTP requests
The maximum number of LMTP threads that can be running simultaneously. This is also limited by your SMTP server. (20 is the postfix default concurrency limit)
To detect if the receiving mail is spam, the DAgent can check this header for a value that is in there. This name is case insensitive. If this option is empty, the detection method will be turned off. You can also force a delivery to the Junk Mail folder using the
When this value is found in the
spam_header_name, the mail will be considered spam, and will be delivered in the user's Junk Mail folder. The value can be anywhere in the header, not just the start. The value is case insensitive.
The method which should be used for logging. Valid values are:
- Use the Linux system log. All messages will be written to the mail facility. See also syslog.conf(5).
- Log to a file. The filename will be specified in log_file.
When logging to a file, specify the filename in this parameter. Use
(minus sign) for stderr output.
Specify whether to prefix each log line with a timestamp in 'file' logging mode.
The level of output for logging in the range from 0 to 5. 0 means no logging, 5 means full logging.
Log the raw message to a file. The file is saved to the location specifed in
Path to save the raw message.
Archive incoming message on delivery. If an archive is attached to the target mailbox, the message will immediately be archived upon delivery.
Rules will be processed before the message is archived, so when a rule moves the message to an alternate location, the archived message will be placed in the correct location in the archive. When the incoming message is copied by a rule, only the original message is archived.
Zarafa-dagent can auto-accept meeting requests if the mr-accept option is enabled for a user. When this option is enabled and a meeting request or meeting cancellation is received, this script is started with the following parameters: /usr/bin/zarafa-mr-accept <username> </path/to/dagent.cfg> [<ENTRYID>].
If the script is successful (exitcode is 0), then no other actions are performed (eg rules or vacation messages) and the message is not delivered in the inbox. If the script exits with a non-zero exit code, rules and vacation messages are run as usual, and the message is delivered in the inbox (or other folder, depending on rules or options).
Enable or disable the dagent plugin framework.
The path to the dagent plugin manager.
Path to the activated dagent plugins. This folder contains symlinks to the zarafa plugins and custom scripts. The plugins are installed in
/usr/share/zarafa-dagent/python/plugins. To activate a plugin create a symbolic link in the
Some emails do not contain any charset information or specify us-ascii even though it isn't. In both cases, dagent will assume the following charset is used. Note that this implies that the given charset should be a superset of us-ascii (most charsets are).
Enable the addition of X-Zarafa-Rule-Action headers on messages that have been forwarded or replied by a rule.
Enable this option to prevent rules to cause a loop. An e-mail can only be forwarded once. When this option is enabled, the set_rule_headers option must also be enabled.
The following options are reloadable by sending the zarafa-dagent process a HUP signal:
- The Zarafa dagent configuration file.