MTA configuration for AXS:One archiving

From the point of view of MTA configuration, the archiving support is configured rather similarly to configuring use of a third-party,  integrated, spam/virus filter package; in particular, use of the  archiving support routines is configured via      and        MTA options. For some value of N, the     MTA  option must be  set to point to the   module, while the       option points to an archive module  option file (in  MTA option file format)  controlling a few options for the archiving module. For instance: spamfilter1_library=IMTA_LIB:libarch.so spamfilter1_config_file=IMTA_TABLE:archive.dat See Archive_spamfilterN_config_file for further discussion of what may (and must) appear in the archive module option file.

In addition, when it is desired (as it normally is) to be able to correlate the messages in the Message Store with their archived version  in the AXS:One system, then the MTA itself should be configured to  generate an identifying hash for each message being delivered into the  Message Store. (The AXS:One archiving module will generate an identifying message hash for each message that does not already have  one itself; this is sufficient for archived messages that do not have a  corresponding copy in the Message Store---for instance, archived copies  of messages sent to remote recipients.) The material to be hashed, and  the algorithm for generating the hash, are controlled via MTA options   and    ;  channels are individually configurable, via  certain   channel options, as to whether they generate, preserve, or delete, such  hashes for messages passing through them. See Message identifier generation for further discussion of the generation of such identifying hashes.

Finally, when archiving messages there is the question of identifying the user for whom messages were originally destined---a user  identifier. By default, each user&#x27;s canonical e-mail address is used. However, the  MTA option, also discussed in  Message identifier generation,  may be set to specify use of some alternate form of identifier; when  set, the AXS:One archiving facility will generate and use unique user  identifiers according to this template, rather than e-mail addresses as  by default.

See also:
 * Example message archiving configuration
 * spamfilter1_config_file MTA Option
 * spamfilter1_library MTA Option
 * Legacy configuration MTA option file
 * Archive spamfilterN_config_file
 * Message identifier generation
 * AXS:One archive integration