'fetchd' Parameters in /etc/fetchd.conf
Support knowledgebase (rsimai_imap_fetchd_params)
Applies to
eMail Server: Version 3.x
Subject:
This article describes the parameters of the daemon 'fetchd' in the file /etc/fetchd.conf
,
which is used for the fetch mail function.
Parameters
The given values are the default values after the installation.
Modify these values only if you know exactly what you are doing.
A wrong configuration might result in data loss.
Restart the daemon to adopt modified values:
rcfetchd restart
-
debug = 0
'debug=1' activates the debugging for fetchd.
Further messages are written in /var/log/messages.
-
keeponserver = 0
Fetched e-mails are not removed from the server with 'keeponserver=1'.
However, all e-mails are fetched each time fetchd is executed.
This function should be used for debugging purposes only.
-
unixsocket = /var/run/fetchd.sock
The socket used by fetchd to communicate with other system components.
-
ldaphost = localhost
LDAP server from which the data is fetched via the POP or IMAP accounts.
-
ldap_reconnect_interval = 5
The number of seconds fetchd waits before retrying a connection to the LDAP server after
an interruption.
-
ldap_max_reconnect = 20
Number of the reconnection attempts fetchd should make before giving up.
-
mailadmin = mailadmin
The local user to which fetchd sends messages by e-mail.
-
append_fetch_header = 1
This parameter is currently ignored.
fetchd appends an additional header line to the fetched messages:
X-Fetched: by SuSE eMail Server...
-
thread_max = 5
The maximum number of processes that can be started simultaneously.
In theory, a process can be started for each single POP or IMAP account.
To do this, the value must be increased accordingly.
Drawbacks:
- Providers support only a certain number of simultaneous POP or IMAP connections.
- Every process consumes a certain amount of RAM depending on the size of the fetched e-mail.
On systems without sufficient RAM, this might result in a system 'freeze'.
-
priority_granularity = 10
The lower the value for thread_max, the higher the value for priority_granularity should be.
As a general rule, the value for priority_granularity should be at least twice as large as the one for
thread_max.
The reason is that fetchd uses a job list containing the jobs along with their priority.
If the number of jobs to execute exceeds that allowed by thread_max,
the jobs and their priority are placed in a queue and, after a minute, a new attempt is made
to execute the jobs. In case this attempt fails again, the priority increases until each job has
been executed. This may result in certain jobs being executed after a few minutes
to avoid possible problems due to an excessive RAM usage.
See also:
Changing the Maximum Number of fetchd Processes
Keywords: FETCHD, IMAP31, EMAIL SERVER
Categories:
SuSE Linux IMAP Server
SDB-rsimai_imap_fetchd_params, Copyright SuSE Linux AG, Nürnberg, Germany
- Version: 18. Nov 2002
SuSE Linux AG - Last generated: 25. Mar 2003 by glazzar (sdb_gen 1.40.0)