Use_text_databases MTA option

From Messaging Server Technical Reference Wiki
Jump to: navigation, search



File format MTA options: use_text_databases (bitmask)

The use_text_databases MTA option controls whether the reverse "database", the general "database", and the forward "database" are truly on-disk databases, or whether they are instead stored as in-memory structures. As of MS 8.0.2.3, the bits in the option default to 1 if the corresponding URL option is not set and 0 otherwise. The default value was 8 prior to MS 8.0.2.3. The default is 0 in versions of Messaging Server prior to 8.0.2.3. Setting a bit of use_text_databases, so that an in-memory structure is used, makes moot any setting of the corresponding, new in MS 8.0, *_database_url MTA option: the in-memory structure will be used in preference to consulting memcache.

If bit 0 (value 1) is set, then the IMTA_TABLE:general.txt file (configroot/general.txt) is read when the MTA configuration is initialized or reloaded, and the information from that file is stored in memory replacing all uses of the general database.

If bit 1 (value 2) is set, then the IMTA_TABLE:reverse.txt file (configroot/reverse.txt) is read when the MTA configuration is initialized or reloaded, and the information from that file is stored in memory replacing all uses of the reverse database.

If bit 2 (value 4) is set, then the IMTA_TABLE:forward.txt file (configroot/forward.txt) is read when the MTA configuration is initialized or reloaded, and the information from that file is stored in memory replacing all uses of the forward database.

In particular, note that enabling use of such in-memory "databases" means that changes to the "database" (changes to the underlying text file source) require recompiling the configuration, or reloading the configuration, in order to get the change seen in a compiled configuration; see the cnbuild utility and the reload utility. As of MS 6.3P1, text databases support including other files via the < character, and comment lines (indicated by the presence of any of the comment_chars characters in column one).


See also: