table of contents
gromox.cfg(5) | Gromox admin reference | gromox.cfg(5) |
Name¶
gromox.cfg — Central configuration file for Gromox services
Description¶
The common configuration file utilized by all services. Historically, each service had separate configuration files, but the number of directives that needed explicit configuration were reduced over time to the point that there were too many distinct files for little value, and so, gromox.cfg came to be.
Configuration directives¶
- autoreply_silence_window
- If an autoreply message (other than a bounce report, e.g. out-of-office)
is to be generated, that return message will be suppressed if another
autoreply for the given {From, To} address pair was produced within the
given time period previously. (Unlike the response_audit_capacity
directive, autoreply pairs are stored persistently, in the message
database.)
Default: 1day - backfill_transport_headers
- Try to fill the PR_TRANSPORT_HEADERS property when messages are submitted.
Turning this option on requires extra storage (usually between 0.5KB and
1KB per sent message). Transport headers for sent messages can be
generated on the fly from the regular MAPI message data structures e.g.
via gromox-exm2eml(8) for analysis, so unless there is a need to retain
the results from older generator versions, you should leave this off.
Default: off - bounce_postmaster
- This directive defines the Envelope-From and From addresses for
system-generated bounce messages such as Non-Delivery-Reports
(autoresponse messages about e.g. mailbox being full, or a target email
address being invalid). RFC-5321-5322-consuming components like SMTP, IMAP
and EAS want to have an SMTP-looking address in this field. Preferably, it
should point to the administrator's mailbox (or an alias thereto).
When the value set here has no domain part and ends in just '@', the domain is taken from a re-resolution of the system hostname (so as to cope with an unqualified hostname in /etc/hosts that many system installations use).
Default: postmaster@ - exmdb_client_rpc_timeout
- If the execution of an RPC takes longer than the specified time, the
client will sever the connection and return an error to the calling
program. The value cannot be lower than 4s. The special value 0 disabled
RPC timeout checking.
Default: 0 - reported_server_version
-
Default: 15.00.0847.4040
See also¶
Gromox |