Transmission Type X.400

See also section Transmission (→ metadata).

(1) The maximum number of files that can be sent per message can be specified here. This can lead to several messages being created within a triggered transmission. You will find corresponding messages in the ASM log ("... message 1", "... message 2", ...). However, all files collected up to that point are always processed for each triggered transmission.

(2) This value applies to the sum of the attachments. If the value is exceeded, a new mail is generated. This mechanism is ignored for value 0.

(3) A transmission can also be processed via a DMZ server (if installed), i.e. the DMZ server establishes the connection to the target system.

(4) If this checkbox is not set, then sending is not interrupted even in the case of faulty mails.

(5) An X.400 channel must be selected here.

(6) If the checkbox is not set, only ASM entries using the identical partner channel that the profile uses in the X.400 Response Route can be selected there. If the checkbox is set, then all ASM entries that have a channel of the same type can be selected (i.e. all ASM entries with an X.400 channel). Since n emails, with one attachment each, are sent in an ASM session with individual processing, the channel can, therefore, change during the session (and thus sender, subject and recipient). Without individual processing, an email can have many attachments, but the maximum number is defined in (1).

(7) With the __use_subject__ placeholder, the value of the Subject field from the metadata of the X.400 Response Route of the profile sending to the ASM entry can be used. Note: The placeholder can be inserted via the icon on the right.

(8) The MIME type of the message. 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.

(9) With the __use_body__ placeholder, the value of the Message text field from the metadata of the X.400 Response Route of the profile sending to the ASM entry can be used. Note: The placeholder can be inserted via the icon on the right.

(10) Here you can select an X.400-specific encoding.

(11) 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.