X.400 (mail)
The UAFI program provided by X.400 providers is not supported.
Settings
(1) Channel selection: Channel of type "X.400" that has to be selected and is used for the connection to the server and to fetch the emails (fetching channel).
(2) Activate parallel processing: If this checkbox is set, multiple instances of the processing profile may run in parallel. In that case, the checkbox Profile may only run in one instance must not be set for the processing profile. For processing details, see section Parallel processing of mails.
(3) Via DMZ: The DMZ server can be used for the transfer (if there is one). If no DMZ is configured, this checkbox will not be displayed. Note: With extremely large files, the communication between Integration Server and the DMZ server can lead to a timeout. A solution is described in section Dealing with Timeouts Due Extremely Large Files.
(4) Unknown mails: If no matching processing profile is found for an email (see following section), it will be moved to the Unresolved area or discarded. See also section Non-assignable emails.
(5) Fetch all X.400 mails: Every job can either fetch all emails or just the unread ones.
(6) Restrict polling for the specified X.400 address: The only messages that are fetched are those that come from the selected channel (1) or those that match one of the comparison channels in the distribution rules (details see there).
(7) Restrict polling for mails received later than last run: Only emails that have arrived since the last run of the profile will be retrieved.
(8) Do not delete picked up X.400 mails: Files are not removed from the server after fetching.
Distribution rules
See section Distribution rules (mail). If no rule is specified or no rule applies, setting (4) applies.
System variables
The system variable VAR_SYS_MAIL_BODY is filled with the text of the body and passed to each job that processes data from the message (attachment or body).
See also VAR_SYS_ATTACHMENT_NAME and VAR_SYS_MAIL_ATTACHMENTS (number of attachments).