====== Ftp/Ftps send channel ======

The FTP send channel allows the connection of an FTP directory to a remote host. Messages are stored in the directory stored in the communication channel from the message basket (outgoing) in the form of files.

==== Properties ====

^Name  ^Meaning|
|//Name//|Name of the communication channel.|
|//Channeltype//|Re-list the type. (For verification)|
|//communication direction//|Preferably incoming.|
|//Messagebox //|Messagebox for incoming messages //(incoming)///, must be selected in the corresponding lookup table.|
|//Preset Sender//|Here you can assign a fixed sender, which is intended for this channel..|
|//Preset Recipient//|Here you can assign a fixed receiver, which is intended for this channel.|
|//Validation of the sender//|checks the sender address of the Interchanges for certain EDI subscribers, if they do not contain the specified subscriber, the message is entered with an error message in the inbound message basket and a corresponding report is generated (only if Required). The test method is selected by means of a combo box (None, Optional, Required, Fixed partner).|
|//Validation of the receipient//|checks the recipient address of the Interchanges for certain EDI subscribers, if they do not contain the specified subscriber, the message is placed in the message basket with an error message and a corresponding report is generated (only if required). The test method is selected by means of a combo box (None, Optional, Required, Fixed partner).|
|//Public//|By checking the check mark, the communication channel can be used for all subnodes. However, if a communication channel with the same name is created in the subnode, the communication channel of the subnode is used.|
|//Repetitions in case of errors//|If an error occurs, the number of consecutive reception attempts is determined by entering a value in the corresponding field.|
|//Automatic Unzipping//|Documents or attachments are automatically unzipped using the procedure selected in the combo box.|

==== Properties (enhanced) ====


^Name  ^Meaning|
|//Host//|IP address of the email server e. g. //175.11.214.25//.|
|//Port//|FTP-Port (preferably 21).|
|//Username//|Login to the FTP directory.|
|//Password//|Password of the FTP directory.|
|//Output path//|Path of the FTP output directory, e. g. ///ab/xyz/incomming//|
|//file mask//|Here you can define a mask that only certain files can be read in e. g. //*.dat//.|
|//FTP transfer mode//|Setting the transmission mode. Mode //(Auto, Text, Binary)// can be selected in the corresponding look main table.|
|//Use temporary file names//|Specifies whether a different name is to be used for transferring the file. This option is activated by checking the checkbox.|
|//Temporary file name//|Setting a temporary file name for the transfer. The whole file name is specified, the default value is '_upload_.tmp', i.e. if 'Use temporary file name' is activated and no 'Temporary file name' has been stored, then the file name '_upload_.tmp' is used. After the successful transfer of the file, the file will be renamed to the actual filename.|
|//Action after collection//|Specifies whether the file should remain, be deleted or moved after retrieval. Whether the option to delete or move is supported depends on the FTP server used.|
|//Target path for moving//|Directory to which the file is to be moved in the FileHandling method Move or MoveWithTimeStamp.|
|//'PROT P' send//|If a connection is implicitly encrypted via SSL, the "Prot P"command should be sent to the server -> RFC 4217|
|//Extended directory listing//|If this option is not selected, the FTP server will use the simple directory list to retrieve files from the FTP server. This means that directories cannot be distinguished from files, but this is irrelevant for a corresponding file mask. If this option is selected, the detailed directory display is used, but on a few ftp-servers it leads to results that cannot be evaluated. But there is no problem with the recognition of the files.|
|//PFX file of the SSL certificate//|The client's private certificate (for client side authentication)|
|//Password of the SSL certificate//|That to the above mentioned. Certificate associated password.|
|//SSL behavior//|How to encrypt the connection using SSL. Mode (None, Offer (=Automatic), Explicit, Implicit). In implicit mode, communication is immediately started via an encrypted channel, via another port. More often, the explicit mode is used. The connection is established via the non-encrypted standard ftp port and after the connection is established, but before authentication, it is switched to the encrypted mode.|
|//Passive Mode//|Using this flag, the server can be set to passive or active mode -> RFC 959|
|//Complete log (also **password**!)//|Complete output of the executed commands and results in the log (including passwords used).|