Response Route X.400
Introduction: Phase 6.
Note: X.400 is a special type of email protocol. The X.400 service must be licensed and activated on the Integration Server to use this Response Route. Please contact our support or sales staff.
Note: The UAFI program provided by X.400 providers is not supported.
Note: With extremely large files, the communication between Lobster_data and the DMZ server can lead to a timeout. A solution is described in section Dealing with Timeouts Due to Extremely Large Files.
(1) You have to select an X.400 channel for this Response Route.
(2) Specifies whether to send from the Integration Server directly or via the DMZ server. If no DMZ is configured, this checkbox has no effect. Note: We advise against this option, as it can lead to performance losses and there is no loss of security for a purely outbound connection if you do not use a DMZ.
(3) The values coming from the selected channel (yellow fields) can be overwritten.
(4) If the data is sent in the body, (X.400-specific) encodings are available.
(5) Here you can choose if and how the data should be attached (body/attachment).
(6) Here you can additionally attach files from the file system. If you use the prefix filter:, you can use an entry to define an entire list of files instead of just one file. So all files orders*.pdf in this example. The names of the files are also used as names of the attachments. Note: The files are deleted after they have been attached. This behaviour can be prevented by creating a profile variable VAR_MAIL_SKIP_DELETE_ATTACHMENT (type Boolean) with value true. Phase 3 must be active for this.
(7) When data is sent in the attachments (5), the MIME type can be selected. If the MIME type is set to lobster/unzip, the payload will be considered as a zip file and the contained files will be added as individual attachments.
(8) The name of the main attachment. Not relevant for (6).
(9) This option will only be active after the channel (1) has been selected. If the option is set, an acknowledgement of receipt for the sent X.400 message is requested from the recipient. If the use of the Comm Log has been set for the channel, the acknowledgement of receipt appears in the MDN. If not, then the acknowledgement of receipt is ignored.
(10) If this checkbox is set, empty files are transferred as well.